From: Dan Kegel <dank@kegel.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bringing back 'make symlinks'?
Date: Tue, 25 May 2004 20:47:51 -0700 [thread overview]
Message-ID: <40B41367.5070607@kegel.com> (raw)
In-Reply-To: <20040525214328.GA2675@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Tue, May 25, 2004 at 08:45:18AM -0700, Dan Kegel wrote:
>
>>In the 2.4 kernel, 'make symlinks' created the symlinks needed
>>to use the kernel tree's headers for building a gcc/glibc toolchain.
>>
>>In the 2.6 kernel, you can do the same thing with 'include include/asm'.
>>Unless you're trying to build arm or cris, or maybe others, in which case
>>you also need 'include/asm-$(ARCH)/.arch'.
> ...
>
> In current 2.6 there exitst a target named: modules_prepare
> It does a bit more than what symlinks did in 2.4 - actually prepare for
> building external modules.
Right, and that's a problem, because the 'bit more' it does
requires a target compiler -- which isn't available while
bootstrapping the target compiler!
The way things are now, I can build toolchains for everything
except the sh architecture (though my toolchain bootstrap script
is ugly as noted due to the lack of 'make symlinks').
I'm not sure if the sh architecture makefile even has targets
to make all the needed symlinks in the absense of a working
target compiler; I'll look at that and maybe submit a minimal
patch when I get a chance.
- Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
next prev parent reply other threads:[~2004-05-26 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 15:45 bringing back 'make symlinks'? Dan Kegel
2004-05-25 21:43 ` Sam Ravnborg
2004-05-26 3:47 ` Dan Kegel [this message]
2004-05-30 10:55 ` Sam Ravnborg
2004-05-31 18:40 ` Dan Kegel
2004-05-31 20:16 ` Sam Ravnborg
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=40B41367.5070607@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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