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