On Fri, 2006-09-22 at 09:50 +0100, Rob Andrews wrote:
On 22-Sep-2006 08:54.24 (BST), Andy Green wrote:
> I see, that would be convenient...
>
> --target PLATFORM
> When building the package, interpret PLATFORM as
> arch-vendor-os and set the macros
> %_target, %_target_cpu, and %_target_os accordingly.
>
> What happens at the moment when you try to use --target then?
Well, using --target i386 on an x86_64 installation, it managed to build
i386 binaries (using g++ -m32). But obviously, the library path was wrong.
It most likely managed to build for the correct architecture because it
passed --target=%{_target} to the configure script.
Nope, ... normally --target is
not involved/used by most configure
scripts.
What triggers compiling for i386's on x86_64 hosts is CFLAGS (-m32
etc.), i.e. inside of an rpm.spec, it's %rpmopts.
Ralf