From: Harri Pasanen <harri.pasanen@trema.com>
To: gcc-help@gcc.gnu.org
Subject: gcc 3.4.3 bootstrap fails on hppa64-hp-hpux11.11
Date: Fri, 19 Nov 2004 13:48:00 -0000 [thread overview]
Message-ID: <200411191445.24743.harri.pasanen@trema.com> (raw)
Hi,
With
../gcc-3.4.3/configure -enable-languages=c,c++ --enable-threads=posix
--disable-nls --with-gnu-as --with-as=/opt/gcc34-64/bin/as
--with-ld=/usr/ccs/bin/ld --enable-shared --prefix=/opt/gcc34-64
--host=hppa64-hp-hpux11.11 --disable-checking
make bootstrap
fails eventually with
stage1/xgcc -Bstage1/ -B/opt/gcc34-64/hppa64-hp-hpux11.11/bin/ -g
-O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition
-DHAVE_CONFIG_H -DGENERATOR_FILE -o genmodes \
genmodes.o errors.o ../libiberty/libiberty.a
ld: Unable to load shared library "/opt/langtools/lib/libcomp.sl"
Fatal error.
collect2: ld returned 1 exit status
This is apparantly something related to HP linker,
as /opt/langtools/lib/libcomp.sl is something that is only available
if the commercial C compiler for HP-UX is installed.
???
-Harri
This message, including any attachments, is intended only for the person(s) to whom it is addressed. If you received it in error, please let us know and delete the message from your system. This message may be confidential and may fall under the duty of non-disclosure. Any use by others than the intended addressee is prohibited. Trema shall not be liable for any damage related to the electronic transmission of this message, such as failure or delay of its delivery, interception or manipulation by third parties, or transmission of viruses or other malicious code.
reply other threads:[~2004-11-19 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200411191445.24743.harri.pasanen@trema.com \
--to=harri.pasanen@trema.com \
--cc=gcc-help@gcc.gnu.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 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).