This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/36481] gcc fails to build on Solaris x86 - it forgets the locations of libmpfr



------- Comment #18 from david dot kirkby at onetel dot net  2010-01-15 13:15 -------
Subject: Re:  gcc fails to build on Solaris x86 - it
 forgets the locations of libmpfr

BlanchardJ at ieee dot org wrote:
> ------- Comment #17 from BlanchardJ at ieee dot org  2010-01-15 12:37 -------
> 
>> Yes, thank you. That is helpful. How do you produce the $ISALIST? Is that
>> simply 
>> sparcv9 on a modern SPARC and amd64 on an Open Solaris system, or is it a list. 
>> If the latter, how do you every it.
>>
>>
>> drkirkby@hawk:~$ isalist
>> amd64 pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
>>
>> Do I need
>>
>> xport LD_OPTIONS='-R/opt/csw/lib/amd64 -R opt/csw/lib/pentium_pro+mmx etc" ? I 
>> doubt it, but I'm not sure what you mean there.
>>
>> Is it just this, or anything else I need to do? You say "typical blastwave
>> build 
>> would have at a minimum .." but I doubt you would consider gcc a "typical 
>> blastwave build" If there are further complications, can you let me know what 
>> they are.
>>
>> Dave
>>
> 
> Hi,
> 
> It's just the string '$ISALIST' so it will appear as-is in the final run path.
> The runtime linker will take care of expanding it correctly at runtime. So one
> just export LD_OPTIONS as-is before building.
> 
> 

Thank you. That's very helpful. I really hate having to set LD_LIBRARY_PATH -
it 
is particularly an issue if you have multiple compilers. There's alyways the 
chance it gets set to the wrong compiler by mistake.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36481


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]