From: Sam Ravnborg <sam@ravnborg.org>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: 2.6.24-rc1-82798a1 compile failure (x86_64)
Date: Sat, 3 Nov 2007 13:11:49 +0100 [thread overview]
Message-ID: <20071103121149.GA22149@uranus.ravnborg.org> (raw)
In-Reply-To: <472C47B4.4030808@archlinux.org>
On Sat, Nov 03, 2007 at 11:04:36AM +0100, Thomas Bächler wrote:
> Thomas Bächler schrieb:
> >
> > I just remembered, a friend of mine got it to compile with the exact
> > same toolchain, but with a different configuration (which I don't have).
> > He used a snapshot tarball from yesterday though, not the git tree.
> >
>
> I found the problem and eliminated it. While this is my own fault, it is
> still a bug in either the kernel or the build system: I had CFLAGS set
> to "-Wall -O3 -march=native -pipe". I always thought the kernel would
> ignore those and set its own CFLAGS, but I was wrong. Either the -O3 or
> the -march=native break the build process on gcc 4.2.2.
>
The kernel will now honour the users CFLAGS setting as you just discovered.
The flags will be appended to the flags specified by the kernel.
So the kernel change is on purpose but this does not explain why it
fails for you.
It should be trivial to investigate which of the options that makes
it fail.
Sam
next prev parent reply other threads:[~2007-11-03 12:10 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 [this message]
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
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=20071103121149.GA22149@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=thomas@archlinux.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