Mailinglist Archive: opensuse-amd64 (75 mails)
| < Previous | Next > |
Re: [suse-amd64] Compiling 32bit binaries on AMD64
- From: Volker Kuhlmann <hidden@xxxxxxxxxxxxxxx>
- Date: Fri, 6 Jan 2006 12:40:31 +1300
- Message-id: <20060105234030.GA9451@xxxxxxxxxxxxxxx>
> The answers on this list all seemed clear to me. It's really a FAQ
> if you look at the archives there are probably hundreds of mails
> about it, all with the same information.
I must have used the wrong words with google then.
> You seem to expect some complicated procedure but there really isn't any.
> I guess people don't take a feature seriously if it's too easy to use :|
Even better if it's not complicated, not good if there's insufficently
accessible documentation about it.
For a long time -march= has switched to compiling code for that
architecture - unless I'm completely mistaken. gcc -v --help is quite
clear:
-march= Generate code for given CPU
So I can expect -march=i586 to compile 32bit code, but nope.
The gcc people no doubt have a reason that -m32 is needed too.
rpmbuild --rebuild --target i586 is expected to recompile a package for
i586. Not so, as SUSE fails to supply the absolutely essential
-m32 with RPM_OPT_FLAGS. (#141206)
linux32 rpmbuild --rebuild target i586 is doing something, but whatever
it is, it's not making 32bit code.
3 different packages are compiled from the same .src.rpm just for x86
and x85_64 (i586.rpm, x64_64.rpm, -libs32-...x85_64.rpm). As it's all
from the same .src.rpm there obviously have to be different command
invocations to achieve this result. WTF are they?
The continued confusion about this shows that there is a need for better
information. The admin guide mentions -m32 in sections 26.2 and 26.3,
but it doesn't mention anything about recompiling packages. The whole
affair is not a simple "... people don't take a feature seriously if
it's too easy to use".
Volker
--
Volker Kuhlmann is possibly list0570 with the domain in header
http://volker.dnsalias.net/ Please do not CC list postings to me.
> if you look at the archives there are probably hundreds of mails
> about it, all with the same information.
I must have used the wrong words with google then.
> You seem to expect some complicated procedure but there really isn't any.
> I guess people don't take a feature seriously if it's too easy to use :|
Even better if it's not complicated, not good if there's insufficently
accessible documentation about it.
For a long time -march= has switched to compiling code for that
architecture - unless I'm completely mistaken. gcc -v --help is quite
clear:
-march= Generate code for given CPU
So I can expect -march=i586 to compile 32bit code, but nope.
The gcc people no doubt have a reason that -m32 is needed too.
rpmbuild --rebuild --target i586 is expected to recompile a package for
i586. Not so, as SUSE fails to supply the absolutely essential
-m32 with RPM_OPT_FLAGS. (#141206)
linux32 rpmbuild --rebuild target i586 is doing something, but whatever
it is, it's not making 32bit code.
3 different packages are compiled from the same .src.rpm just for x86
and x85_64 (i586.rpm, x64_64.rpm, -libs32-...x85_64.rpm). As it's all
from the same .src.rpm there obviously have to be different command
invocations to achieve this result. WTF are they?
The continued confusion about this shows that there is a need for better
information. The admin guide mentions -m32 in sections 26.2 and 26.3,
but it doesn't mention anything about recompiling packages. The whole
affair is not a simple "... people don't take a feature seriously if
it's too easy to use".
Volker
--
Volker Kuhlmann is possibly list0570 with the domain in header
http://volker.dnsalias.net/ Please do not CC list postings to me.
| < Previous | Next > |