| 1 |
On 10/07/10 - 06:38:10, François Bissey wrote: |
| 2 |
> The more I look at ecls' configure.in the less I understand how |
| 3 |
> CFLAGS and |
| 4 |
> LDFLAGS are picked up at all on some machine. I thought it could be |
| 5 |
> debugging |
| 6 |
> flags but that's not it. |
| 7 |
> |
| 8 |
> There are a few more things that I can look at on my ~x86 machine |
| 9 |
> tomorrow. |
| 10 |
> |
| 11 |
> Francois |
| 12 |
> |
| 13 |
It must be getting the flags from portage, at least here. If I in ecls |
| 14 |
|
| 15 |
unset LDFLAGS |
| 16 |
|
| 17 |
before it is configured then "ecl-config --ldflags" returns no linker |
| 18 |
options. The linker flags then do not appear twice in the linking stage |
| 19 |
when maxima is built. However maxima will still not build when three |
| 20 |
(perhaps more) linker options are specified. |
| 21 |
|
| 22 |
Note: |
| 23 |
|
| 24 |
from J-F's build of maxima: |
| 25 |
linker flags: |
| 26 |
\"-Wl,-O1 -Wl,--sort-common -Wl,--as-needed\" with unrecognized option |
| 27 |
'--sort-common -Wl' |
| 28 |
|
| 29 |
my build: |
| 30 |
linker flags: |
| 31 |
\"-Wl,-O1 -Wl,--as-needed -Wl,--sort-common\" with unrecognized option |
| 32 |
'--as-needed -Wl' |
| 33 |
|
| 34 |
It would seem that "something" in maxima isn't correctly parsing the |
| 35 |
string containing the linker flags. If I build ecls |
| 36 |
|
| 37 |
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common" emerge ecls |
| 38 |
|
| 39 |
with the portage provided ecls and |
| 40 |
|
| 41 |
unset LDFLAGS in maxima before the configure then |
| 42 |
|
| 43 |
emerge maxima |
| 44 |
|
| 45 |
only picks up the ecls-provided linker flags and it builds, I assume |
| 46 |
correctly. However, I don't believe this approach is optimal. |
| 47 |
|
| 48 |
Steve |
Archives