From: "David S. Miller" <davem@caip.rutgers.edu>
To: gas2@cygnus.com
Subject: assertion failures under sunos on the sparc
Date: Mon, 27 Nov 1995 17:02:00 -0000 [thread overview]
Message-ID: <199511280102.UAA22199@huahaga.rutgers.edu> (raw)
It seems that if you interrupt a build of a tree halfway through, and
make doesn't clean up the half-written .o file properly, later on when
you link the screen fills with a monsterous amount of 'bfd-assertion
failure bfd/sunos.c'. I get about 400 of them for the linux kernel
when this happens.
The error message is warranted because the linker is processing bogus
information, however this amount of verbosity is very overwhelming to
the user. Is there a way to inform the user which object file is the
corrupt one instead during examination of objects in bfd? If so, this
would be more useful than what happen currently.
This is with binutils-2.6
Later,
David S. Miller
davem@caip.rutgers.edu
next reply other threads:[~1995-11-27 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-27 17:02 David S. Miller [this message]
1995-11-27 18:30 ` Richard Stallman
1995-11-27 18:35 ` David S. Miller
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=199511280102.UAA22199@huahaga.rutgers.edu \
--to=davem@caip.rutgers.edu \
--cc=gas2@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).