| To: | Eric Sandeen <sandeen@xxxxxxx> |
|---|---|
| Subject: | Re: kgcc now required ?? |
| From: | Christoph Hellwig <hch@xxxxxxxxxx> |
| Date: | Sun, 11 Feb 2001 18:37:19 +0100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <3A86C9FC.EE891A9@xxxxxxx>; from sandeen@xxxxxxx on Sun, Feb 11, 2001 at 11:21:00AM -0600 |
| References: | <kszysiu@xxxxxxxxxxxx> <200102111503.f1BF3lH19265@xxxxxxxxxxxxxxxxxxxx> <20010211180214.J16362@xxxxxxx> <3A86C9FC.EE891A9@xxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Sun, Feb 11, 2001 at 11:21:00AM -0600, Eric Sandeen wrote:
> Jens Axboe wrote:
>
> > But can we at least get a decent work-around, that doesn't barf
> > if kgcc isn't available? It seems rather silly to assume gcc
> > is borken.
>
> As of 2.4.0, the official Makefile uses:
>
> CC :=$(shell if which $(CROSS_COMPILE)kgcc > /dev/null 2>&1; then echo
> $(CROSS_COMPILE)kgcc; else echo $(CROSS_COMPILE)gcc; fi) -D__KERNEL__
> -I$(HPATH)
No - you seem to use some patched (-ac?) tree.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: kgcc now required ??, Eric Sandeen |
|---|---|
| Next by Date: | Re: Unresolved Symbols problem w/ 2.4.1-XFS cvs, Slawomir Pol |
| Previous by Thread: | Re: kgcc now required ??, Eric Sandeen |
| Next by Thread: | Re: kgcc now required ??, Russell Cattelan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |