From: Steven Rostedt <srostedt@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: ftrace tree build failure
Date: Mon, 24 Nov 2008 23:31:33 -0500 [thread overview]
Message-ID: <1227587493.7622.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20081125151345.3f0ed493.sfr@canb.auug.org.au>
On Tue, 2008-11-25 at 15:13 +1100, Stephen Rothwell wrote:
> Hi Steve,
>
> On Mon, 24 Nov 2008 22:48:51 -0500 Steven Rostedt <srostedt@redhat.com> wrote:
> >
> > Could you post a git branch that had this failure, so I can compile it
> > to see what happened?
>
> ssh://master.kernel.org/~sfr/ftrace master
>
> to get the failure, I did:
>
> make ARCH=x86_64 allmodconfig
> make ARCH=x86_64 arch/x86/boot/tty.o
>
> My machine is Debian sid.
>
> $ gcc --version
> gcc (Debian 4.3.2-1) 4.3.2
> $ ld --version
> GNU ld (GNU Binutils for Debian) 2.18.0.20080103
>
> The original failure was with a gcc 4.3.2 cross compiled for a powerpc
> host and a binutils 2.19.
>
> You can see which trees are merged by looking for commits by me.
This may be a compiler bug, or something introduced by the compiler. I
compiled it fine first with gcc 4.0.2, but then tried with the same
compiler you used, and got the same error as you.
I'll look more at it.
Thanks,
-- Steve
next prev parent reply other threads:[~2008-11-25 4:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 3:21 linux-next: ftrace tree build failure Stephen Rothwell
2008-11-25 3:48 ` Steven Rostedt
2008-11-25 4:13 ` Stephen Rothwell
2008-11-25 4:31 ` Steven Rostedt [this message]
2008-11-25 5:09 ` Stephen Rothwell
2008-11-25 5:44 ` Steven Rostedt
2008-11-25 6:57 ` Stephen Rothwell
2008-11-25 7:14 ` Ingo Molnar
2008-11-25 7:26 ` Stephen Rothwell
2008-11-25 5:24 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 0:53 Stephen Rothwell
2009-01-07 9:55 ` Ingo Molnar
2009-01-07 21:20 ` Stephen Rothwell
2009-01-02 9:07 Stephen Rothwell
2009-01-02 9:14 ` Ingo Molnar
2009-01-02 10:22 ` Stephen Rothwell
2009-01-02 11:16 ` Ingo Molnar
2008-11-25 3:07 Stephen Rothwell
2008-11-25 3:21 ` Steven Rostedt
2008-11-25 7:28 ` Ingo Molnar
2008-11-25 7:43 ` Stephen Rothwell
2008-11-25 8:04 ` Ingo Molnar
2008-11-25 14:57 ` John W. Linville
2008-11-25 18:46 ` Luis R. Rodriguez
2008-11-26 0:08 ` Stephen Rothwell
2008-11-26 0:14 ` Luis R. Rodriguez
2008-08-25 3:08 Stephen Rothwell
2008-08-25 6:05 ` Ingo Molnar
2008-08-25 6:11 ` Ingo Molnar
2008-08-25 6:31 ` Stephen Rothwell
2008-08-25 3:01 Stephen Rothwell
2008-08-25 6:09 ` Ingo Molnar
2008-08-25 16:42 ` Steven Rostedt
2008-08-25 16:46 ` Steven Rostedt
2008-08-15 2:27 Stephen Rothwell
2008-08-15 7:56 ` Ingo Molnar
2008-08-15 8:29 ` Stephen Rothwell
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=1227587493.7622.14.camel@localhost.localdomain \
--to=srostedt@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.