[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20070603153419.be0bcf91.randy.dunlap@oracle.com>
Date: Sun, 3 Jun 2007 15:34:19 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Sam Ravnborg <sam@...nborg.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
kbuild-devel@...ts.sourceforge.net
Subject: Re: [PATCH 05/19] kbuild: document cc-fullversion
On Sun, 3 Jun 2007 22:46:03 +0200 Sam Ravnborg wrote:
> Subject: [PATCH 05/19] kbuild: document cc-fullversion
> From: Sam Ravnborg <sam@...nborg.org>
> Date: Mon, 28 May 2007 22:26:55 +0200
>
> Signed-off-by: Sam Ravnborg <sam@...nborg.org>
> ---
> Documentation/kbuild/makefiles.txt | 14 ++++++++++++++
> 1 files changed, 14 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/kbuild/makefiles.txt b/Documentation/kbuild/makefiles.txt
> index bb5306e..c6d9a35 100644
> --- a/Documentation/kbuild/makefiles.txt
> +++ b/Documentation/kbuild/makefiles.txt
> @@ -501,6 +501,20 @@ more details, with real examples.
> The third parameter may be a text as in this example, but it may also
> be an expanded variable or a macro.
>
> + cc-fullversion
> + cc-fullversion is usefull when the exact version of gcc is needed.
useful
> + One typical use-case is when a specific GCC version is broken.
> + cc-fullversion points out a more specific version than cc-version does.
> +
> + Example:
> + #arch/powerpc/Makefile
> + $(Q)if test "$(call cc-fullversion)" = "040200" ; then \
> + echo -n '*** GCC-4.2.0 cannot compile the 64-bit powerpc ' ; \
> + false ; \
> + fi
> +
> + In this example for a specific GCC version the build will error out explaining
> + the user why it stops.
to the user why it stops.
>
> === 4 Host Program support
>
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists