From: "David S. Miller" <davem@caip.rutgers.edu>
To: rms@gnu.ai.mit.edu
Cc: gas2@cygnus.com
Subject: Re: assertion failures under sunos on the sparc
Date: Mon, 27 Nov 1995 18:35:00 -0000 [thread overview]
Message-ID: <199511280235.VAA11911@huahaga.rutgers.edu> (raw)
In-Reply-To: <199511280230.VAA19387@mole.gnu.ai.mit.edu>
Date: Mon, 27 Nov 1995 21:30:28 -0500
From: Richard Stallman <rms@gnu.ai.mit.edu>
CC: gas2@cygnus.com
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,
How come Make doesn't do that? Make is supposed to delete the current
target if you kill it after that target has been altered.
I severly apologize, it now seems that I am getting bfd assertion
failures like mad even for what appears to be correct builds of my
sources. This is with gcc-2.7.1 and binutils-2.6 on the sparc under
SunOS.
For all I know, make was doing the correct thing.
I will hunt this down some more, it looks pretty bad.
Later,
David S. Miller
davem@caip.rutgers.edu
prev parent reply other threads:[~1995-11-27 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-27 17:02 David S. Miller
1995-11-27 18:30 ` Richard Stallman
1995-11-27 18:35 ` David S. Miller [this message]
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=199511280235.VAA11911@huahaga.rutgers.edu \
--to=davem@caip.rutgers.edu \
--cc=gas2@cygnus.com \
--cc=rms@gnu.ai.mit.edu \
/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).