From: "Thomas Bächler" <thomas@archlinux.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Miller <davem@davemloft.net>,
mingo@elte.hu, bunk@kernel.org, thomas@archlinux.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: 2.6.24-rc1-82798a1 compile failure (x86_64)
Date: Sun, 04 Nov 2007 13:27:44 +0100 [thread overview]
Message-ID: <472DBAC0.7040802@archlinux.org> (raw)
In-Reply-To: <20071104111640.GA17565@uranus.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
Sam Ravnborg schrieb:
> I'm afraid some people do not realize a whit about what they do.
> So at least we could let kbuild warn about it.
> Something like this:
>
> $ export CFLAGS=-O3
> $ make AFLAGS=-fisk
> Makefile:540: "Appending $AFLAGS (-fisk) from command line to kernel defined $AFLAGS"
> Makefile:544: "Appending $CFLAGS (-O3) from environment to kernel defined $CFLAGS"
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CC arch/x86/kernel/asm-offsets.s
> GEN include/asm-x86/asm-offsets.h
> CALL scripts/checksyscalls.sh
> CC scripts/mod/empty.o
I agree, this is a sane way to do it. Would this patch have been
applied, I would have found the problem within minutes AND I would have
known that the kernel does use my CFLAGS, which I assumed it wouldn't.
Maybe you should prefix the message with a "WARNING: ".
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-11-04 12:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:46 2.6.24-rc1-82798a1 compile failure (x86_64) Thomas Bächler
2007-10-29 22:12 ` Thomas Gleixner
[not found] ` <47266BF6.6070206@archlinux.org>
[not found] ` <alpine.LFD.0.9999.0710300033470.3186@localhost.localdomain>
2007-10-30 9:10 ` Thomas Bächler
2007-11-03 10:04 ` Thomas Bächler
2007-11-03 12:11 ` Sam Ravnborg
2007-11-04 2:02 ` Adrian Bunk
2007-11-04 10:04 ` Ingo Molnar
2007-11-04 10:19 ` Sam Ravnborg
2007-11-04 10:31 ` David Miller
2007-11-04 11:16 ` Sam Ravnborg
2007-11-04 12:27 ` Thomas Bächler [this message]
2007-11-04 15:29 ` Adrian Bunk
2007-11-04 15:55 ` Oleg Verych
2007-11-04 16:19 ` Giacomo Catenazzi
2007-11-04 16:34 ` Adrian Bunk
2007-11-04 18:33 ` Giacomo Catenazzi
2007-11-05 4:03 ` David Miller
2007-11-04 18:10 ` Sam Ravnborg
2007-11-05 4:01 ` David Miller
2007-11-06 17:32 ` Arjan van de Ven
2007-11-07 0:12 ` Adrian Bunk
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=472DBAC0.7040802@archlinux.org \
--to=thomas@archlinux.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.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.