public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mitch Adair <mitch@theneteffect.com>
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.19pre3
Date: Thu, 21 Dec 2000 21:40:17 -0600 (CST)	[thread overview]
Message-ID: <200012220340.VAA14005@mako.theneteffect.com> (raw)
In-Reply-To: <E149GRm-0003sX-00@the-village.bc.nu> from "Alan Cox" at Dec 22, 2000 12:52:32 AM

> 2.2.19pre3
[snip]
> o	Optimise kernel compiler detect, kgcc before	(Peter Samuelson)
> 	gcc272 also

I get an endless stream of this:

kgcc:gcc272:cc:gcc: not found
kgcc:gcc272:cc:gcc: not found
/bin/sh: -D__KERNEL__: command not found
/bin/sh: -D__KERNEL__: command not found
/bin/sh: -D__KERNEL__: command not found
/bin/sh: -D__KERNEL__: command not found


I think the Makefile optimisation needs to be (cut-n-paste):

--- Makefile~   Thu Dec 21 21:35:39 2000
+++ Makefile    Thu Dec 21 21:35:54 2000
@@ -28,7 +28,7 @@
 #      gcc272 for Debian
 #      otherwise 'cc'
 #
-CCFOUND :=$(shell $(CONFIG_SHELL) scripts/kwhich kgcc gcc272 cc gcc)
+CCFOUND :=$(shell $(CONFIG_SHELL) scripts/kwhich kgcc:gcc272:cc:gcc)
 ## Faster, but requires GNU make 3.78, which postdates Linux 2.2.0
 ##CC   =$(if $(CROSS_COMPILE),$(CROSS_COMPILE)gcc,$(CCFOUND)) -D__KERNEL__ -I$(HPATH)
 CC     =$(shell if [ -n "$(CROSS_COMPILE)" ]; then echo $(CROSS_COMPILE)gcc; else echo $(CCFOUND); fi) \


	M
(what's the old saying - the first rule of optimization is don't or
something like that... ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-22  4:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-22  0:52 Linux 2.2.19pre3 Alan Cox
2000-12-22  3:40 ` Mitch Adair [this message]
2000-12-22 15:32 ` Petri Kaukasoina
2000-12-22 15:53   ` Richard B. Johnson
2000-12-22 16:02     ` Chad Schwartz
2000-12-22 16:23       ` Alan Cox
2000-12-22 16:25         ` Chad Schwartz
2000-12-22 16:43         ` Richard B. Johnson
2000-12-22 17:54     ` Miquel van Smoorenburg
2000-12-22 18:13       ` Richard B. Johnson
2000-12-22 16:21   ` Alan Cox
2000-12-22 19:33 ` Petri Kaukasoina
2000-12-22 19:56   ` Andrea Arcangeli
2000-12-23 12:05 ` Willy Tarreau
2000-12-28  1:18 ` Matthias Andree
2000-12-28  2:37   ` Alan Cox
2000-12-28 10:23     ` Matthias Andree
2000-12-28 12:20       ` Alan Cox
2000-12-28 13:53         ` Linux 2.2.18: /proc/apm slows system time (was: Linux 2.2.19pre3) Matthias Andree
2000-12-28 14:14           ` Matthias Andree
2000-12-29 12:42           ` Erik Mouw
2000-12-30 12:39             ` Matthias Andree
2000-12-30 17:01               ` Alan Cox
2000-12-30 17:38                 ` Erik Mouw
2000-12-30 17:50                   ` Alan Cox
2000-12-30 17:39                 ` Matthias Andree
2000-12-31 10:34                 ` Matthias Andree
2000-12-31 11:28                   ` Chris Wedgwood
2000-12-31 13:32                     ` Alan Cox
2001-01-02 13:52                       ` [PATCH] CMOS locking for 2.4 (was: /proc/apm slows system time) Paul Gortmaker
2000-12-31 13:37                   ` Linux 2.2.18: /proc/apm slows system time (was: Linux 2.2.19pre3) Alan Cox
2000-12-31 15:50                     ` Erik Mouw
2000-12-31 16:13                       ` Alan Cox
2001-01-02 16:32                     ` Matthias Andree
2001-01-02 17:31                       ` Alan Cox
2001-01-03 22:02                         ` Matthias Andree
2000-12-28 11:14     ` Linux 2.2.19pre3 Guest section DW

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=200012220340.VAA14005@mako.theneteffect.com \
    --to=mitch@theneteffect.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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