On Mon, May 02, 2005 at 09:01:10AM +1000, Luke Mewburn wrote:
> On Sat, Apr 30, 2005 at 12:28:39AM -0500, Richard Rauch wrote:
>   | I was trying to cross-build a 1.6 release from a 2.0 system.
>   | The build failed, but it seems that build.sh installed the
>   | old, 1.6 crt*.o libraries on my 2.x system.
> 
> How did you invoke build.sh, and what build-related environment

./build.sh -M/raid/0/kernobj-1.6 -T/raid/0/tools-1.6 kernel=odysseus

...I believe.  Or some such.  This is pretty much what I normally do
for building -current, save that I wanted a 1.6-variation on the path
names to separate from -current.


> variables did you have defined at the time ?

/etc/mk.conf contained these lines (less comments; the X11SRCDIR
would have been a problem, I see...but I never got to that point).

X11SRCDIR=/usr/netbsd/current/xsrc
OBJHOSTNAME=yes
MPLAYER_DISABLE_DRIVERS= arts
OBJMACHINE=     yes
PKGSRC_MESSAGE_RECIPIENTS= rkr
BLENDER_USE_EXPPYTHON= YES
BLENDER_INSTALL_DOC=   YES
PAPERSIZE=      Letter
USE_TETEX2=     YES
FAILOVER_FETCH= YES
ACCEPTABLE_LICENSES+=povray-license


build.sh also overwrote /usr/include files, it turned out.
To fix, I ultimately re-downloaded the 2.0 ISO (I couldn't find
my old CD that I had used for installing the system) and
re-extracted the "comp" set.


> build.sh makes an effort to avoid damaging your system, and
> requires the user to explicitly pass in options to install to
> the running system (in "/").

I wasn't even to the point of installing.  I was just building
a kernel.


> (Also, are you aware that the syntax for build.sh changed from 1.6 to 2.0?)

No.  What kinds of changes took place?


-- 
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/