| 1 |
At the risk of participating |
| 2 |
in the upstream open source communitee I sent my configure issues to |
| 3 |
the autotools people. Below is the response. It looks like I need to |
| 4 |
see why "--host" is being set the way it is. |
| 5 |
|
| 6 |
As usual send any tips my way, I'll be delving into the code. |
| 7 |
|
| 8 |
matt |
| 9 |
|
| 10 |
Hi Matt, |
| 11 |
|
| 12 |
* m h wrote on Wed, Jan 11, 2006 at 08:26:02PM CET: |
| 13 |
... |
| 14 |
> The idea being you install portage in a "prefixed" |
| 15 |
> environment. This environment is sort of a sandboxed filesystem. |
| 16 |
> (Fink and openpkg are existing examples of this). Then the user can |
| 17 |
> install whatever software portage supports easily into the sandboxed |
| 18 |
> environment. |
| 19 |
|
| 20 |
OK. Fine idea. |
| 21 |
|
| 22 |
> I'm running into configure issues that I can't seem to resolve. (I |
| 23 |
> wouldn't call myself a C programmer. I'm much more comfy in python. |
| 24 |
> But I can get around a linux system). My issue is that when portage |
| 25 |
> runs the "./configure" I get errors like the following: |
| 26 |
|
| 27 |
OK. Much more interesting are config.log contents (and much more |
| 28 |
detailed, so if you really need to post it all, please pack it). |
| 29 |
Some hints: |
| 30 |
|
| 31 |
> checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc |
| 32 |
|
| 33 |
So you used --host or the like, to announce cross-compilation. In that |
| 34 |
case a $host_alias-prefixed compiler will be preferred. And is found |
| 35 |
here. |
| 36 |
|
| 37 |
> checking for C compiler default output... a.out |
| 38 |
> checking whether the C compiler works... yes |
| 39 |
> checking whether we are cross compiling... no |
| 40 |
|
| 41 |
(i.e., $host = $build). |
| 42 |
|
| 43 |
> checking for suffix of executables... |
| 44 |
> checking for suffix of object files... |
| 45 |
|
| 46 |
This is suspicious. config.log should be able to tell more. |
| 47 |
|
| 48 |
> checking for a BSD-compatible install... /data1/portage/jan6/prefix/toolsbox-4-p |
| 49 |
> atchespre.20060106/i686-pc-linux-gnu//bin/ginstall -c |
| 50 |
|
| 51 |
This is weird, too. How exactly do you call configure? |
| 52 |
|
| 53 |
> checking whether make sets $(MAKE)... no |
| 54 |
|
| 55 |
Very weird. |
| 56 |
|
| 57 |
> checking for ANSI C header files... no |
| 58 |
|
| 59 |
Your compiler does not find its default headers for some reason. |
| 60 |
|
| 61 |
> Disconcerting is the mention that there is no GNU C compiler (which is |
| 62 |
> sitting in $PREFIX/bin/gcc) and the "WARNING"s. |
| 63 |
> When the same configure command from the command line (using the same |
| 64 |
> env variables, since PATH is adjusted for the prefixed environment), |
| 65 |
> it works. |
| 66 |
|
| 67 |
So maybe you did not want i686-pc-linux-gnu-gcc, but plain gcc? |
| 68 |
If you have to specify cross-compilation, then set CC=gcc, too. |
| 69 |
|
| 70 |
Hope those tips help a bit. |
| 71 |
|
| 72 |
Cheers, |
| 73 |
Ralf |
| 74 |
|
| 75 |
-- |
| 76 |
gentoo-osx@g.o mailing list |
Archives