public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: cc-version not available to change EXTRA_CFLAGS
Date: Wed, 19 Jul 2006 11:02:04 +0200	[thread overview]
Message-ID: <20060719090204.GA4980@suse.de> (raw)
In-Reply-To: <20060121180805.GA15761@suse.de>

 On Sat, Jan 21, Olaf Hering wrote:

> 
> I want to add a gcc version check for reiserfs, on akpms request.

This debug patch still doesnt work in 2.6.18-rc2:


make -kj 14 O=$O

scripts/gcc-version.sh: line 11: _c_flags: command not found
scripts/gcc-version.sh: line 12: _c_flags: command not found
+ '[' 0000 -lt 0500 ']'
+ echo -O1


---
 fs/reiserfs/Makefile |    1 +
 1 file changed, 1 insertion(+)

Index: linux-2.6.18-rc2/fs/reiserfs/Makefile
===================================================================
--- linux-2.6.18-rc2.orig/fs/reiserfs/Makefile
+++ linux-2.6.18-rc2/fs/reiserfs/Makefile
@@ -30,6 +30,7 @@ endif
 ifeq ($(CONFIG_PPC32),y)
 EXTRA_CFLAGS := -O1
 endif
+EXTRA_CFLAGS += $(shell set -x ; if [ $(call cc-version) -lt 0500 ] ; then echo -O1 ; fi ;)
 
 TAGS:
 	etags *.c

  parent reply	other threads:[~2006-07-19  9:02 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
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 [this message]
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=20060719090204.GA4980@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