Re: [gentoo-science] ecls/maxima summarry

[Steven Trogdon <strogdon@d.umn.edu>]

[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]

On   10/07/10 - 06:38:10, François Bissey wrote:
> The more I look at ecls' configure.in the less I understand how  
> CFLAGS and
> LDFLAGS are picked up at all on some machine. I thought it could be  
> debugging
> flags but that's not it.
> 
> There are a few more things that I can look at on my ~x86 machine  
> tomorrow.
> 
> Francois
> 
It must be getting the flags from portage, at least here. If I in ecls

unset LDFLAGS

before it is configured then "ecl-config --ldflags" returns no linker  
options. The linker flags then do not appear twice in the linking stage  
when maxima is built. However maxima will still not build when three  
(perhaps more) linker options are specified.

Note:

from J-F's build of maxima:
linker flags:
\"-Wl,-O1 -Wl,--sort-common -Wl,--as-needed\" with unrecognized option  
'--sort-common -Wl'

my build:
linker flags:
\"-Wl,-O1 -Wl,--as-needed -Wl,--sort-common\" with unrecognized option  
'--as-needed -Wl'

It would seem that "something" in maxima isn't correctly parsing the  
string containing the linker flags. If I build ecls

LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common" emerge ecls

with the portage provided ecls and

unset LDFLAGS in maxima before the configure then

emerge maxima

only picks up the ecls-provided linker flags and it builds, I assume  
correctly. However, I don't believe this approach is optimal.

Steve

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]