public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	kai@tp1.ruhr-uni-bochum.de, greg@kroah.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] klibc for 2.5.59 bk
Date: Mon, 17 Feb 2003 14:24:41 -0500	[thread overview]
Message-ID: <3E5136F9.9090709@pobox.com> (raw)
In-Reply-To: <20030217185700.GA27610@mars.ravnborg.org>

Sam Ravnborg wrote:
> On Mon, Feb 17, 2003 at 01:36:59PM -0500, Jeff Garzik wrote:
> 
>> 
>>+check_gcc = $(shell if $(CC) $(1) -S -o /dev/null -xc /dev/null > /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
> 
> 
> Will check_gcc be compatible across architectures?


s/will/is/   Yes.

	Jeff




  reply	other threads:[~2003-02-17 19:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  4:59 [RFC] klibc for 2.5.59 bk Greg KH
2003-02-07  5:06 ` H. Peter Anvin
2003-02-07  5:10   ` Greg KH
2003-02-07 15:00 ` Alex Riesen
2003-02-09 12:57   ` Greg KH
2003-02-17  3:06     ` Kai Germaschewski
2003-02-17  5:50       ` Jeff Garzik
2003-02-17 18:02       ` Sam Ravnborg
2003-02-17 18:07         ` H. Peter Anvin
2003-02-17 18:36           ` Jeff Garzik
2003-02-17 18:57             ` Sam Ravnborg
2003-02-17 19:24               ` Jeff Garzik [this message]
2003-02-18  8:58             ` H. Peter Anvin
2003-02-18  9:17               ` Jeff Garzik
2003-02-18  9:36                 ` Stelian Pop
2003-02-18  9:37                   ` Stelian Pop
2003-02-18  9:46                     ` Jeff Garzik
2003-02-18  9:45                   ` Jeff Garzik
2003-02-18  9:56                     ` Stelian Pop
     [not found] <20030217031008$3e63@gated-at.bofh.it>
     [not found] ` <20030217031008$270a@gated-at.bofh.it>
2003-02-17 17:12   ` Arnd Bergmann

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=3E5136F9.9090709@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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