From: Eric Ding <ericding@applix.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: ld bug with -Bsymbolic --noinhibit-exec (2.9.1.0.990418-1c)
Date: Wed, 16 Jun 1999 17:14:25 -0400 [thread overview]
Message-ID: <199906162114.RAA11468@tuxedo.applix.com> (raw)
In-Reply-To: Message from Franz Sirl <Franz.Sirl-kernel@lauterbach.com> of "Wed, 16 Jun 1999 22:40:31 +0200." <99061622444300.00949@ns1102.munich.netsurf.de>
>>>>> Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:
> Hmm, I browsed thru the binutils code and didn't see anything suspicious. Is
> there any chance you can strip that down to a small testcase with a few
> symbols? That would help debugging a lot.
Sure can. Create a file (let's call it foo.c)... it just contains:
int foo_tester()
{
return(twenty());
}
Then run the following:
gcc -fPIC -c foo.c
After the compilation, run:
gcc -shared -o libfoo.so foo.o
gcc -shared -Wl,-Bsymbolic -o libfoo.so foo.o
gcc -shared -Wl,--noinhibit-exec -Wl,-Bsymbolic -o libfoo.so foo.o
On Intel, the first succeeds, the second fails (as expected), and the
third succeeds in building a .so file, even with the "undefined
reference" error.
On PPC, the first succeeds, but the second and third both fail.
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. ]]
next prev parent reply other threads:[~1999-06-16 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-16 16:29 ld bug with -Bsymbolic --noinhibit-exec (2.9.1.0.990418-1c) Eric Ding
1999-06-16 17:21 ` 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 [this message]
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=199906162114.RAA11468@tuxedo.applix.com \
--to=ericding@applix.com \
--cc=Franz.Sirl-kernel@lauterbach.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.