From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Olaf Hering <olh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cc-version not available to change EXTRA_CFLAGS
Date: Sat, 21 Jan 2006 22:47:12 +0300 [thread overview]
Message-ID: <200601212247.14101.arvidjaar@mail.ru> (raw)
In-Reply-To: <20060121191140.GA17661@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 21 January 2006 22:11, Olaf Hering wrote:
> On Sat, Jan 21, Andrey Borzenkov wrote:
> > does chmod +x scripts/gcc-version.sh help?
>
> no, cc-version is not expanded in this context.
well it does in this trivial test:
cc-version = $(shell foo/baz 2234)
FOO = $(shell set -x; if [ $(cc-version) -lt 2000 ] ; then echo y; else echo
n; fi)
bar:
echo $(FOO)
I get exactly the same result if foo/baz is not executable or returns empty
string (in the former case I also get error message from make but may be it
is supressed, I never fully groked kernel Makefiles).
So again - does scripts/gcc-version.sh returns any usable value? Is it
executable?
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD4DBQFD0o/CR6LMutpd94wRAjuFAJj2Ov4Z2iVxamYY/IxkLzOGRb1fAJwIBOxt
aH91icTk8dTKzO/VzLjlLA==
=DNXC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-01-21 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 19:07 cc-version not available to change EXTRA_CFLAGS Andrey Borzenkov
2006-01-21 19:11 ` Olaf Hering
2006-01-21 19:47 ` Andrey Borzenkov [this message]
2006-01-21 21:07 ` Olaf Hering
2006-01-21 22:51 ` Jan Engelhardt
2006-01-21 23:00 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 18:08 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
2006-07-23 17:51 ` 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=200601212247.14101.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.