Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: bug-binutils@gnu.org, binutils@sources.redhat.com
Cc: debian-gcc@lists.debian.org, parisc-linux@parisc-linux.org
Subject: [parisc-linux] [hppa] binutils will not build shared libraries with external deps?
Date: Mon, 26 May 2003 22:22:51 -0700	[thread overview]
Message-ID: <20030527052251.GC24873@tausq.org> (raw)

Looks like latest binutils CVS (also as of 2.14.90.0.1) cannot build
shared libraries that have external symbols on at least hppa-linux:

tausq@ios:~$ cat blah.c
extern int foo();
int call_foo() { return foo(); }

tausq@ios:~$ gcc -shared -fPIC -o blah.so blah.c
/tmp/ccC3fZeH.o(.text+0x1c): In function `call_foo':
: undefined reference to `foo'

this worked fine on older binutils (e.g. 2.13.90.0.16 worked).

does anyone know what might be broken? this is causing a lot of failures
in the binutils test suite....

thanks,
randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

             reply	other threads:[~2003-05-27  4:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27  5:22 Randolph Chung [this message]
2003-05-28 19:07 ` [parisc-linux] Re: [hppa] binutils will not build shared libraries with external deps? amodra
2003-05-28 20:27   ` H. J. Lu
2003-05-28 20:27   ` H. J. Lu
2003-05-29 16:10     ` Matthias Klose
2003-05-29 16:10     ` Matthias Klose
2003-06-02 21:10   ` John David Anglin
2003-06-02 23:09     ` Alan Modra
2003-06-02 23:09     ` Alan Modra
2003-06-04 18:23       ` John David Anglin
2003-06-04 18:23       ` John David Anglin
2003-06-02 21:10   ` John David Anglin
2003-05-28 19:07 ` amodra
  -- strict thread matches above, loose matches on Subject: below --
2003-05-27  5:22 [parisc-linux] " Randolph Chung

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=20030527052251.GC24873@tausq.org \
    --to=tausq@debian.org \
    --cc=binutils@sources.redhat.com \
    --cc=bug-binutils@gnu.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=parisc-linux@parisc-linux.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