From: Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk>
To: Dave Korn <dk@artimi.com>
Cc: "'Binutils list'" <binutils@sources.redhat.com>
Subject: RE: "already configured" for dejagnu after gmake distclean.
Date: Mon, 29 Mar 2004 18:53:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0403291810010.8601@brains> (raw)
In-Reply-To: <NUTMEGpCnJ711HZv7FD00000293@NUTMEG.CAM.ARTIMI.COM>
On Mon, 29 Mar 2004, Dave Korn wrote:
>
> > -----Original Message-----
> > From: Hugh Sasse Staff Elec Eng
> > Sent: 29 March 2004 16:48
>
> > > state; you must have not distcleaned between the two
> > configures, and
> > > now you have makefiles
> >
> > I am absolutely positive that I did that distclean in
> > between, forseeing this problem if I didn't. It is well over
> > a week ago though, and I don't have any evidence lying around
> > to prove this.
>
> Well, it pretty much has to be the case; the evidence is all those
> generated files that were showing up as being in your source tree when you
> did the cvs update. Every single one of those lines beginning '?' should
> not have been there. Perhaps you did the reconfigure, then belatedly
> remembered about distclean and ran it, then re-reconfigured; if you'd
I don't think so, because I know that configure creates the
makefiles that would be used by the subsequent make.
> already started the reconfigure, however, it might have already rewritten
> the makefiles so that by the time you did the distclean it was deleting
> stuff from the object dir not the source dir. It's hard to know how it
> first went wrong, but that's certainly the state it ended up in.
>
> > > in the source tree. In theory, configure could be
> > protected against
> > > this, detect when generated files were found in the source
> > tree, and
> > > automatically do a distclean itself, but people don't often tend to
> > > switch from the one style of building to the other, so it
> > hasn't been done.
> >
> > I'd suggest that this is more common than might be thought,
> > because it is one of the often-suggested remedies to an
[...]
>
> I'm in full agreement with you. AFAIC configure should flat-out refuse to
> run in the source tree. It's nothing but a source of trouble and confusion.
> It could even be the case that 'make distclean' has a bug in it and hasn't
> been working properly when run in the source dir for some time, but nobody's
> noticed....
Would it be of any help to test this out, and point people at the
results? I'm willing to do that.
>
>
> cheers,
> DaveK
prev parent reply other threads:[~2004-03-29 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 15:57 Hugh Sasse Staff Elec Eng
2004-03-25 19:53 ` Dave Korn
2004-03-29 16:46 ` Hugh Sasse Staff Elec Eng
2004-03-29 18:00 ` Dave Korn
2004-03-29 18:53 ` Hugh Sasse Staff Elec Eng [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=Pine.GSO.4.58.0403291810010.8601@brains \
--to=hgs@dmu.ac.uk \
--cc=binutils@sources.redhat.com \
--cc=dk@artimi.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).