From: Andrew Cagney <ac131313@redhat.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: Nathanael Nerode <neroden@gcc.gnu.org>,
Nick Clifton <nickc@redhat.com>,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: top level makefile.in
Date: Tue, 01 Oct 2002 08:36:00 -0000 [thread overview]
Message-ID: <3D99C0F0.50407@redhat.com> (raw)
In-Reply-To: <20021001163755.M25369@bubble.sa.bigpond.net.au>
> On Mon, Sep 30, 2002 at 11:46:52PM -0400, Andrew Cagney wrote:
>
>> Per my reply to Nathaniel, the proposed fix to all this is currently
>> waiting on a clear to go, from binutils.
>
>
> OK, go! Maybe I'm dreaming, but once upon a time didn't the
> "configure" and "make info" etc. occur in a separate directory?
> ie. not generate a whole lot of rubbish in your cvs repo..
It must be a very very long time ago.
For longer than I can remember, the release scripts have run in the
source directory. This is so that all the generated droppings are left
in that same directory. The final pass is something like a ``make
distclean'' which should tidy things up. If the distro contains rubish,
its a bug in that target.
Andrew
next parent reply other threads:[~2002-10-01 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021001104833.E25369@bubble.sa.bigpond.net.au>
[not found] ` <20021001012213.GA16275@nevyn.them.org>
[not found] ` <20021001114136.F25369@bubble.sa.bigpond.net.au>
[not found] ` <3D991AAC.4010207@redhat.com>
[not found] ` <20021001163755.M25369@bubble.sa.bigpond.net.au>
2002-10-01 8:36 ` Andrew Cagney [this message]
2002-10-01 8:51 ` Andrew Cagney
2002-10-01 15:50 ` Nathanael Nerode
2002-10-01 16:13 ` Andrew Cagney
2002-10-01 16:24 ` Nathanael Nerode
2002-10-01 19:40 ` Andrew Cagney
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=3D99C0F0.50407@redhat.com \
--to=ac131313@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=neroden@gcc.gnu.org \
--cc=nickc@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