From: Ralf Corsepius <rc040203@freenet.de>
To: DJ Delorie <dj@redhat.com>
Cc: GCC List <gcc@gcc.gnu.org>
Subject: Re: Obsolete building in source dir?
Date: Fri, 17 Sep 2004 11:08:00 -0000 [thread overview]
Message-ID: <1095402723.4989.643.camel@mccallum.corsepiu.local> (raw)
In-Reply-To: <200409161638.i8GGc4iF000829@greed.delorie.com>
On Thu, 2004-09-16 at 18:38, DJ Delorie wrote:
> > Instead of doing this you could consider to systematically using
> > $host(_alias), $build(_alias), $target(_alias) builddir-subdirectories,
> > no matter if cross-compiling or not.
>
> Except we can't, because the toplevel machinery is shared among many
> projects. We have to be careful not to change those without their
> permission.
AFAIU, your concern only applies to subpackages which support "native
compilation only". Do such packages exist within the "uberbaum"?
I am aware about fundamental issues with adalib and about potential
issues with tcl/tk based subpackages, nevertheless all of them can be
expected to support VPATH builds, so I don't see that moving their
--srcdir would break building them.
I am aware that some configure scripts and Makefiles apply nasty tricks
such as test'ing for presence of tools in neighboring build-directories.
These checks/tests probably would require to be adapted in some cases.
Ralf
next prev parent reply other threads:[~2004-09-17 6:32 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
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 [this message]
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=1095402723.4989.643.camel@mccallum.corsepiu.local \
--to=rc040203@freenet.de \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).