From: Andi Kleen <andi@firstfloor.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
Paulo Marques <pmarques@grupopie.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org
Subject: Re: /proc/kallsyms broken in 2.6.26-rc1-git6
Date: Tue, 13 May 2008 11:54:37 +0200 [thread overview]
Message-ID: <20080513095437.GJ31954@one.firstfloor.org> (raw)
In-Reply-To: <20080512172323.GA9236@uranus.ravnborg.org>
> I expect it to be a toolchain issue. Andi is often running with gcc versions
> that are very new (fresh from svn maybe). I dunno about binutils.
No actually that's a pretty old version from SUSE 10.2
gcc-4.1.3-29
binutils-2.17.50.0.5-21
This means i've been recently trying to get the x86-64 kernel to work
with the new gold linker from binutils mainline, but it's far from
booting yet and was not used here.
> To reproduce I would expect that a very recent gcc/binutils is needed.
> Andi?
Just a SUSE 10.2 toolchain. You can probably rpm2cpio it from any
SUSE mirror.
-Andi
next prev parent reply other threads:[~2008-05-13 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 17:41 /proc/kallsyms broken in 2.6.26-rc1-git6 Andi Kleen
2008-05-09 18:03 ` Paulo Marques
2008-05-09 19:36 ` Andi Kleen
2008-05-09 19:59 ` Paulo Marques
2008-05-09 23:16 ` Andi Kleen
2008-05-12 9:55 ` Paulo Marques
2008-05-12 10:08 ` Andi Kleen
2008-05-09 23:37 ` Alexey Dobriyan
2008-05-12 10:00 ` Paulo Marques
2008-05-12 15:50 ` Cyrill Gorcunov
2008-05-12 17:23 ` Sam Ravnborg
2008-05-12 17:28 ` Cyrill Gorcunov
2008-05-13 9:54 ` Andi Kleen [this message]
2008-05-19 18:11 ` Sam Ravnborg
2008-05-19 18:15 ` Cyrill Gorcunov
2008-05-19 18:21 ` Sam Ravnborg
2008-05-19 18:22 ` Cyrill Gorcunov
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=20080513095437.GJ31954@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=adobriyan@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=sam@ravnborg.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