Hi, I've just upgraded my system from 32bits, to amd64 and after having tried to run a 64bit static program, to discover that my system refuses to run it. My next step is to ask what do I need, to get a static 64-bit program to run on this system?
Örn Hansen
Hi,
I've just upgraded my system from 32bits, to amd64 and after having tried to run a 64bit static program, to discover that my system refuses to run it. My next step is to ask what do I need, to get a static 64-bit program to run on this system?
A 64-bit kernel... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
lördag 10 april 2004 10:26 skrev Andreas Jaeger:
A 64-bit kernel...
That's the easy part ... Hard part is, that it also demands the ld-linux to be 64-bit. And then the question is, what's the minimum number of packages I have to forcefeed, to get a system that won't break on startup. Since the process being used here, is similar to the difference between libc5 and libc6 some years back, and that was a real pain in the backside.
Andreas
Örn Hansen
lördag 10 april 2004 10:26 skrev Andreas Jaeger:
A 64-bit kernel...
That's the easy part ...
Hard part is, that it also demands the ld-linux to be 64-bit. And then the
A static program won't need it.
question is, what's the minimum number of packages I have to forcefeed, to get a system that won't break on startup. Since the process being used here, is similar to the difference between libc5 and libc6 some years back, and that was a real pain in the backside.
We're on the suse-amd64 list, so let me advertise a bit ;-): Get yourself SUSE Linux Professional 9.0 for AMD64 or 9.1 Professional. That way you get a full distribution and don't need to reinvent everything... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas Jaeger wrote:
Örn Hansen
writes: lördag 10 april 2004 10:26 skrev Andreas Jaeger:
A 64-bit kernel...
That's the easy part ...
Hard part is, that it also demands the ld-linux to be 64-bit. And then the
A static program won't need it.
question is, what's the minimum number of packages I have to forcefeed, to get a system that won't break on startup. Since the process being used here, is similar to the difference between libc5 and libc6 some years back, and that was a real pain in the backside.
We're on the suse-amd64 list, so let me advertise a bit ;-): Get yourself SUSE Linux Professional 9.0 for AMD64 or 9.1 Professional. That way you get a full distribution and don't need to reinvent everything...
Andreas
WRT that last recommendation, if I go buy 9.0 or 9.1 Professional at CompUSA, will it include AMD64 support, or do I have to retreive that from SuSE's FTP site ? What about 9.0 or 9.1 Personal ? TIA
"William A. Mahaffey III"
WRT that last recommendation, if I go buy 9.0 or 9.1 Professional at CompUSA, will it include AMD64 support, or do I have to retreive that from SuSE's FTP site ? What about 9.0 or 9.1 Personal ? TIA
9.0: There're two SUSE Linux 9.0 Professional versions, a 32-bit x86 one and the 64-bit AMD64 one. 9.1: There will be just one box that includes support for both architectures. Personal only supports 32-bit x86. Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
lördag 10 april 2004 13:22 skrev Andreas Jaeger:
We're on the suse-amd64 list, so let me advertise a bit ;-): Get yourself SUSE Linux Professional 9.0 for AMD64 or 9.1 Professional. That way you get a full distribution and don't need to reinvent everything...
I did buy the 9.0 Professional, only the 32bit version. And I'll wait to buy another, until the 9.1 becomes available here. Which is usually about two to three weeks, after it's released. In the meantime, I did the conversion ... and it took hours, ugh. These are the steps I took. 1. Replace running kernel with 64bit version. 2. Replace glibc and friends, with both 32bit and 64bit versions. This part went fine, the system was working great. It should also be quite enough for anyone, only wanting to run 64bit programs, unfortunately mine also had a 64bit X frontend, so I couldn't stop here. At this point, YaST should be ones best friend. However, I hand converted a few programs to get away cheaply or to only have to re-install X and friends, and ended up having to to the total conversion anyway. I ended up, letting YaST do the conversion. However, YaST still shows an i386 based system in the dialog box, when I want to do an "upgrade" ... anyone know how to change this part?
Andreas
Örn Hansen
At this point, YaST should be ones best friend. However, I hand converted a few programs to get away cheaply or to only have to re-install X and friends, and ended up having to to the total conversion anyway. I ended up, letting YaST do the conversion. However, YaST still shows an i386 based system in the dialog box, when I want to do an "upgrade" ... anyone know how to change this part?
This one comes from some YaST configuration file in /var/ - but I wouldn't change it, you changed the system behind's YaST back and I now changes with yast might break stuff... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (3)
-
Andreas Jaeger
-
William A. Mahaffey III
-
Örn Hansen