From: Christopher Faylor <me@cgf.cx>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Make lack of gcc directory non-fatal again in Makefile.tpl
Date: Thu, 03 Jun 2004 05:13:00 -0000 [thread overview]
Message-ID: <20040603045058.GA23869@coe.casa.cgf.cx> (raw)
In-Reply-To: <20040603040247.GA2053@nevyn.them.org>
On Thu, Jun 03, 2004 at 12:02:47AM -0400, Daniel Jacobowitz wrote:
>On Wed, Jun 02, 2004 at 11:31:58PM -0400, Christopher Faylor wrote:
>>
>> Somewhere in the last few days the behavior of the top-level Makefile
>> seems to have changed such that it dies if there is no gcc directory.
>> I'm not 100% sure that this is the correct way to fix this problem but
>> the patch below rectifies that behavior.
>>
>> Ok to apply?
>
>I don't think it went to gcc-patches, but Paolo posted an (I think)
>better fix for this to binutils and gdb-patches. He's away and can't
>check it in...
Hmm. I specifically checked gcc-patches since that's where I thought
the master for this file resided.
I'll check in Paolo's patch as soon as I can resurrect a clean copy.
cgf
prev parent reply other threads:[~2004-06-03 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 4:51 Christopher Faylor
2004-06-03 5:00 ` Daniel Jacobowitz
2004-06-03 5:13 ` Christopher Faylor [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=20040603045058.GA23869@coe.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gcc-patches@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).