From: Sam Ravnborg <sam@ravnborg•org>
To: Russell King <rmk@arm•linux.org.uk>
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 22:51:33 +0200 [thread overview]
Message-ID: <20080623205133.GA12278@uranus.ravnborg.org> (raw)
In-Reply-To: <20080623203249.GB16238@flint.arm.linux.org.uk>
On Mon, Jun 23, 2008 at 09:32:49PM +0100, Russell King wrote:
> 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?
The asm-offsets.h file should always be generated in the same directory.
And that is include/asm-$ARCH today.
But if we move include/asm-$ARCH to arch/$ARCH/include then that directory
no longer exists.
And I wanted to avoid adding generated files to arch/$ARCH/include
so the obvious choice was to generate the asm-offsets.h file in
include/asm which works in make O=... and 'normal' builds.
And because I were facing problams when asm was a symlink I
went for the solution with asm being a directory.
But then arm creates asm-arm as a directory too.
So I can try to see of I can make asm a symlink again
to asm-$ARCH. Adding a include3 directory is not my preferred
solution.
Sam
next prev parent reply other threads:[~2008-06-23 20:50 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
2008-06-23 20:51 ` Sam Ravnborg [this message]
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=20080623205133.GA12278@uranus.ravnborg.org \
--to=sam@ravnborg$(echo .)org \
--cc=hskinnemoen@atmel$(echo .)com \
--cc=lethal@linux-sh$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rmk@arm$(echo .)linux.org.uk \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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