From: "Per Øyvind Karlsen" <peroyvind@mandriva.org>
To: Ian Lance Taylor <iant@google.com>
Cc: binutils <binutils@sourceware.org>
Subject: Re: gold library search path?
Date: Thu, 14 Jul 2011 02:53:00 -0000 [thread overview]
Message-ID: <CA+0WU1Tws1e2H2xEYRo_TU1=X2QRMbpE1ZX4uVDaT=uJ8h9Ezw@mail.gmail.com> (raw)
In-Reply-To: <mcrmxgheq13.fsf@coign.corp.google.com>
2011/7/14 Ian Lance Taylor <iant@google.com>:
> Per Øyvind Karlsen <peroyvind@mandriva.org> writes:
>
>> I feel a bit silly for not being able to figure this out, trying
>> to go through the search over and over, googling and blah,
>> but I'm totally not able to figure out how to set the library search
>> of the gold linker during build..?
>>
>> Passing '--with-lib-path=/lib64:/usr/lib64:/usr/local/lib64:/usr/lib:/usr/local/lib'
>> to configure gives me the expected behaviour I want with the bfd linker,
>> but gold only wants to try search /lib & /usr/lib no matter what.. :|
>>
>> So that makes me wonder whether this actually might be a bug or not,
>> while still feeling a bit st00pid.. :p
>
> You're not stupid, there actually isn't a way to set gold's default
> library path using a configure option.
>
> I see that GNU ld does support a --with-lib-path configure option, and I
> would not be opposed to supporting it in gold either. The current
> default (/lib:/usr/lib, adjusted for any --sysroot option) is set in
> General_options::finalize in option.cc.
Ah, that explains it, I think that was where I found the traces of it
in the code,
but I figured that there had to like more "proper" and some actual "correct"
place to do it.
I guess I'll just patch option.cc for now, while awaiting for gold to support
the --with-lib-path option as well. :o)
--
Regards,
Per Øyvind
prev parent reply other threads:[~2011-07-14 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 23:07 Per Øyvind Karlsen
2011-07-14 1:01 ` Ian Lance Taylor
2011-07-14 2:53 ` Per Øyvind Karlsen [this message]
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='CA+0WU1Tws1e2H2xEYRo_TU1=X2QRMbpE1ZX4uVDaT=uJ8h9Ezw@mail.gmail.com' \
--to=peroyvind@mandriva.org \
--cc=binutils@sourceware.org \
--cc=iant@google.com \
/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).