Re: [PATCH 0/2] kbuild updates

[Andreas Gruenbacher <agruen@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

On Tuesday 22 June 2004 07:20, Sam Ravnborg wrote:
> On Tue, Jun 22, 2004 at 11:39:43AM +1000, Peter Chubb wrote:
> > 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.
>
> Patch is welcome. I recall having trouble with it when introducing it. But
> that can have been caused by other issues.

The same issue exists with the KERNELSRC and KERNELOUTPUT paths in 
$(objtree)/Makefile: they would also better be relative to each other. In our 
case we have something like:

	KERNELSRC    := /usr/src/linux-2.6.5-7.79
	KERNELOUTPUT := /usr/src/linux-2.6.5-7.79-obj/i386/default

this would become:

	KERNELSRC    := ../../../linux-2.6.5-7.79
	KERNELOUTPUT := ../linux-2.6.5-7.79-obj/i386/default

I am currently regenerating $(objtree)/Makefile by hand by invoking mkmakefile 
with the appropriate parameters. The attached script could be used to 
automate this; it would work equally well for the asm symlink.

Regards,
-- 
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX AG

[-- Attachment #2: relpath --]
[-- Type: application/x-shellscript, Size: 580 bytes --]