Setting up NFS client

[Denys Vlasenko]

On Sunday 19 April 2009 11:08, Michael Abbott wrote:
> On Sat, 18 Apr 2009, Mike Frysinger wrote:
> > On Saturday 18 April 2009 14:14:45 Paul Smith wrote:
> > > On Sat, 2009-04-18 at 18:53 +0100, Michael Abbott wrote:
> > > > I have to build this separately (and ended up having
> > > > to make a couple of tiny patches for out of tree building to work).  I
> > > > downloaded portmap-6.0 from http://neil.brown.name/portmap/ .
> > > Nice; have you send this along upstream?  In my experience people are
> > > usually happy to get things like this.
> > i already sent this fix upstream long ago (May 17 2007 to be exact)
> 
> Well, the patch to pmap_check.c went into git at the time (date seems to 
> be May 13, as it happens),
> 	http://neil.brown.name/git/portmap ,
> but not into a new release -- looks like your patch was straight after the 
> 6.0 release, and there hasn't been a 6.1.
> 
> However the Makefile change isn't there, but it is only to help out of 
> tree builds, which frankly don't get much attention on most projects (the 
> amount of time I've spent on enabling this on various components is 
> ridiculous).  To be honest, no I haven't tried pushing upstream -- and the 
> associated build command may suggest why I didn't bother!
> 
> 
> P.S.  Anybody here know how to build out of tree kernel modules so that 
> the built files are in their own "out of tree" directory?  Two quite 
> different uses of the term "out of tree" here, and necessarily four 
> separate directories: 1. kernel sources; 2. kernel build directory; 3. 
> module sources; 4. module build directory.  Unfortunately I haven't found 
> any way to avoid (3)==(4).

There is a reason why out-of-tree builds are not as well tested as in-tree ones.

Getting them right, and _maintaining_ them right, as everything else,
needs developer's effort (the limiting resource in our trade).
And most projects are small enough that just making a scratch copy
of the source tree and building in-tree does not require much space
or time.

Thus, it makes sense to not waste developer's time making it work
for small projects. Developer can fix a few real bugs instead.

For big projects like kernel, gcc etc it makes more sense.


IIRC out-of-tree kernel build has this "curious" property that every time
someone embeds __FILE__ into a printk message it ends it being:

/home/peter/srcdevel/big/projects/hacking/kernel/linux-x.y.z/kernel/module.c

instead of:

kernel/module.c

This wastes many kilobytes in kernel image.

This alone makes me willing to create a shadow tree full of symlinks
and make an "in-tree" build there.
--
vda