From: Russell King <rmk@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-next@vger.kernel.org
Subject: Re: linux-next build poblems
Date: Mon, 23 Jun 2008 21:32:49 +0100 [thread overview]
Message-ID: <20080623203249.GB16238@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080623202156.GA12027@uranus.ravnborg.org>
On Mon, Jun 23, 2008 at 10:21:56PM +0200, Sam Ravnborg wrote:
> >
> > I need to work out something.
> > But my first attemps failed miserably and I will stop for now
> > as I have some day-time job stuff to be done.
> > Travelling for a few days from now one so I cannot do anything
> > until the weekend.
> I came up with the following fix.
> And I fixed an arm tool chain for my box so I could check it.
>
> We can now build an arm kernel (or at least the first steps).
>
> I have pushed it out to kbuild-next.git.
> And I will redo the patch series later so we do not bisect break arm etc.
Silly question, but what's wrong with restoring the symlink in the
build include/ directory?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-06-23 20:33 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
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 [this message]
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=20080623203249.GB16238@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=hskinnemoen@atmel.com \
--cc=lethal@linux-sh.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.org \
--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 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.