All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Dan Kegel <dank@kegel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bringing back 'make symlinks'?
Date: Tue, 25 May 2004 23:43:28 +0200	[thread overview]
Message-ID: <20040525214328.GA2675@mars.ravnborg.org> (raw)
In-Reply-To: <40B36A0E.5080509@kegel.com>

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'.
> 
> That's fine, but it means that a script (like crosstool) or a book (like 
> LFS)
> that's trying to build a gcc/glibc toolchain for both 2.4 and 2.6 ends up
> with a section like
> 
> case "$KERNEL_VERSION.$KERNEL_PATCHLEVEL.x" in
> 2.2.x|2.4.x) make ARCH=$ARCH symlinks    include/linux/version.h
>              ;;
> 2.6.x)       make ARCH=$ARCH include/asm include/linux/version.h
>              case $ARCH in
>              arm*|cris*) make ARCH=$ARCH include/asm-$ARCH/.arch
>                          ;;
>              esac
>              ;;
> *)           abort "Unsupported kernel version 
> $KERNEL_VERSION.$KERNEL_PATCHLEVEL"
> esac

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.

	Sam

  reply	other threads:[~2004-05-25 21:43 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 [this message]
2004-05-26  3:47   ` Dan Kegel
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=20040525214328.GA2675@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.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 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.