Skip to contentSkip to conversation

cc-version not available to change EXTRA_CFLAGS

DISCUSSION Andrey Borzenkov 4 participants 6 messages Jan 21, 2006

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 11 lines

make -kj14 O=../O-powerpc-ppc64-defconfig arch/powerpc/mm/mem.o
GEN /home/olaf/kernel/olh/ppc64/O-powerpc-ppc64-defconfig/Makefile
scripts/kconfig/conf -s arch/powerpc/Kconfig arch/powerpc/platforms/83xx/Kconfig:10:warning: 'select' used by config symbol \ 'MPC834x_SYS' refer to undefined symbol 'DEFAULT_UIMAGE' #

# using defaults found in .config
#
make[3]: `.kernelrelease' is up to date.
  SPLIT   include/linux/autoconf.h -> include/config/*
+ '[' -lt 0400 ']'
/bin/sh: line 1: [: -lt: unary operator expected

does chmod +x scripts/gcc-version.sh help?

Which raises the question - I believed, we support Intel CC for kernel compilation? Or was just just a dream?

- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD0oaFR6LMutpd94wRAsj3AKDQ/TJDNUFT6HlJ+zkG7mW2pmrRZgCfWjfR qFqo6sJ1jW/t/w1B26i/hdU=
=ByTQ
-----END PGP SIGNATURE-----

#1 lore raw
Quoted 1 line · Andrey Borzenkov

does chmod +x scripts/gcc-version.sh help?

no, cc-version is not expanded in this context.

Signature · 2 lines
short story of a lazy sysadmin:
 alias appserv=wotan
#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 4 lines · Olaf Hering
Quoted 1 line · Andrey Borzenkov

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-----

#3 lore raw
Quoted 4 lines · Andrey Borzenkov
Quoted 1 line

no, cc-version is not expanded in this context.

So again - does scripts/gcc-version.sh returns any usable value? Is it executable?

As I said, its not called at all in this context.

Signature · 2 lines
short story of a lazy sysadmin:
 alias appserv=wotan
#4 lore raw
In reply to Andrey Borzenkov
Quoted 3 lines

Which raises the question - I believed, we support Intel CC for kernel compilation? Or was just just a dream?

Not really. If ICC works though, then it's because ICC was tuned hard to behave like GCC.

Jan Engelhardt

#5 lore raw
In reply to Andrey Borzenkov
Quoted 3 lines · Andrey Borzenkov

Which raises the question - I believed, we support Intel CC for kernel compilation? Or was just just a dream?

We have include/linux/compiler-intel.h as the only artifact to support the Intel compiler.
In all other places we assume gcc - but Intel tries hard to be gcc alike.

Sam