Re: Please read if you use x86 -current

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

On Thu, 13 Nov 2008 16:28:15 +0100 (CET)
Havard Eidnes <he%NetBSD.org@localhost> wrote:

> > > > > > >   cd src/sys/modules
> > > > > > >   make
> > > > > > >   make install
> > > > > >
> > > > > > At a minimum, build.sh should have an option to do that, to
> > > > > > get the proper path for the toolchain, since these
> > > > > > instructions can fail:
> > > > >
> > > > > USETOOLS=no
> > > >
> > > > And for folks who cross-compile?
> > >
> > > I have to ask: are you just trying to be difficult?
> >
> > Not even slightly.
> 
> Heh, it sure looked that way to me. :)

My apologies -- I try not to be that cryptic.
> 
> I've pasted in the part of Andrew's instructions which should
> have been included as context in the above.

I'm not sure which part of Andrew's instructions you're including --
the business about build.sh needing modification was my text
(http://mail-index.netbsd.org/current-users/2008/11/12/msg005867.html).

> 
> So, this comment just goes to how one should handle the "make" in
> Andrew's initial instructions.

Here's the part of Andrew's post I was addressing:

        I am open to ideas about how this can be automated either via
        the kernel makefile, or build.sh.

I'm suggesting that worrying about the kernel makefile first is the
wrong problem -- we need to make build.sh DTRT.  I also suggested (in
my first "troublesome" post) either a -l option to build modules, or
simply always build them -- just like build.sh always builds things like
games.tgz and text.tgz, even though small systems or embedded systems
don't use them.
> 
> If you're doing your kernel or normal complete build using
> build.sh, that script will set up a TOOLDIR for you.  So, if
> you're cross-compiling, my suggestion:
> 
> > > [...] So when the
> > > instructions said "make", that should be read as
> > >
> > > $TOOLDIR/bin/nbmake-$ARCH
> 
> Still holds as a valid translation, you just need to know where
> build.sh put it's TOOLDIR.
> 
> 
> Now, I can sympathise with the request to have build.sh modified
> to build and/or install the modules on request, but the way I see
> it that is a slightly orthogonal argument to the above, which
> goes to how to interpret the original instructions.
> 
> Regards,
> 
> - H__vard
> 



                --Steve Bellovin, http://www.cs.columbia.edu/~smb