Hi. Both your tests below worked okay.
./configure --prefix /opt --target=armv5tel-softfloat-linux-gnueabi --host=armv5tel-softfloat-linux-gnueabi --build=x86_64-pc-linux-gnu Now runs to the point of: checking pkg-config is at least version 0.9.0... no checking for SSL... configure: error: in `/root/dovecot/dovecot-1-2-6c0fb914e03e': configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. A reboot and rebuild must have cleared out some stored values. I now have the original error back. I thought I'd broken autoconf/automake :( It's good to know that you can screw things up and still roll everything back to how you had it. http://dev.gentoo.org/~vapier/eh/index.xml?part=1&chap=5 This guide talks about a pkg-config wrapper and setting some environmental variables. Specifically putting the wrapper in the PATH . I don't know which path variable is pertinent. It also talks about an emerge wrapper but doesn't say where to put that either. This http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5 talks about putting things in your PATH. env-update didn't like my attempt to put cross-pkg-config in the PATH. -- Thanks. Stephen Sven Rebhan wrote: > 2009/6/15 Stephen Feyrer <[email protected]>: >> ./configure runs happily and takes the arguments set to tell the system >> to cross compile but all I get is X86_64 binaries. > > Either the package you are building has a bug in the build system and > calls gcc instead of $CC or your cross-compiler is screwed up. You can > test the compile doing the following: > > cd /tmp && echo "int main(void) { return 0; }" >> test.c && > armv5tel-softfloat-linux-gnueabi-gcc -o test test.c && file test > > Check if the file that is built by the compiler is an arm binary. If > this is the case, check if > > emerge-armv5tel-softfloat-linux-gnueabi --root-deps=rdeps <package> > > works. If this does not work, try to dig into the autoconf/automake > code of the package and find the point where the wrong compiler is > used (you should probably see this in the build.log). > > Best regards and good luck! ;-) > > Sven
smime.p7s
Description: S/MIME Cryptographic Signature
