I'm doing a cross-build of current on a system running stable, with a
separate drive for current mounted as /current (with all sub-mounts correct).
Separate problem causing me to cross-build: current doesn't like to boot
lately - it hangs immediately after loading acpi.ko (on the SMP Supermicro;
works fine on an Asus KT133A with older Athlon 1.2).

I have been using 
setenv DESTDIR /current
make -m/current/usr/share/mk -DDESTDIR=/current world >& mkw.out

with mostly success (I only had to add the -m option lately and only for
the kernel build so far, but I do it anyhow).  The redundant DESTDIR is
probably not needed but I want to be sure.

After discovering the -j thing and its workaround independently, I now
get the following stop after the initial compiler and lib build:

>>> stage 4: populating /usr/obj/current/usr/src/i386/usr/include
cd /current/usr/src; MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386  MACHINE=i386  
DESTDIR=/usr/obj/current/usr/src/i386  INSTALL="sh /current/usr/src/tools/install.sh"  
 make -f Makefile.inc1 SHARED=symlinks includes incsinstall
make: don't know how to make includes. Stop
*** Error code 2

Stop in /current/usr/src.
*** Error code 1

Stop in /current/usr/src.

A quick look at the makefiles doesn't show anything obvious; is is possible
that DESTDIR is being used to look up OBJDIR sometimes (like where includes
come from?)  My /obj is shared with stable with no conflict since the
leading subdir is current instead of usr...  

I'm going to try setting MAKEOBJDIRPREFIX to /current/usr/obj and see.
Got the same failure at the same place.

Can't find anything in the handbook about cross-builds; the makefiles are
fairly clear but not all of the interactions of bsd.*.mk are obvious.
Whatever changed did so in the last 2 or 3 weeks and may or may not
be related to the cc change.  The default gnu makefiles and dir setup
for gmp won't build with -j either, just for info - they do mkdir in the
middle of the make and assume all the resulting dependencies will be
picked up.  May work with gmake and -j but certainly not with bmake.

-- Pete

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to