public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mohan Embar <gnustuff@thisiscool.com>
To: Zack Weinberg <zack@codesourcery.com>, Kelley Cook <kcook@gcc.gnu.org>
Cc: gcc@gcc.gnu.org, neroden@twcny.rr.com
Subject: Re: Parallel make also broken now...
Date: Tue, 07 Sep 2004 19:45:00 -0000	[thread overview]
Message-ID: <XRVPFE42MSQICJI61FC07761YKHWU4Y.413e1065@p733> (raw)
In-Reply-To: <413DFB10.8070009@gcc.gnu.org>

Hi Kelley,

>If so it is, as far as I can guess, the same apparent gmake bug that prevented me 
>from committing an essentially approved patch which IMO would have had a side 
>effect of solving Mohan's gcc-none.o problem more elegantly than his patch does.

>http://gcc.gnu.org/ml/gcc-patches/2004-08/msg02155.html

When you say "his patch", which patch are you referring to? I rescinded this one:

http://gcc.gnu.org/ml/gcc-patches/2004-09/msg00550.html

...and the second one:

http://gcc.gnu.org/ml/gcc-patches/2004-09/msg00586.html

...merely reintroduces #include "config.h" to ggc-none.c, which we'd need to
do anyway given that the host-specific build  of ggc-none.o was removed here
(cf. item 5):

http://gcc.gnu.org/ml/gcc-patches/2004-08/msg00265.html

-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/




      parent reply	other threads:[~2004-09-07 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06 16:18 Steven Bosscher
2004-09-06 16:53 ` Zack Weinberg
2004-09-06 18:40   ` Steven Bosscher
2004-09-07 18:16     ` Kelley Cook
2004-09-07 18:52       ` Zack Weinberg
2004-09-07 18:54       ` Mohan Embar
2004-09-07 19:45       ` Mohan Embar [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=XRVPFE42MSQICJI61FC07761YKHWU4Y.413e1065@p733 \
    --to=gnustuff@thisiscool.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kcook@gcc.gnu.org \
    --cc=neroden@twcny.rr.com \
    --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).