1 |
Duncan posted <pan.2006.02.15.07.53.34.26158@×××.net>, excerpted below, |
2 |
on Wed, 15 Feb 2006 00:53:34 -0700: |
3 |
|
4 |
> Simon Stelling posted <43F23F8A.80905@g.o>, excerpted below, on |
5 |
> Tue, 14 Feb 2006 21:37:30 +0100: |
6 |
> |
7 |
>> Duncan wrote: |
8 |
>>> Is -fPIC gcc-version sensitive? |
9 |
>> |
10 |
>> It might be that some version of gcc prints a warning when configure |
11 |
>> performs a test to decide whether -fPIC is a supported flag or not and |
12 |
>> another version doesn't. Depending on that, configure might decide that |
13 |
>> it's not supported and compile everything without -fPIC. Have a close |
14 |
>> look to configure's output and config.log, I'm pretty sure that's the |
15 |
>> issue here. |
16 |
> |
17 |
> Thanks. I'll check. |
18 |
|
19 |
FWIW, I did check, and you were right about the warning, but it wasn't |
20 |
due to -fPIC, but rather to one of my CFLAGS/CXXFLAGS (the warning: |
21 |
-freorder-blocks-and-partition does not work with exceptions). gcc-3.4.x |
22 |
doesn't print that warning, taking the flag without protest (tho it |
23 |
probably still ignores it, don't care enough to go find the gcc-3.4 docs |
24 |
and look), the gcc-4.1 snapshots do. |
25 |
|
26 |
So... The configure script simply interpreted the warning about the cflag |
27 |
being ignored as a warning about its added -fPIC being ignored. It |
28 |
therefore compiled without -fPIC and naturally failed. |
29 |
|
30 |
The problems with -freorder-blocks-and-partition do seem to be mostly with |
31 |
c++ code (as this was, the regular c test earlier in the script worked |
32 |
just fine), but also seem to be more trouble than they are worth. I'm |
33 |
thinking I'll now have to split them up, tracking them separately, much as |
34 |
I hate to do so. (The weaker non-partitioning version -freorder-blocks, |
35 |
works just fine, as I've had it in my CFLAGS as well, since the long |
36 |
cflags post I made some weeks ago, without issue. The problems are all |
37 |
with the -and-partition version, and almost all with c++, not c.) |
38 |
|
39 |
Hmm... I wonder which warning option controls those warnings. Maybe I |
40 |
can turn it off in the same C(XX)?FLAGS variables that turn on the flag |
41 |
creating them? Since it seems to be mainly a c++ problem, however, little |
42 |
if any C++ code appears to be able to use the partition thing anyway, and |
43 |
I haven't investigated gcc's warning options much, I think I'll try the |
44 |
separate CXXFLAGS without that for awhile, first, tho. |
45 |
|
46 |
I'm actually quite relieved, as I had noticed a few more -fPIC errors |
47 |
recently, apparently all due to this. I was beginning to worry that all |
48 |
the -fPIC work that the Gentoo amd64 team has done was somehow getting |
49 |
lost! Finding out it was my own system is therefore /quite/ a relief, as |
50 |
I'd hate to have to go thru all those porting struggles again! I'm sure |
51 |
you'll agree! =8^) |
52 |
|
53 |
-- |
54 |
Duncan - List replies preferred. No HTML msgs. |
55 |
"Every nonfree program has a lord, a master -- |
56 |
and if you use the program, he is your master." Richard Stallman in |
57 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
58 |
|
59 |
|
60 |
-- |
61 |
gentoo-amd64@g.o mailing list |