1 |
On 11/25/05, Harry Putnam <reader@×××××××.com> wrote: |
2 |
> Harry Putnam <reader@×××××××.com> writes: |
3 |
> |
4 |
> [...] |
5 |
> |
6 |
> > checking whether the C compiler (gcc -O2 -march=pentium4 -fomit-frame-pointer -L/usr/X11R6/lib -ltiff -L/usr/lib) is a cross-compiler... yes |
7 |
> |
8 |
> Still thinks its a cross-compiler... what does that mean anyway? |
9 |
|
10 |
Well, generally, it means that you are compiling for a different |
11 |
architecture than what you are running. For example, it is possible |
12 |
to compile for AMD64 CPUs from a P4 host, or vice-versa. However, |
13 |
since you are not doing that, it means your toolchain is broken in |
14 |
some way. |
15 |
|
16 |
The way autoconf (the ./configure script) checks for this is that it |
17 |
compiles a very simple program. This program is: |
18 |
|
19 |
|
20 |
#line 1880 "configure" |
21 |
#include "confdefs.h" |
22 |
|
23 |
main(){return(0);} |
24 |
|
25 |
It then compiles this program. If the program compiles, configure |
26 |
decides that gcc works. If the program doesn't run, it decides that |
27 |
you are cross compiling. So, let's try this manually. |
28 |
|
29 |
Save the above lines to a file, call it conftest.c. The build it with |
30 |
|
31 |
gcc -O2 -march=pentium4 -fomit-frame-pointer -L/usr/X11R6/lib -ltiff |
32 |
-L/usr/lib -o conftest conftest.c |
33 |
|
34 |
If the compile complets without error, try running the program with: |
35 |
|
36 |
conftest && echo "works" |
37 |
|
38 |
-Richard |
39 |
|
40 |
-- |
41 |
gentoo-user@g.o mailing list |