mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] Doc/kbuild/makefiles.txt: check_gcc -> cc-option
Date: Wed, 27 Oct 2004 22:25:07 +0200	[thread overview]
Message-ID: <20041027202507.GB2713@stusta.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It's not good to show the obsolete check_gcc in an example.


Signed-off-by: Adrian Bunk <bunk@stusta.de>

- --- linux-2.6.10-rc1-mm1-full/Documentation/kbuild/makefiles.txt.old	2004-10-27 19:58:24.000000000 +0200
+++ linux-2.6.10-rc1-mm1-full/Documentation/kbuild/makefiles.txt	2004-10-27 20:03:24.000000000 +0200
@@ -707,15 +707,17 @@
 	probe supported options:
 
 		#arch/i386/Makefile
- -		check_gcc = $(shell if $(CC) $(1) -S -o /dev/null -xc \
- -		            /dev/null\ > /dev/null 2>&1; then echo "$(1)"; \
- -		            else echo "$(2)"; fi)
- -		cflags-$(CONFIG_MCYRIXIII) += $(call check_gcc,\
- -		                                     -march=c3,-march=i486)
 
- -		CFLAGS += $(cflags-y)
+		...
+		cflags-$(CONFIG_MPENTIUMII)     += $(call cc-option,\
+						-march=pentium2,-march=i686)
+		...
+		# Disable unit-at-a-time mode ...
+		CFLAGS += $(call cc-option,-fno-unit-at-a-time)
+		...
 
- -	The above examples both utilise the trick that a config option expands
+
+	The first examples utilises the trick that a config option expands
 	to 'y' when selected.
 
     CFLAGS_KERNEL	$(CC) options specific for built-in

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBgAQjmfzqmE8StAARAlpgAJwMs91KxFXt6J5CMIxX7CBmU+ck2QCggOtq
79uRYePvlHJEQ+lSKgNzzdQ=
=o4Vo
-----END PGP SIGNATURE-----

             reply	other threads:[~2004-10-27 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 20:25 Adrian Bunk [this message]
2004-10-30 22:18 ` Sam Ravnborg

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=20041027202507.GB2713@stusta.de \
    --to=bunk@stusta.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

all inboxes | Powered by JetHome®