Project

General

Profile

Actions

Bug #2455

closed

make has weird behaviour on a random basis

Added by tuxillo about 12 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Build
Target version:
Start date:
11/14/2012
Due date:
% Done:

0%

Estimated time:

Description

Hi,

I got a similar message (with bmake on base) during certain operations I haven't been able to determine yet.

antonioh@dfbsd32_devel:/home/source/dfbsd/test/vkernel> sudo E make reinstallkernel
/var/vkernel found
umount /var/vkernel/root > /dev/null 2>&1
vnconfig -u `cat /var/vkernel/vn.which` > /dev/null 2>&1
rm -f /var/vkernel/vn.which
(vnconfig -l | fgrep "not in use" > /dev/null) || (echo "Cannot find unused VN"; /usr/bin/false)
vnconfig -l | fgrep "not in use" | cut -f 1 -d : | head -1 > /var/vkernel/vn.which
egrep '^vn' /var/vkernel/vn.which > /dev/null || (echo "VN device selection is bad"; /usr/bin/false)
vnconfig -c -s labels `cat /var/vkernel/vn.which` /var/vkernel/root.img
fsck -p /dev/`cat /var/vkernel/vn.which`s1a
/dev/vn0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/vn0s1a: clean, 854822 free (2214 frags, 106576 blocks, 0.2% fragmentation)
mount /dev/`cat /var/vkernel/vn.which`s1a /var/vkernel/root
Mounted /var/vkernel/root
cd /home/source/dfbsd/test/vkernel/../.. && make -j 4 DESTDIR=/var/vkernel/root KERNCONF=VKERNEL NO_MODULES= installkernel
--
installkernel ---
--- installkernel ---
--------------------------------------------------------------

Kernel install for VKERNEL started on Thu Nov 15 01:16:39 CET 2012

--------------------------------------------------------------
cd /usr/obj/home/source/dfbsd/sys/VKERNEL; MAKEOBJDIRPREFIX=/usr/obj/home/source/dfbsd/world_i386 OBJTREE=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 MACHINE_PLATFORM=pc32 OBJFORMAT_PATH=/usr/obj/home/source/dfbsd/ctools_i386_i386 HOST_CCVER=gcc44 CCVER=gcc44 LDVER=ld.bfd BINUTILSVER=binutils222 PATH=/usr/obj/home/source/dfbsd/ctools_i386_i386/usr/sbin:/usr/obj/home/source/dfbsd/ctools_i386_i386/usr/bin:/usr/obj/home/source/dfbsd/ctools_i386_i386/bin:/usr/obj/home/source/dfbsd/ctools_i386_i386/usr/games:/usr/obj/home/source/dfbsd/btools_i386/usr/sbin:/usr/obj/home/source/dfbsd/btools_i386/usr/bin:/usr/obj/home/source/dfbsd/btools_i386/bin:/usr/obj/home/source/dfbsd/btools_i386/usr/games:/usr/pkg/bin make KERNEL=kernel install
make: "/usr/obj/home/source/dfbsd/sys/VKERNEL/Makefile" line 5: Unknown directive
make: "/usr/obj/home/source/dfbsd/sys/VKERNEL/Makefile" line 6: Unknown directive
make: "/usr/obj/home/source/dfbsd/sys/VKERNEL/Makefile" line 7: Unknown directive
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/obj/home/source/dfbsd/sys/VKERNEL
  • [installkernel] Error code 1

make: stopped in /home/source/dfbsd
.CURDIR='/home/source/dfbsd'
.OBJDIR='/usr/obj/home/source/dfbsd'
.MAKE='make'
MAKE_VERSION='20121010'
LD_LIBRARY_PATH=''
MACHINE_ARCH='i386'
MACHINE='i386'
MAKEFILE='/home/source/dfbsd/Makefile.inc1'
.TARGETS='installkernel'
.ERROR_TARGET='installkernel'
.ERROR_META_FILE=''
.MAKE.LEVEL='2'
.MAKE.MODE=''
1 error

make: stopped in /home/source/dfbsd
.CURDIR='/home/source/dfbsd'
.OBJDIR='/usr/obj/home/source/dfbsd'
.MAKE='make'
MAKE_VERSION='20121010'
LD_LIBRARY_PATH=''
MACHINE_ARCH='i386'
MACHINE='i386'
MAKEFILE='/home/source/dfbsd/Makefile.inc1'
.TARGETS='installkernel'
.ERROR_TARGET='installkernel'
.ERROR_META_FILE=''
.MAKE.LEVEL='2'
.MAKE.MODE=''
  • [installkernel] Error code 2

make: stopped in /home/source/dfbsd
1 error

make: stopped in /home/source/dfbsd
  • Error code 2

Stop.
make: stopped in /home/source/dfbsd/test/vkernel

Actions #1

Updated by marino about 12 years ago

There's nothing random about this -- the three "unknown directive" messages are indicative of a pre-bmake generated makefile. This is the reason a full buildworld was recommended.

The solution is either do the full buildworld or at least manually change those makefile lines 5-7 in /usr/obj/home/source/dfbsd/sys/VKERNEL/Makefile from ".makeenv" to ".export"

Actions #2

Updated by tuxillo over 10 years ago

  • Description updated (diff)
  • Category set to Build
  • Status changed from New to Closed
  • Assignee set to marino
  • Target version set to 3.8

Haven't observed this behaviour since then.

Actions

Also available in: Atom PDF