From: Randy Dunlap <randy.dunlap@oracle.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-devel@lists.sourceforge.net
Subject: Re: [PATCH 05/19] kbuild: document cc-fullversion
Date: Sun, 3 Jun 2007 15:34:19 -0700 [thread overview]
Message-ID: <20070603153419.be0bcf91.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070603204603.GE9240@uranus.ravnborg.org>
On Sun, 3 Jun 2007 22:46:03 +0200 Sam Ravnborg wrote:
> Subject: [PATCH 05/19] kbuild: document cc-fullversion
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Mon, 28 May 2007 22:26:55 +0200
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.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 ***
prev parent reply other threads:[~2007-06-03 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 20:46 Sam Ravnborg
2007-06-03 22:34 ` Randy Dunlap [this message]
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=20070603153419.be0bcf91.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-devel@lists.sourceforge.net \
--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®