From: Joe Buck <jbuck@synopsys.com>
To: egcs@cygnus.com (egcs team)
Subject: Solaris problems with exceptions+shared libraries, 971031
Date: Sat, 01 Nov 1997 13:42:00 -0000 [thread overview]
Message-ID: <199711012142.NAA27180@atrus.synopsys.com> (raw)
On sparc-sun-solaris 2.5.1, for 971031 configured --enable-shared,
I get the following errors from the libstdc++ tests:
/remote/dtg103/jbuck/gnu/src/egcs-971031/gcc/xgcc -B/remote/dtg103/jbuck/gnu/src/egcs-971031/gcc/ -g -O2 -fno-implicit-templates -h libstdc++.so.2.8.0 -shared -o libstdc++.so.2.8.0 `cat piclist` -lm
ld: fatal: file pic/cstrmain.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x52cdf
ld: fatal: file pic/stdexcepti.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x54e97
ld: fatal: file ../libio/pic/filebuf.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x553f3
ld: fatal: file ../libio/pic/fstream.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x55673
ld: fatal: file ../libio/pic/procbuf.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x56ca7
ld: fatal: file ../libio/pic/stdiostream.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x56e4b
ld: fatal: file ../libio/pic/stream.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x5713f
ld: fatal: file ../libio/pic/strstream.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x57e93
ld: fatal: file ../libio/pic/parsestream.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x5879b
ld: fatal: file ../libio/pic/pfstream.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x58adb
ld: fatal: file ../libio/pic/editbuf.o: section .eh_frame: an output relocation [R_SPARC_RELATIVE] against symbol `__EXCEPTION_TABLE__' would be created against a non-aligned offset: 0x58bd3
collect2: ld returned 1 exit status
make: *** [libstdc++.so.2.8.0] Error 1
next reply other threads:[~1997-11-01 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-01 13:42 Joe Buck [this message]
[not found] <199711012142.NAA27180.cygnus.egcs@atrus.synopsys.com>
1997-11-01 16:05 ` Jason Merrill
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=199711012142.NAA27180@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
/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).