To compile 64 bit?
Hello SuSE people. Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit. Ex: Tonight I went to download smart at Guru's site. There were no 64 bit versions, only i686 and src's. I hesitated to download either because I didn't know if either of them would work without problems. Bob S..
B. Stia wrote:
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit.
Ex: Tonight I went to download smart at Guru's site. There were no 64 bit versions, only i686 and src's. I hesitated to download either because I didn't know if either of them would work without problems. You could always try and see, but be prepared to install quite a few more devel packages. Try this (as root if you are not set up to build rpm packages as a normal user), rpmbuild --rebuild --target=x86_64 <packagename>.src. If it works, you can find your new shiny rpm in /usr/src/packages/RPMS/x86_64. HTH
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Tuesday 29 November 2005 04:20 am, Joe Morris (NTM) wrote:
B. Stia wrote:
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit.
Ex: Tonight I went to download smart at Guru's site. There were no 64 bit versions, only i686 and src's. I hesitated to download either because I didn't know if either of them would work without problems.
You could always try and see, but be prepared to install quite a few more devel packages. Try this (as root if you are not set up to build rpm packages as a normal user), rpmbuild --rebuild --target=x86_64 <packagename>.src. If it works, you can find your new shiny rpm in /usr/src/packages/RPMS/x86_64. HTH
Hi Joe, This is what I got when I tried it. Don't understand what the error messages mean. EasyStreet:/home/bob/installing/new # rpmbuild --rebuild --target=x86_64 smart-0.40-12.guru.suse93.src.rpm Installing smart-0.40-12.guru.suse93.src.rpm warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root Building target platforms: x86_64 Building for target x86_64 sh: kde-config: command not found error: /usr/src/packages/SPECS/smart.spec:44: parseExpressionBoolean returns -1 error: Name field must be present in package: (main package) error: Version field must be present in package: (main package) error: Release field must be present in package: (main package) error: Summary field must be present in package: (main package) error: Group field must be present in package: (main package) error: License field must be present in package: (main package) EasyStreet:/home/bob/installing/new # Not a big deal. Just would like to know/understand. Bob S.
B. Stia wrote:
This is what I got when I tried it. Don't understand what the error messages mean.
I'll try to explain by group:
EasyStreet:/home/bob/installing/new # rpmbuild --rebuild --target=x86_64 smart-0.40-12.guru.suse93.src.rpm Installing smart-0.40-12.guru.suse93.src.rpm warning: user pab does not exist - using root warning: user pab does not exist - using root warning: user pab does not exist - using root
<snip redundant> He builds as a user, which was pab. You were not, and do not have that user on your system
Building target platforms: x86_64 Building for target x86_64 sh: kde-config: command not found
error: /usr/src/packages/SPECS/smart.spec:44: parseExpressionBoolean returns -1 error: Name field must be present in package: (main package) error: Version field must be present in package: (main package) error: Release field must be present in package: (main package) error: Summary field must be present in package: (main package) error: Group field must be present in package: (main package) error: License field must be present in package: (main package) These are variables usually placed in the spec file, but he must place
Interesting. joe@jmorris:~> locate kde-config /opt/kde3/bin/kde-config joe@jmorris:~> rpm -qf /opt/kde3/bin/kde-config kdelibs3-3.5.0-14 them in his ~.rpmmacros file which is used to build as a user. If you added the above to the spec file, it might build. I'm not sure since kde-config was not found. -- Joe Morris Registered Linux user 231871
On Thursday 01 December 2005 04:37 am, Joe Morris (NTM) wrote:
B. Stia wrote:
This is what I got when I tried it. Don't understand what the error messages mean.
......<snip some stuff>..... Hi Joe, Thanks for the explanation.
Building target platforms: x86_64 Building for target x86_64 sh: kde-config: command not found
Interesting. joe@jmorris:~> locate kde-config /opt/kde3/bin/kde-config joe@jmorris:~> rpm -qf /opt/kde3/bin/kde-config kdelibs3-3.5.0-14
Yeah, me too. Wonder if he has it looking for kde in /user ?
error: /usr/src/packages/SPECS/smart.spec:44: parseExpressionBoolean returns -1 error: Name field must be present in package: (main package) error: Version field must be present in package: (main package) error: Release field must be present in package: (main package) error: Summary field must be present in package: (main package) error: Group field must be present in package: (main package) error: License field must be present in package: (main package)
These are variables usually placed in the spec file, but he must place them in his ~.rpmmacros file which is used to build as a user. If you added the above to the spec file, it might build. I'm not sure since kde-config was not found.
The errors are what I was asking about. the rpmmacros is new to me. Oh well, maybe I can install the 686 version and see if it will work. Bob S.
-- Joe Morris Registered Linux user 231871
Joe Morris (NTM) wrote:
B. Stia wrote:
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit.
Ex: Tonight I went to download smart at Guru's site. There were no 64 bit versions, only i686 and src's. I hesitated to download either because I didn't know if either of them would work without problems. You could always try and see, but be prepared to install quite a few more devel packages. Try this (as root if you are not set up to build rpm packages as a normal user), rpmbuild --rebuild --target=x86_64 <packagename>.src. If it works, you can find your new shiny rpm in /usr/src/packages/RPMS/x86_64. HTH
Bulding rpms is user stuff. Don't ever do user stuff at root; you run the risk that you will stuff up (don't we all?) and maybe clobber your system as that chap with the GRUB problem seems to have done. Instead, learn how ot configure rpm to build programs as a user. Many times I argued this on redhat-devel, and eventually it seems Red Hat has managed to "covert" all its packages to build without root privilege.
On Mon, 28 Nov 2005 23:49:09 -0500 "B. Stia" <usr@sanctum.com> wrote:
Hello SuSE people.
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit. By default, if you are running on a 64-bit system with a 64-bit OS the compiler default should be 64-bits. The file command should tell you if a binary is 32-bit or 64-bit. One of the problems that developers have is that most 32-bit apps work fine on 64-bit systems, so there is not much incentive to provide both a 32-bit and 64-bit version. And, there is no guarantee that the 64-bit version will be faster.
BTW: I've been working 64-bits since about 1994 on the Alpha. One problem we had with the Alpha was that we had fx32 which allowed us to run 32-bit Windows apps on the 64-bit Alpha running NT. The idea was to ease the transition, but it also provided no incentive for developers to create native 64-bit Alpha code. I think that the transition to 64-bits in Linux space will be a bit slow, but as Intel and AMD stop making the 32-bit chips, there will be some steady progress. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
Tirsdag 29 november 2005 05:49, skrev B. Stia:
Hello SuSE people.
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit.
Ex: Tonight I went to download smart at Guru's site. There were no 64 bit versions, only i686 and src's. I hesitated to download either because I didn't know if either of them would work without problems.
Bob S..
http://ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-x86_64/RPMS.suser-drcux/ This is a link to Guru rpms compiled for x86_64. There should be other mirrors, but I guess you can find them yourself. Iznogood
On Tuesday 29 November 2005 07:34 am, Iznogood wrote:
Tirsdag 29 november 2005 05:49, skrev B. Stia:
Hello SuSE people.
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit.
Ex: Tonight I went to download smart at Guru's site. There were no 64 bit versions, only i686 and src's. I hesitated to download either because I didn't know if either of them would work without problems.
Bob S..
http://ftp.gwdg.de/pub/linux/suse/apt/SuSE/10.0-x86_64/RPMS.suser-drc ux/
This is a link to Guru rpms compiled for x86_64.
There should be other mirrors, but I guess you can find them yourself.
Iznogood
Hey, thanks for the input and interest, but I am still running 9.2. Is Iznogood your real name??? :-) I love it !! Bob S.
On Mon, 28 Nov 2005 23:49:09 -0500, B. Stia wrote:
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit.
Why? Linux supports running 32bit apps in a 64bit system environment but *not* the other way round. And if you compile sources on a 64bit system you automatically get 64 bit apps. Philipp
On Wednesday 30 November 2005 09:55 pm, Philipp Thomas wrote:
On Mon, 28 Nov 2005 23:49:09 -0500, B. Stia wrote:
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit.
Why? Linux supports running 32bit apps in a 64bit system environment but *not* the other way round. And if you compile sources on a 64bit system you automatically get 64 bit apps.
Philipp
Hi Philipp, Yes of course, you are correct. But it was only offered as a .686 version in 32 bit and I was afraid that might mess things up. You think it will work? Bob S.
B. Stia wrote:
On Wednesday 30 November 2005 09:55 pm, Philipp Thomas wrote:
On Mon, 28 Nov 2005 23:49:09 -0500, B. Stia wrote:
Question: Am running an AMD 64 processor. There are still not all programs that are 64 bit. I know that the system will handle 32 bit stuff but I was wondering if an src file can be compiled to 64 bit. Why? Linux supports running 32bit apps in a 64bit system environment but *not* the other way round. And if you compile sources on a 64bit system you automatically get 64 bit apps.
Philipp
Hi Philipp, Yes of course, you are correct. But it was only offered as a .686 version in 32 bit and I was afraid that might mess things up. You think it will work?
Bob S.
_I_ think it will either work, or fail very quickly. The most important Q is whether it's built for USUSE? If not, there may be other problems, whether you build it yourself or no.
participants (6)
-
B. Stia -
Iznogood -
Jerry Feldman -
Joe Morris (NTM) -
John Summerfield -
Philipp Thomas