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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
