From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31.2 broke UML 64-bit build (2.6.31 was fine)
Date: Tue, 13 Oct 2009 00:05:48 +0800 [thread overview]
Message-ID: <20091012160548.GA3961@hack> (raw)
In-Reply-To: <4AD34542.7050500@nagafix.co.uk>
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.
next prev parent reply other threads:[~2009-10-12 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 15:03 2.6.31.2 broke UML 64-bit build (2.6.31 was fine) Antoine Martin
2009-10-12 16:05 ` Américo Wang [this message]
[not found] ` <4AD36022.4090300@nagafix.co.uk>
2009-10-13 1:54 ` Américo Wang
2009-10-13 2:12 ` Greg KH
2009-10-13 2:54 ` Américo Wang
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=20091012160548.GA3961@hack \
--to=xiyou.wangcong@gmail.com \
--cc=antoine@nagafix.co.uk \
--cc=linux-kernel@vger.kernel.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