On Wed, Apr 05, 2006 at 06:32:01PM -0400, Matthew Saltzman wrote: > (I've put gnumeric aside for a bit.) > > I tried to build Axel Thimm's f2c RPM for PPC using: > > rpmbuild -bb --target ppc f2c-20031026-2.el4.at.spec > > (after fixing a minor spec file issue). When it finishes building on my > PPC64 system, I read over the original post too quickly. If you want to build for ppc on ppc64 you would need to do so in a chroot using rpmbuild's --root option. Simply using --target and even -m32 is not enough, the build environment is different. The next question would be how to create a matching chroot environment on your system. The easiest way is not to, just use a native ppc system to build on. Otherwise there are some tools on rhn to help you create such a build environment (never used them, though). Other popular tools like dar and mach or any self-brown stuff require you to have a local pool of packages available. I think Dag Wieers has started to work on a tool (or even already finished it?) for RHEL doing all the xml-rpc retrieval stuff, check the list's archive for an announcement he made a while ago here. > it installs the libraries it built into /usr/lib64 instead of > /usr/lib. Of course, as these are 32-bit libraries, it wreaks havoc > with the linker when it looks for libf2c.a. > > Target ppc is definitely 32 bits, so what is causing _libdir to be set to > /usr/lib64? Is it a bug? (Nothing that appears relevant is set in the > spec file or in my .rpmmacros file.) > -- Axel.Thimm at ATrpms.net
Attachment:
pgp6HsDd8r0lj.pgp
Description: PGP signature