From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Ugly little hack for snapshot problem
Date: Fri, 15 Aug 2003 21:20:00 -0000 [thread overview]
Message-ID: <200308152120.h7FLKVcn020381@duracef.shout.net> (raw)
First the problem:
http://sources.redhat.com/gdb/bugs/708
Can't build 5.3 branch (and probably trunk).
Here's a synopsis of the analysis:
src-release walks the tree and configures all the subdirs and
makes info files in them.
src-release walks the tree and does 'distclean' to remove
config.status and other files.
The problem is that src/dejagnu/Makefile.am is coded in an unusual
way. src/dejagnu has subdirectories, and the subdirectories are
configured normally, but Makefile.am does *not* list all the
subdirectories!
... So 'configure' configures in dejagnu/example/calc, but
'make distclean' never goes there, and the tarball gets some
extra crap in it, specifically dejagnu/example/calc/config.status.
Then the user tries to build from the tarball and gets an error that
dejagnu/example/calc has already been configured and the build chokes.
In the past, I've had two ideas for fixing this. One is to make a
simple local modification in sourceware dejagnu. In fact, Andrew C did
this before, and it worked for two years, and then Nick C imported a new
dejagnu from Savannah and our local change got erased.
The second idea is to fix dejagnu upstream and then import a new
dejagnu. I started on this but never finished it.
Now I've got a third idea. It's simple:
src-release walks the tree and configures all the subdirs ...
src-release walks the tree and makes 'distclean ...'
+ src-release calls 'rm -f dejagnu/example/calc/config.status'
Advantages:
It's very easily seen to be correct.
It's very easily seen not to touch anything except src-release.
It patches src-release, not dejagnu, so it doesn't get wiped
by a dejagnu import.
I can stick a comment in there so that if dejagnu evers gets fixed,
and we import a new dejagnu, the kludge can go away soon after that.
Disadvantages:
It's ugly.
The top-level MAINTAINERS file does not say who owns 'src-release'.
Like the cliche says: "if it's stupid, and it works, it isn't stupid."
How about it?
Michael C
next reply other threads:[~2003-08-15 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 21:20 Michael Elizabeth Chastain [this message]
2003-08-15 21:28 ` Daniel Jacobowitz
2003-08-15 21:37 Michael Elizabeth Chastain
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=200308152120.h7FLKVcn020381@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).