1 |
Hi again, I'm trying to compile it on my own, without portage and |
2 |
following portage "econf" value. |
3 |
So, it seems I can compile (well, it hasn't ended yet, but seems to |
4 |
go on on stage2....) |
5 |
I've noticed a thing. My CFLAGS are |
6 |
|
7 |
CFLAGS="-mieee -mcpu=ev67 -Wa,-mev6 -O2 -pipe " |
8 |
|
9 |
as defined in /etc/make.conf, but as I emerge gcc, the CFLAGS that |
10 |
appear at the top (and used during gcc build) are |
11 |
|
12 |
CFLAGS="-mieee -mcpu=ev67 -O2 -pipe " |
13 |
|
14 |
so the "-Wa,-mev6" has been blown away.... In past times I've found |
15 |
that on ev68 processors this flag was necessary for compiling many |
16 |
things (including gcc), I can't recall where I found this, but I've |
17 |
posted it on safe cflags wiki on gentoo wiki. |
18 |
Now I wonder how can I modify the gcc ebuild to prevent this (I |
19 |
prefer the use of ebuilds in place of manual installation), but gcc |
20 |
ebuild are pretty strange and fcc-4.1.1-r3 ebuild (like others, I |
21 |
presume) calls some emerge functions that are not within the ebuild |
22 |
itself. Can anybody help me on this? |
23 |
|
24 |
Thanks |
25 |
|
26 |
d |
27 |
|
28 |
/* |
29 |
Davide Cittaro |
30 |
HPC and Bioinformatics Systems @ Informatics Core |
31 |
|
32 |
IFOM - Istituto FIRC di Oncologia Molecolare |
33 |
via adamello, 16 |
34 |
20139 Milano |
35 |
Italy |
36 |
|
37 |
tel.: +39(02)574303007 |
38 |
e-mail: davide.cittaro@×××××××××××××××.it |
39 |
*/ |