Linux-Next discussions
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>,
	Russell King <rmk@arm.linux.org.uk>,
	Paul Mundt <lethal@linux-sh.org>,
	linux-next@vger.kernel.org
Subject: Re: linux-next build poblems
Date: Mon, 23 Jun 2008 19:08:01 +0200	[thread overview]
Message-ID: <20080623170801.GA16637@uranus.ravnborg.org> (raw)
In-Reply-To: <20080624022232.5c81519c.sfr@canb.auug.org.au>

On Tue, Jun 24, 2008 at 02:22:32AM +1000, Stephen Rothwell wrote:
> Hi Sam,
> 
> I haven't had a good look, but something has gone badly wrong with the
> arm, avr32 and sh builds of linux-next today.  Have a look at
> http://kisskb.ellerman.id.au/linux-next.
Looked at sh and this is obviously a kbuild-next.git problem.

I will try to look at it tonight - as in a few hours from now.
If you are in a hurry drop kbuild-next.git.

I have changed a few things around the symlink handling
and this was only tested with sparc and x86 (32 bit) as this
is the cross toolchains I have available on this box.

It is just perfect that -next find this before the merge window!

	Sam

  reply	other threads:[~2008-06-23 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 16:22 linux-next build poblems Stephen Rothwell
2008-06-23 17:08 ` Sam Ravnborg [this message]
2008-06-23 23:29   ` Stephen Rothwell
2008-06-23 17:10 ` Russell King
2008-06-23 20:07   ` Sam Ravnborg
2008-06-23 20:21     ` Sam Ravnborg
2008-06-23 20:32       ` Russell King
2008-06-23 20:51         ` Sam Ravnborg
2008-06-23 21:01           ` Sam Ravnborg
2008-06-24 13: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=20080623170801.GA16637@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=hskinnemoen@atmel.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=sfr@canb.auug.org.au \
    /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