All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Ding <ericding@applix.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: ld bug with -Bsymbolic --noinhibit-exec (2.9.1.0.990418-1c)
Date: Wed, 16 Jun 1999 12:29:51 -0400	[thread overview]
Message-ID: <199906161629.MAA09854@tuxedo.applix.com> (raw)


Hi,

I'm developing on LinuxPPC R5, with egcs-1.1.2-12c and
binutils-2.9.1.0.990418-1c installed.  I'm running into a problem with
using the -Bsymbolic flag.  Building a shared library which references
global symbols that are not found in it, we usually use the
--noinhibit-exec flag so that shared library builds even without those
symbols being bound.

The build command looks like this:

    gcc -shared -Wl,-v -Wl,-Bsymbolic -Wl,--noinhibit-exec -o \
     /ax/axexec/axdata/axshlib/libaxel.so -L/ax/axexec/axdata/axshlib \
     -L/ax/axobj/axdata/rts elimports.o elexports.o \
     /ax/axobj/axdata/rts/axel.o

Without the -Bsymbolic flag, the shared library builds fine.  With the
flag, however, it spits out the following errors (which are expected):

GNU ld version 2.9.4 (with BFD 990418)
/ax/axobj/axdata/rts/axel.o: In function `ElfInstallLibModules':
/ax/axobj/axdata/rts/axel.o(.text+0x38): undefined reference to `ElfInstallModule'
/ax/axobj/axdata/rts/axel.o(.text+0x48): undefined reference to `ElfInstallModule'
/ax/axobj/axdata/rts/axel.o(.text+0x58): undefined reference to `ElfInstallModule'
/ax/axobj/axdata/rts/axel.o: In function `ELElfMacroId':
/ax/axobj/axdata/rts/axel.o(.text+0xc0): undefined reference to `ElfGetModuleStartInd'

On other platforms (i.e., Intel, Alpha), we also see these errors, but
because of the --noinhibit-exec flag, the shared library is correctly
built anyway.  But on PPC, ld returns with 1 exit status, and the shared
library is not built.  Not using -Bsymbolic is not an option.

Ideas?

Thanks,
Eric
-- 
Senior Software Engineer / ericding@applix.com               <><
Applix, Inc. / 112 Turnpike Road / Westboro MA 01581-2842

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

             reply	other threads:[~1999-06-16 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-16 16:29 Eric Ding [this message]
1999-06-16 17:21 ` ld bug with -Bsymbolic --noinhibit-exec (2.9.1.0.990418-1c) Franz Sirl
1999-06-16 18:09   ` Eric Ding
1999-06-16 18:31     ` Franz Sirl
1999-06-16 19:38       ` Eric Ding
1999-06-16 20:40         ` Franz Sirl
1999-06-16 21:14           ` Eric Ding
1999-06-17 21:24             ` Franz Sirl
1999-06-17 22:49               ` Eric Ding
1999-06-18 19:54               ` Eric Ding
1999-06-21  9:31                 ` Franz Sirl
1999-06-21 13:05                   ` Franz Sirl
1999-06-21 19:44                     ` Eric Ding

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=199906161629.MAA09854@tuxedo.applix.com \
    --to=ericding@applix.com \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.