From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
Cc: DJ Delorie <dj@redhat.com>,
binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix in-srcdir build of gcc
Date: Sun, 27 Feb 2005 00:23:00 -0000 [thread overview]
Message-ID: <42204408.2050908@lu.unisi.ch> (raw)
In-Reply-To: <42203256.6040108@lu.unisi.ch>
> I am too. Unfortunately this patch on one hand makes ./configure work
> for gcc, on the other hand it makes it more "surprising" for
> binutils/gdb. I am especially concerned about gdb, because of the two
> it is the one that is most likely to be built by casual users doing
> "./configure && make".
The symbolic link confuses the fixincludes makefile.
What about making the patch create an host-subdir only when gcc is present?
Paolo
prev parent reply other threads:[~2005-02-26 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 16:12 Paolo Bonzini
2005-02-25 16:34 ` Daniel Jacobowitz
2005-02-25 20:34 ` Paolo Bonzini
2005-02-25 19:44 ` Joseph S. Myers
2005-02-25 21:22 ` DJ Delorie
2005-02-26 19:36 ` Paolo Bonzini
2005-02-27 0:23 ` Paolo Bonzini [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=42204408.2050908@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@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