1 |
Clemente Aguiar posted |
2 |
<6A0C419392D7BA45BD141D0BA4F253C7D0BD79@×××××××××××××××××××××××××.pt>, |
3 |
excerpted below, on Fri, 09 Dec 2005 09:39:01 +0000: |
4 |
> |
5 |
>> De: news [mailto:news@×××××××××.org] Em nome de Duncan |
6 |
>> |
7 |
>> Clemente Aguiar ... |
8 |
>> |
9 |
>> > After the basic stage3 instalation, kernel compilation and reboot, |
10 |
>> > everything was fine. [Then an emerge -e world yields an error on |
11 |
>> > gcc: snippage to the interesting stuff:] |
12 |
>> |
13 |
>> > -fPIC [snip but same gcc command] version-script=libgcc/32/libgcc.map |
14 |
>> > -o 32/libgcc_s.so.1.tmp -m32 [snip] |
15 |
>> |
16 |
>> -fPIC with -m32? |
17 |
>> |
18 |
> I did NOT add any of the compilation flags myself (-fPIC or -m32). |
19 |
|
20 |
-m32 is required when compiling 32-bit code on a multilib gcc. It's |
21 |
parallel to -m64, which is the default, for 64-bit code. Since gcc must |
22 |
compile both 64-bit and 32-bit compilers, the -m32 would be |
23 |
normal/expected for the 32-bit side. |
24 |
|
25 |
-fPIC is required for libraries in 64-bit mode, so it would be |
26 |
normal/expected there, but can cause issues in 32-bit mode or for |
27 |
executables (not libraries) in 64-bit mode, so wouldn't normally be used |
28 |
there. It's NOT normal on the 32-bit side! |
29 |
|
30 |
Thus, I'm at a loss as to why they'd both be seen in the same compile |
31 |
directive, except that sometimes folks add -fPIC themselves, but your |
32 |
CFLAGS below don't have it, so it wasn't you. AFAIK, it's a bug. |
33 |
|
34 |
>> > Here is my emerge --info |
35 |
>> > Portage 2.0.51.22-r3 (default-linux/amd64/2005.1, gcc-3.4.4, |
36 |
>> > glibc-2.3.5-r2, 2.6.12-gentoo-r10 x86_64) |
37 |
>> > ================================================================= |
38 |
>> > System uname: 2.6.12-gentoo-r10 x86_64 Intel(R) Xeon(TM) CPU 3.60GHz |
39 |
>> [snip] |
40 |
>> > ACCEPT_KEYWORDS="amd64" |
41 |
>> > AUTOCLEAN="yes" |
42 |
>> > CBUILD="x86_64-pc-linux-gnu" |
43 |
>> > CFLAGS="-O2 -march=nocona -pipe" |
44 |
>> |
45 |
>> OK, -fPIC isn't in your CFLAGS, so that isn't the problem. [snip] |
46 |
> |
47 |
> Thanks Duncan. |
48 |
> So far nobody else said anything about this issue. I am considering |
49 |
> filling a bug. I am a newbie on these matters (never filed a bug |
50 |
> before). |
51 |
> How should I go about it? |
52 |
> What should I mention about the bug? (what is the bug) |
53 |
|
54 |
A bug is something happening that shouldn't, by expectations and according |
55 |
to the documentation. Filing a bug refers to filing a report on the bug |
56 |
in bugzilla, the web based database most open source projects use to track |
57 |
bugs. Gentoo has its bugzilla at |
58 |
|
59 |
http://bugs.gentoo.org. |
60 |
|
61 |
The filing process is pretty well guided, telling you what is needed at |
62 |
each step. It's actually good that you HAVEN'T filed bugs elsewhere, |
63 |
before, because Gentoo's bug filing process is a bit different than most, |
64 |
and is actually more confusing (and frustrating) if you've used others and |
65 |
have preconceived ideas about how it /should/ work, than if you are |
66 |
starting out without such preconceived (and wrong for Gentoo) ideas. |
67 |
|
68 |
First, you need a bugzilla account, which you will log into every time you |
69 |
file a bug, or to add new information to bugs you've already filed, when |
70 |
the developer follows up and asks for it, or asks you to test something. |
71 |
To create your new account, follow the Open a new Bugzilla account option |
72 |
on the site I linked above. It'll ask for an email address and your name, |
73 |
then allow you to create the account, and mail you the password. |
74 |
|
75 |
Once you have your new account and are logged in, hit the "New" or |
76 |
"Report a bug" link, and it'll ask you to select a product. Normally and |
77 |
in this case, the product is "Gentoo Linux". |
78 |
|
79 |
Clicking on "Gentoo Linux" brings you to the main bug form page. You |
80 |
start by searching for your bug, so they don't get too many duplicate |
81 |
reports of the same thing. If there's nothing that matches, you then |
82 |
continue with the filing as instructed. Your error, and emerge info, both |
83 |
are helpful, but you posted both here, so you know that already. =8^) |
84 |
|
85 |
As it happens, a search on "gcc-3.4.4" already produces a couple hits that |
86 |
look relevant, so you should NOT file a new one this time. HOWEVER, it'll |
87 |
still be very useful to have your additional report on the existing bug, |
88 |
so if you haven't yet, please do create that account, and add your |
89 |
information as necessary to the existing bug. |
90 |
|
91 |
Here's the first bug, altho a look at his error attachment shows a |
92 |
different error, so this probably isn't yours: |
93 |
|
94 |
http://bugs.gentoo.org/show_bug.cgi?id=102688 |
95 |
|
96 |
Here's the second one. This one shows a similar error with -m32 and -fPIC |
97 |
in the same section. |
98 |
|
99 |
http://bugs.gentoo.org/show_bug.cgi?id=103922 |
100 |
|
101 |
I'd suggest you register and add your information to the several other |
102 |
folks who have reported a problem. Of special interest in your case is |
103 |
that it's a new install, so shouldn't have all the cruft many other |
104 |
systems might. That makes your report valuable because it doesn't have |
105 |
as many other complicating factors to consider. |
106 |
|
107 |
In addition to that, you'll probably want to add yourself to the cc: list, |
108 |
so you can follow the progress as they work on it. Note that progress |
109 |
doesn't always seem as rapid as you might like when you have one open |
110 |
that's frustrating your own progress. This particular bug was filed on |
111 |
8-27, with the last modified date shoing as 10-05, so some patience may be |
112 |
necessary. |
113 |
|
114 |
It's also possible, if gcc won't compile anything else either, you may |
115 |
need to revert to an older gcc, 3.4.3 or something, if 3.4.4 won't work |
116 |
for you at the moment. If you started with 3.4.3, and didn't specifically |
117 |
unmerge it, it's likely still on your system. All you'll need to do is |
118 |
merge gcc-config if necessary (it's likely already there), and then use it |
119 |
to switch to the older profile. Hopefully, the older one will work even if |
120 |
the newer one doesn't. |
121 |
|
122 |
If you don't have 3.4.3 still on your system, you should be able to get a |
123 |
bin-packaged version off the packages CD. In no case should you have to |
124 |
be stuck with the non-working version, even on a new install. |
125 |
|
126 |
-- |
127 |
Duncan - List replies preferred. No HTML msgs. |
128 |
"Every nonfree program has a lord, a master -- |
129 |
and if you use the program, he is your master." Richard Stallman in |
130 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
131 |
|
132 |
|
133 |
-- |
134 |
gentoo-amd64@g.o mailing list |