From: Ian Lance Taylor <ian@zembu.com>
To: Franz.Sirl-kernel@lauterbach.com
Cc: binutils@sourceware.cygnus.com, drow@false.org, geoffk@ozemail.com.au
Subject: Re: R_PPC_LOCAL24PC c++ linking problems with current binutils
Date: Mon, 19 Jul 1999 16:49:00 -0000 [thread overview]
Message-ID: <19990719234924.28643.qmail@daffy.airs.com> (raw)
In-Reply-To: <99072000221900.00843@ns1102.munich.netsurf.de>
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Date: Tue, 20 Jul 1999 00:07:53 +0200
Compiling with c++ -o mmaptest.so -fPIC -shared mmaptest.cc gives:
mmaptest.o: In function `__default_alloc_template<true, 0>::_S_chunk_alloc(unsigned int, int &)':
mmaptest.o(.__default_alloc_template<true, 0>::gnu.linkonce.t._S_chunk_alloc(unsigned int, int &)+0x234): undefined reference to `__default_alloc_template<true, 0>::_S_chunk_alloc(unsigned int, int &)'
mmaptest.o(.__default_alloc_template<true, 0>::gnu.linkonce.t._S_chunk_alloc(unsigned int, int &)+0x2a8): undefined reference to `__default_alloc_template<true, 0>::_S_chunk_alloc(unsigned int, int &)'
collect2: ld returned 1 exit status
/* It makes no sense to point a local relocation
at a symbol not in this object. */
if (h != NULL
&& (h->root.type == bfd_link_hash_defined
|| h->root.type == bfd_link_hash_defweak)
&& sec->output_section == NULL)
I think the last is the wrong test. sec->output_section will be NULL
for a linkonce section which is being discarded. More appropriate
would be a test whether ELF_LINK_HASH_DEF_REGULAR is set in
h->elf_link_hash_flags.
Ian
next prev parent reply other threads:[~1999-07-19 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-19 15:21 Franz Sirl
1999-07-19 16:49 ` Ian Lance Taylor [this message]
1999-07-19 17:49 ` Daniel Jacobowitz
1999-07-19 19:56 ` Ian Lance Taylor
1999-07-19 20:07 ` Daniel Jacobowitz
1999-07-20 9:33 ` Ian Lance Taylor
1999-07-19 19:30 ` Geoff Keating
1999-07-19 20:05 ` Daniel Jacobowitz
1999-07-20 9:43 ` Ian Lance Taylor
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=19990719234924.28643.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=binutils@sourceware.cygnus.com \
--cc=drow@false.org \
--cc=geoffk@ozemail.com.au \
/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).