| 1 |
Hi. |
| 2 |
|
| 3 |
Both your tests below worked okay. |
| 4 |
|
| 5 |
./configure --prefix /opt --target=armv5tel-softfloat-linux-gnueabi |
| 6 |
--host=armv5tel-softfloat-linux-gnueabi --build=x86_64-pc-linux-gnu |
| 7 |
|
| 8 |
Now runs to the point of: |
| 9 |
|
| 10 |
checking pkg-config is at least version 0.9.0... no |
| 11 |
checking for SSL... configure: error: in |
| 12 |
`/root/dovecot/dovecot-1-2-6c0fb914e03e': |
| 13 |
configure: error: The pkg-config script could not be found or is too |
| 14 |
old. Make sure it |
| 15 |
is in your PATH or set the PKG_CONFIG environment variable to the full |
| 16 |
path to pkg-config. |
| 17 |
|
| 18 |
A reboot and rebuild must have cleared out some stored values. I now |
| 19 |
have the original error back. I thought I'd broken autoconf/automake :( |
| 20 |
|
| 21 |
It's good to know that you can screw things up and still roll everything |
| 22 |
back to how you had it. |
| 23 |
|
| 24 |
http://dev.gentoo.org/~vapier/eh/index.xml?part=1&chap=5 |
| 25 |
|
| 26 |
This guide talks about a pkg-config wrapper and setting some |
| 27 |
environmental variables. Specifically putting the wrapper in the PATH . |
| 28 |
I don't know which path variable is pertinent. It also talks about an |
| 29 |
emerge wrapper but doesn't say where to put that either. |
| 30 |
|
| 31 |
|
| 32 |
This http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=5 |
| 33 |
|
| 34 |
talks about putting things in your PATH. env-update didn't like my |
| 35 |
attempt to put cross-pkg-config in the PATH. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Thanks. |
| 40 |
|
| 41 |
Stephen |
| 42 |
|
| 43 |
|
| 44 |
Sven Rebhan wrote: |
| 45 |
> 2009/6/15 Stephen Feyrer <steve@××××××××.uk>: |
| 46 |
>> ./configure runs happily and takes the arguments set to tell the system |
| 47 |
>> to cross compile but all I get is X86_64 binaries. |
| 48 |
> |
| 49 |
> Either the package you are building has a bug in the build system and |
| 50 |
> calls gcc instead of $CC or your cross-compiler is screwed up. You can |
| 51 |
> test the compile doing the following: |
| 52 |
> |
| 53 |
> cd /tmp && echo "int main(void) { return 0; }" >> test.c && |
| 54 |
> armv5tel-softfloat-linux-gnueabi-gcc -o test test.c && file test |
| 55 |
> |
| 56 |
> Check if the file that is built by the compiler is an arm binary. If |
| 57 |
> this is the case, check if |
| 58 |
> |
| 59 |
> emerge-armv5tel-softfloat-linux-gnueabi --root-deps=rdeps <package> |
| 60 |
> |
| 61 |
> works. If this does not work, try to dig into the autoconf/automake |
| 62 |
> code of the package and find the point where the wrong compiler is |
| 63 |
> used (you should probably see this in the build.log). |
| 64 |
> |
| 65 |
> Best regards and good luck! ;-) |
| 66 |
> |
| 67 |
> Sven |
Archives