From: DJ Delorie <dj@redhat.com>
To: zack@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: Obsolete building in source dir?
Date: Tue, 14 Sep 2004 22:25:00 -0000 [thread overview]
Message-ID: <200409142017.i8EKHtqJ018574@greed.delorie.com> (raw)
In-Reply-To: <87u0u0d35y.fsf@codesourcery.com> (message from Zack Weinberg on Tue, 14 Sep 2004 13:08:25 -0700)
> This raises the question of why gcc has the problem and the other
> projects don't.
I suspect it's because gcc is the only project where the organization
of the build tree doesn't match the organization of the source tree.
Between host/build/target modules and multilibs, we move stuff around
a lot. Keeping track of where we put it is where we lose the most. I
suspect that making srcdir absolute will fix most of the hard
problems, and we can conditional that on finding gcc in the source
tree.
if [ -d $srcdir/gcc ]
then
srcdir=`cd $srcdir; $PWDCMD`
fi
Similarly for the build directory. The down side is that you can't
move a build any more, but I've found that to be true already.
next prev parent reply other threads:[~2004-09-14 20:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 4:06 Giovanni Bajo
2004-09-13 7:34 ` DJ Delorie
2004-09-14 19:21 ` Joe Buck
2004-09-14 19:40 ` Zack Weinberg
2004-09-14 19:59 ` Joseph S. Myers
2004-09-14 20:12 ` DJ Delorie
2004-09-14 21:25 ` Zack Weinberg
2004-09-14 22:25 ` DJ Delorie [this message]
2004-09-26 23:05 ` Marc Espie
2004-09-28 17:38 ` Per Bothner
2004-09-15 11:09 ` Richard Earnshaw
2004-09-15 15:43 ` DJ Delorie
2004-09-15 16:16 ` Richard Earnshaw
2004-09-15 16:58 ` Phil Edwards
2004-09-15 21:15 ` Alexandre Oliva
2004-09-16 5:59 ` Ralf Corsepius
2004-09-16 16:47 ` DJ Delorie
2004-09-17 11:08 ` Ralf Corsepius
2004-09-17 21:12 ` DJ Delorie
2004-09-17 16:38 ` Alexandre Oliva
2004-09-18 15:14 ` Kai Henningsen
2004-09-18 17:31 ` Alexandre Oliva
2004-09-19 18:41 ` Kai Henningsen
2004-09-20 8:51 ` Ralf Corsepius
2004-09-16 22:01 ` Matthias B.
2004-09-14 20:08 ` DJ Delorie
2004-09-14 20:18 ` Joe Buck
[not found] ` <mailman.80195.1095191985.18468.gnu-gcc@lists.nsr.labs.mot.com>
2004-09-15 6:38 ` Loren James Rittle
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=200409142017.i8EKHtqJ018574@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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).