From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: Olaf Hering <olh@suse.de>
Subject: Re: cc-version not available to change EXTRA_CFLAGS
Date: Sat, 21 Jan 2006 22:07:42 +0300 [thread overview]
Message-ID: <200601212207.49483.arvidjaar@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> 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-----
next reply other threads:[~2006-01-21 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 19:07 Andrey Borzenkov [this message]
2006-01-21 19:11 ` cc-version not available to change EXTRA_CFLAGS 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
-- 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=200601212207.49483.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox