public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david dot kirkby at onetel dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/36481] gcc fails to build on Solaris x86 - it forgets the locations of libmpfr
Date: Fri, 15 Jan 2010 13:15:00 -0000	[thread overview]
Message-ID: <20100115131541.22038.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36481-16025@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2010-01-15 13:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 23:28 [Bug c/36481] New: " david dot kirkby at onetel dot net
2008-06-10  8:53 ` [Bug bootstrap/36481] " pinskia at gcc dot gnu dot org
2008-06-10 22:37 ` david dot kirkby at onetel dot net
2008-07-02  1:00 ` BlanchardJ at ieee dot org
2009-03-23 17:23 ` gbarnt at student dot dtu dot dk
2009-03-23 17:23 ` gbarnt at student dot dtu dot dk
2009-03-23 18:38 ` gbarnt at student dot dtu dot dk
2009-03-23 18:43 ` gbarnt at student dot dtu dot dk
2009-03-24 17:47 ` rwild at gcc dot gnu dot org
2009-04-16  6:41 ` sebastian dot wenzler at hp dot com
2009-05-01  9:01 ` gbarnt at student dot dtu dot dk
2009-05-01  9:51 ` schwab at linux-m68k dot org
2010-01-14 10:04 ` abhishekfishy2000 at gmail dot com
2010-01-14 10:06 ` abhishekfishy2000 at gmail dot com
2010-01-15  4:44 ` david dot kirkby at onetel dot net
2010-01-15  5:12 ` BlanchardJ at ieee dot org
2010-01-15  9:59 ` david dot kirkby at onetel dot net
2010-01-15 12:37 ` BlanchardJ at ieee dot org
2010-01-15 13:15 ` david dot kirkby at onetel dot net [this message]
     [not found] <bug-36481-4@http.gcc.gnu.org/bugzilla/>
2012-01-28  5:28 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100115131541.22038.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).