tar -jxf linux-2.6.31.2.tar.bz2
cd linux-2.6.31.2
cp ../.config ./
make ARCH=um
[...]
MODPOST vmlinux.o
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:arch/um/kernel/vmlinux.lds:1:
ignoring invalid character `#' in expression
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:arch/um/kernel/vmlinux.lds:1:
syntax error
collect2: ld returned 1 exit status
KSYM .tmp_kallsyms1.S
nm: '.tmp_vmlinux1': No such file
No valid symbol.
make: *** [.tmp_kallsyms1.S] Error 1
Sorry, not had time to bisect it.
Tested with gcc 4.1.2 and gcc 4.3.2
Use this config if yours does not exhibit the problem:
http://uml.devloop.org.uk/kernels/kernel64-2.6.31.config
Cheers
Antoine
On Mon, Oct 12, 2009 at 10:03:30PM +0700, Antoine Martin wrote:
>tar -jxf linux-2.6.31.2.tar.bz2
>cd linux-2.6.31.2
>cp ../.config ./
>make ARCH=um
>[...]
> MODPOST vmlinux.o
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
>/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:arch/um/kernel/vmlinux.lds:1:
>ignoring invalid character `#' in expression
>/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:arch/um/kernel/vmlinux.lds:1:
>syntax error
>collect2: ld returned 1 exit status
> KSYM .tmp_kallsyms1.S
>nm: '.tmp_vmlinux1': No such file
>No valid symbol.
>make: *** [.tmp_kallsyms1.S] Error 1
Hmm, this is a known problem:
https://lists.linux-foundation.org/pipermail/bugme-new/2009-May/021900.html
>
>Sorry, not had time to bisect it.
>Tested with gcc 4.1.2 and gcc 4.3.2
>Use this config if yours does not exhibit the problem:
>http://uml.devloop.org.uk/kernels/kernel64-2.6.31.config
No problem. Thanks for your report!
I will take care of this tomorrow, it's mid-night here already. :-)
--
Live like a child, think like the god.
On Tue, Oct 13, 2009 at 12:58 AM, Antoine Martin <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
>> Hmm, this is a known problem:
>> https://lists.linux-foundation.org/pipermail/bugme-new/2009-May/021900.html
> How odd that I have been compiling successfully all that time!
> Maybe the fact that it broke "more" recently will help you...
Please try this patch:
http://patchwork.kernel.org/patch/48759/
It should fix your problem.
What I can do here is to suggest -stable team to include this patch in the
next update for .31. Greg?
On Tue, Oct 13, 2009 at 09:54:52AM +0800, Am??rico Wang wrote:
> On Tue, Oct 13, 2009 at 12:58 AM, Antoine Martin <[email protected]> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> >> Hmm, this is a known problem:
> >> https://lists.linux-foundation.org/pipermail/bugme-new/2009-May/021900.html
> > How odd that I have been compiling successfully all that time!
> > Maybe the fact that it broke "more" recently will help you...
>
> Please try this patch:
>
> http://patchwork.kernel.org/patch/48759/
>
> It should fix your problem.
>
> What I can do here is to suggest -stable team to include this patch in the
> next update for .31. Greg?
Send the git commit id of the patch that fixes the problem that is
already in Linus's tree to [email protected] and cc: me.
thanks,
greg k-h
On Tue, Oct 13, 2009 at 10:12 AM, Greg KH <[email protected]> wrote:
> On Tue, Oct 13, 2009 at 09:54:52AM +0800, Am??rico Wang wrote:
>> On Tue, Oct 13, 2009 at 12:58 AM, Antoine Martin <[email protected]> wrote:
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA512
>> >
>> >> Hmm, this is a known problem:
>> >> https://lists.linux-foundation.org/pipermail/bugme-new/2009-May/021900.html
>> > How odd that I have been compiling successfully all that time!
>> > Maybe the fact that it broke "more" recently will help you...
>>
>> Please try this patch:
>>
>> http://patchwork.kernel.org/patch/48759/
>>
>> It should fix your problem.
>>
>> What I can do here is to suggest -stable team to include this patch in the
>> next update for .31. Greg?
>
> Send the git commit id of the patch that fixes the problem that is
> already in Linus's tree to [email protected] and cc: me.
Thanks!
Below it is:
commit 51b563fc93c8cb5bff1d67a0a71c374e4a4ea049
From: Sam Ravnborg <[email protected]>
Date: Sun, 20 Sep 2009 12:28:22 +0200
Subject: [PATCH 1/1] arm, cris, mips, sparc, powerpc, um, xtensa: fix
build with bash 4.0