linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Sam Ravnborg" <sam@ravnborg.org>, "Al Viro" <viro@ZenIV.linux.org.uk>
Cc: "David S. Miller" <davem@davemloft.net>,
	"Ingo Molnar" <mingo@elte.hu>, <rostedt@goodmis.org>,
	"Steven Rostedt" <srostedt@redhat.com>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"sparclinux" <sparclinux@vger.kernel.org>
Subject: Re: ftrace breaks sparc64 build
Date: Tue, 06 Jan 2009 12:39:35 +0000	[thread overview]
Message-ID: <49635F17.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20090106113543.GS28946@ZenIV.linux.org.uk>

>>> Al Viro <viro@ZenIV.linux.org.uk> 06.01.09 12:35 >>>
>On Tue, Jan 06, 2009 at 07:53:04AM +0000, Jan Beulich wrote:
>> The others look like a tools side behavioral difference, as I never saw any
>> such. Is this problem sparc32-specific (I tested x86 and ia64 only)? What's
>> the binutils version used?
>
>2.18.50.0.6.
>
>And no, it's not tools side.  What it is, AFAICT, is that sparc32 has
>LDFLAGS_vmlinux = -r, which leaves a metric arseload of relocs that
>wouldn't have survived into vmlinux otherwise.  Look at .rela__ksymtab
>in .tmp_vmlinux1, for example...

That I think can only be taken care of by disallowing the stripping for that
arch, i.e. adding a negative dependency to the Kconfig option. Or can
anyone think of any other solution?

Jan


  reply	other threads:[~2009-01-06 12:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 18:19 ftrace breaks sparc64 build Sam Ravnborg
2009-01-05 19:31 ` Steven Rostedt
2009-01-05 19:42   ` [PATCH] sparc: make proces_ver_nack a bit more readable Steven Rostedt
2009-01-05 19:46     ` Steven Rostedt
2009-01-05 19:56     ` Steven Rostedt
2009-01-05 20:07       ` Sam Ravnborg
2009-01-05 20:08     ` Sam Ravnborg
2009-01-06 18:23       ` David Miller
2009-01-05 19:54   ` ftrace breaks sparc64 build Sam Ravnborg
2009-01-05 20:05     ` Steven Rostedt
2009-01-05 21:31       ` Sam Ravnborg
2009-01-05 21:52         ` Steven Rostedt
2009-01-05 22:01           ` Sam Ravnborg
2009-01-05 22:14             ` Steven Rostedt
2009-01-05 23:11               ` Heiko Carstens
2009-01-06  2:07                 ` Steven Rostedt
2009-01-06  9:36                   ` Heiko Carstens
2009-01-06  4:30                 ` Steven Rostedt
2009-01-06  9:45                   ` Heiko Carstens
2009-01-06 18:32       ` David Miller
2009-01-06 18:52         ` Steven Rostedt
2009-01-06 19:01           ` David Miller
2009-01-06 19:52             ` Sam Ravnborg
2009-01-06 20:02               ` David Miller
2009-01-05 20:30     ` [PATCH] module: clean up initialization of variable Steven Rostedt
2009-01-05 22:59       ` Harvey Harrison
2009-01-06  1:22       ` Rusty Russell
2009-01-06  2:02         ` Steven Rostedt
2009-01-05 19:48 ` ftrace breaks sparc64 build Al Viro
2009-01-05 19:55   ` Sam Ravnborg
2009-01-06  7:53     ` Jan Beulich
2009-01-06 11:35       ` Al Viro
2009-01-06 12:39         ` Jan Beulich [this message]
2009-01-06 13:34         ` Sam Ravnborg
2009-01-06 15:52           ` Al Viro
2009-01-06 18:39           ` David Miller
2009-01-08  9:28         ` Jan Beulich

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=49635F17.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=sam@ravnborg.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=srostedt@redhat.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).