MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16599.36319.269156.432040@wombat.chubb.wattle.id.au>
Date: Tue, 22 Jun 2004 11:39:43 +1000
From: Peter Chubb <peterc@gelato.unsw.edu.au>
To: s0348365@sms.ed.ac.uk
Cc: Martin Schlemmer <azarah@nosferatu.za.org>,
       Sam Ravnborg <sam@ravnborg.org>,
       Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] kbuild updates
In-Reply-To: <539000871@toto.iv>
Comments: Hyperbole mail buttons accepted, v04.18.
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1362
Lines: 33

>>>>> "Alistair" == Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:


Alistair> Sam, maybe if there was a way to easily detect whether a
Alistair> kernel had been build with or without a different output
Alistair> directory, it would be easier to have vendors take this
Alistair> change on board. For example, I imagine in the typical case
Alistair> whereby no change in build directory is made, you will have
Alistair> something like this:


You can do this without any changes:

     if [ -d /lib/modules/`uname -r`/build/include2 ]; then
       kerndir=`cd  /lib/modules/`uname -r`/build/include2/asm; cd -P../..;/bin/pwd`
     else
       kerndir=`cd /lib/modules/`uname -r`/build; /bin/pwd`
    fi


But can the include2/asm symlink be made a relative one, please?  I frequently
build on one machine, then NFS-mount the build tree and run make
modules_install somewhere else; I always at present have to convert
that link to a relative symlink before doing so.

-- 
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
The technical we do immediately,  the political takes *forever*
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/