From: Olaf Hering <olh@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cc-version not available to change EXTRA_CFLAGS
Date: Sun, 22 Jan 2006 00:15:39 +0100 [thread overview]
Message-ID: <20060121231539.GA23789@suse.de> (raw)
In-Reply-To: <20060121225728.GA13756@mars.ravnborg.org>
On Sat, Jan 21, Sam Ravnborg wrote:
> Let me know if this works for you.
Works perfect, beside this minor glitch.
Warning: trailing whitespace in line 1067 of
Documentation/kbuild/makefiles.txt
> > ifeq ($(CONFIG_PPC32),y)
> > -EXTRA_CFLAGS := -O1
> > +EXTRA_CFLAGS := $(shell set -x ; if [ $(call cc-version) -lt 0402 ] ; then echo $(call cc-option,-O1); fi ;)
>
> For -O1 I do not see the point in using $(call cc-option ...).
> I assume all gcc version does support -O1 - or?
this was just c&p during debug, from another file.
> + Example:
> + #fs/reiserfs/Makefile
> + EXTRA_CFLAGS := $(call cc-ifversion, -lt, 0402, -O1)
> +
> + In this example EXTRA_CFLAGS will be assigned the value -O1 if the
> + $(CC) version is less than 4.2.
I meant 4.0.2 as shipped with SuSE 10.0, but thats ok. I think the buggy
version was 3.2, as we have not seen in with gcc 3.3-hammer in SLES9.
Will you include the reiserfs change with a check for earlier then 4.0
or 4.1 or should I send a separate patch?
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2006-01-21 23:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 18:08 cc-version not available to change EXTRA_CFLAGS Olaf Hering
2006-01-21 22:12 ` Sam Ravnborg
2006-01-21 22:21 ` Olaf Hering
2006-01-21 22:57 ` Sam Ravnborg
2006-01-21 23:15 ` Olaf Hering [this message]
2006-01-21 23:25 ` Sam Ravnborg
2006-01-23 11:02 ` Olaf Hering
2006-02-10 19:47 ` Olaf Hering
2006-02-18 9:03 ` Sam Ravnborg
2006-07-19 9:02 ` Olaf Hering
2006-07-23 17:51 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 19:07 Andrey Borzenkov
2006-01-21 19:11 ` Olaf Hering
2006-01-21 19:47 ` Andrey Borzenkov
2006-01-21 21:07 ` Olaf Hering
2006-01-21 22:51 ` Jan Engelhardt
2006-01-21 23:00 ` 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=20060121231539.GA23789@suse.de \
--to=olh@suse.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