public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Aleksandar Simeonov <Aleksandar.Simeonov@RT-RK.com>
To: Ian Lance Taylor <iant@google.com>
Cc: binutils <binutils@sourceware.org>, rich@mips.com
Subject: Re: Using linker script instead of library in Gold
Date: Thu, 14 Jul 2011 09:05:00 -0000	[thread overview]
Message-ID: <4E1EA2F5.4040509@RT-RK.com> (raw)
In-Reply-To: <mcripr6gp51.fsf@coign.corp.google.com>

Yes, but still when I do linking I got error like:
../../mips-linux-gnu-ld.gold: Attempt to open /usr/lib/libc.so succeeded
../../mips-linux-gnu-ld.gold: warning: skipping incompatible
/usr/lib/libc.so while searching for c
../../mips-linux-gnu-ld.gold: error: cannot find -lc

Maybe I overlooked something?

Aleksandar

On 13/07/2011 17:46, Ian Lance Taylor wrote:
> Aleksandar Simeonov <Aleksandar.Simeonov@RT-RK.com> writes:
> 
>> I have one short question today. Situation is as follow: instead of
>> having lib.so as shared library, on our Linux distribution we have ld
>> linker script:
>> /* GNU ld script
>>    Use the shared library, but some functions are only in
>>    the static library, so try that secondarily.  */
>> OUTPUT_FORMAT(elf32-tradlittlemips)
>> GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a  AS_NEEDED (
>> /lib/ld.so.1 ) )
>>
>> Is Gold capable of using it (for ld is enough to put -lc in command
>> line) and if yes, what command option should be used?
> 
> This is normal on any glibc-based system.  gold supports this without
> requiring any special options.
> 
> Ian
> 

  reply	other threads:[~2011-07-14  8:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 15:46 Aleksandar Simeonov
2011-07-13 19:39 ` Ian Lance Taylor
2011-07-14  9:05   ` Aleksandar Simeonov [this message]
2011-07-14 22:07     ` Ian Lance Taylor
2011-07-15 18:19       ` Aleksandar Simeonov

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=4E1EA2F5.4040509@RT-RK.com \
    --to=aleksandar.simeonov@rt-rk.com \
    --cc=binutils@sourceware.org \
    --cc=iant@google.com \
    --cc=rich@mips.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).