From: José Mê Pérez Cáncer <jose.perez@upcnet.es>
To: "binutils@sourceware.cygnus.com" <binutils@sourceware.cygnus.com>
Cc: Alan Modra <amodra@bigpond.net.au>, "H . J . Lu" <hjl@lucon.org>
Subject: Re: /usr/bin/ld: bfd assertion fail elf32-i386.c:1816
Date: Wed, 01 Aug 2001 11:05:00 -0000 [thread overview]
Message-ID: <3B683516.48406CC@upcnet.es> (raw)
In-Reply-To: <20010801230210.D5233@bubble.sa.bigpond.net.au>
Alan Modra wrote:
>
> You may like to try H.J. Lu's latest binutils too.
> ftp://ftp.kernel.org/pub/linux/devel/binutils/
>
> Alan
I changed my binutils to version 2.11.90.0.25 and recompiled the code
and got the same problem, but this time the linker aborted and gave a
bit more info:
/usr/bin/ld: BFD internal error, aborting at elf32-i386.c line 1916 in
elf_i386_finish_dynamic_symbol
/usr/bin/ld: Please report this bug.
JM
next prev parent reply other threads:[~2001-08-01 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 5:18 José Mª Pérez Cáncer
2001-08-01 6:32 ` Alan Modra
2001-08-01 11:05 ` José Mª Pérez Cáncer [this message]
2001-08-01 11:13 ` H . J . Lu
2001-08-01 8:45 ` H . J . Lu
2001-08-08 6:47 ` Harshad R Joglekar
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=3B683516.48406CC@upcnet.es \
--to=jose.perez@upcnet.es \
--cc=amodra@bigpond.net.au \
--cc=binutils@sourceware.cygnus.com \
--cc=hjl@lucon.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).