public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Johann Oskarsson <yohankun@yahoo.com>
To: binutils@sources.redhat.com
Subject: Re: undefined versioned symbol name (me too) <-- ld bug??
Date: Wed, 29 Aug 2001 08:05:00 -0000	[thread overview]
Message-ID: <20010829150509.89174.qmail@web10003.mail.yahoo.com> (raw)

Hi,

I, too, get this error when I try to compile kdelibs.

I can work around this by removing duplicated -l<lib>s, but the
doc say that is allowed...

I've attached log of the rerun of make and a shellscript that does
the linking correctly

Is this a bug in ld, and should I submit it as such????


Johann

bryanh at giraffe-data dot com (Bryan Henderson):
>I stumbled across a weird behavior that I'm trying to figure out.
>If I knew anything about versioned symbols, it might make sense.
>
>I do
>
>  ld -shared /usr/lib/libc.so strdup.o
>
>strdup.o defines the symbol "strdup", which is obviously defined in 
>libc.so as well.  libc.so is glibc 2.1.3.
>
>This produces the error message:
>
>  ld: a.out: undefined versioned symbol name strdup@@GLIBC_2.0
>
>Why?  What is it telling me?
>
>This is followed by the message
>
>  ld: failed to set dynamic section sizes: Bad value
>
>which kind of makes it sound like an internal failure.  But I'm not
>jumping to any conclusions, since I don't know how versioned symbols
>work at all.
>
>This is GNU ld 2.10.1.
>
>-- 
>Bryan Henderson                                    Phone
415-505-3367
>San Jose, California


__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
kdelibs.log
khtml.sh

                 reply	other threads:[~2001-08-29  8:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010829150509.89174.qmail@web10003.mail.yahoo.com \
    --to=yohankun@yahoo.com \
    --cc=binutils@sources.redhat.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).