From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Cc: amodra@bigpond.net.au
Subject: IA64 linker is broken
Date: Sun, 30 Jan 2005 19:22:00 -0000 [thread overview]
Message-ID: <20050130192249.GA21997@lucon.org> (raw)
When bootstrapping gcc with today's binutils, I got
stage1/xgcc -Bstage1/ -B/usr/gcc-4.0/ia64-unknown-linux-gnu/bin/
-DUSE_LIBUNWIND_EXCEPTIONS -g -O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long
-Wno-variadic-macros -Wold-style-definition -Werror -DHAVE_CONFIG_H
-DGENERATOR_FILE -o build/gengenrtl \
build/gengenrtl.o build/errors.o
../build-ia64-unknown-linux-gnu/libiberty/libiberty.a
/usr/lib/crt1.o:(.dynamic+0x0): multiple definition of `_DYNAMIC'
collect2: ld returned 1 exit status
make[4]: *** [build/gengenrtl] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory `/export/build/gnu/gcc/build-ia64-linux/gcc'
make[3]: *** [stage2_build] Error 2
make[3]: Leaving directory `/export/build/gnu/gcc/build-ia64-linux/gcc'
make[2]: *** [bootstrap] Error 2
The 2005-01-24 binutils is OK. It may have something to do with
http://sources.redhat.com/ml/binutils/2005-01/msg00405.html
I will look into it on Monday.
H.J.
next reply other threads:[~2005-01-30 19:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 19:22 H. J. Lu [this message]
2005-01-31 0:02 ` Alan Modra
2005-01-31 7:13 ` Alan Modra
2005-01-31 8:29 ` Alan Modra
2005-01-31 18:38 ` H. J. Lu
2005-01-31 21:22 ` ELF " H. J. Lu
2005-01-31 22:02 ` PATCH: " H. J. Lu
2005-02-01 0:08 ` Alan Modra
2005-02-01 5:56 ` IA64 linker is totally broken (Re: PATCH: ELF linker is broken) H. J. Lu
2005-02-01 6:18 ` H. J. Lu
2005-02-01 7:16 ` Alan Modra
2005-02-01 22:46 ` H. J. Lu
2005-02-01 23:57 ` Alan Modra
2005-02-02 0:39 ` H. J. Lu
2005-02-02 1:12 ` Alan Modra
2005-02-02 1:37 ` Alan Modra
2005-02-02 2:23 ` H. J. Lu
2005-01-31 23:16 ` ELF linker is broken Alan Modra
2005-02-01 1:41 ` IA64 " Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2003-03-04 20:13 H. J. Lu
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=20050130192249.GA21997@lucon.org \
--to=hjl@lucon.org \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.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).