From: LaMont Jones <lamont@hp.com>
To: parisc-linux@parisc-linux.org
Cc: LaMont Jones <lamont@hp.com>
Subject: [parisc-linux] still getting $$dyncall refs in shlibs
Date: Thu, 24 May 2001 15:32:59 -0600 [thread overview]
Message-ID: <20010524213301.126241872C@security.hp.com> (raw)
With the new toolchain, sipp still builds a libsipp.so.3.1 trips the
bug checker. Checking everything on the system doesn't find any bad
libs. Here is the build output for libsipp.so:
gcc -pipe -O3 -fPIC -I../libsipp -c -o rendering.o rendering.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o geometric.o geometric.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o lightsource.o lightsource.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o objects.o objects.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o smalloc.o smalloc.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o transforms.o transforms.c
...
gcc -pipe -O3 -fPIC -I../libsipp -c -o xalloca.o xalloca.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o phong.o phong.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o strauss.o strauss.c
gcc -pipe -O3 -fPIC -I../libsipp -c -o teapot.o teapot.c
ld --shared -o libsipp.so.3.1 rendering.o geometric.o lightsource.o objects.o smalloc.o transforms.o viewpoint.o basic_shader.o marble.o granite.o mask.o bozo.o bumpy.o planet.o noise.o bezier.o bezier_lex.o pixelbuf.o torus.o cone.o ellipsoid.o prism.o sipp_pixmap.o sipp_bitmap.o wood.o xalloca.o phong.o strauss.o teapot.o -soname libsipp.so.3 -lc
ld: bfd assertion fail ../../bfd/elf32-hppa.c:941
ld: bfd assertion fail ../../bfd/elf32-hppa.c:941
Of course, if the assertion failure actually killed the linker, that
would help...
I'm at a loss from here - and give it to those who have a clue...
lamont
next reply other threads:[~2001-05-24 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 21:32 LaMont Jones [this message]
2001-05-24 21:42 ` [parisc-linux] still getting $$dyncall refs in shlibs Matthew Wilcox
2001-05-24 21:59 ` [parisc-linux] " LaMont Jones
2001-05-24 23:02 ` amodra
2001-05-24 22:59 ` John David Anglin
2001-05-24 23:14 ` LaMont Jones
2001-05-24 23:26 ` John David Anglin
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=20010524213301.126241872C@security.hp.com \
--to=lamont@hp.com \
--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 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.