From owner-freebsd-stable Sun Mar 21 3:58:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 4516814D13 for ; Sun, 21 Mar 1999 03:58:40 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id MAA26062 for freebsd-stable@FreeBSD.ORG; Sun, 21 Mar 1999 12:58:21 +0100 (CET) (envelope-from olli) Date: Sun, 21 Mar 1999 12:58:21 +0100 (CET) From: Oliver Fromme Message-Id: <199903211158.MAA26062@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Problem with "make release" Newsgroups: list.freebsd-stable Organization: Administration Heim 3 Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote in list.freebsd-stable: > Have you got a couple of vn devices configured ? I have no idea > why miniperl is complaining, but vn's are required to build the boot > floppies etc. Yes, I have 16 (!) vn devices configured. This doesn't look like a problem with vn devices anyway, because it's not yet trying to build any floppies or CDs, as far as I can tell. It seems to be in the midst of building perl. The strange thing is that perl is also built during a "make buildworld", which works fine without any problems. Regards Oliver > > I tried to do a "make release" in mid February, I tried it a > > few days ago, and I tried it today. It always fails at exactly > > the same point, with the same error message -- it's 100% > > reproducible, so it's probably not a hardware problem. > > > > At first I thought that my CVS repository might be broken, > > so I newfs'ed it and cvsup'ed a fresh copy -- same thing. > > > > Interestingly, "make buildworld" works perfectly fine (takes > > about 1 hour), but "make release" fails after about 1.5 hours. > > I'm probably doing something wrong, because it seems to work > > for others, but WTF am I doing wrong?!? > > > > [...] > > ===> gnu/usr.bin/perl > > ===> gnu/usr.bin/perl/libperl > > ===> gnu/usr.bin/perl/miniperl > > sh config_h.sh > > Extracting config.h (with variable substitutions) > > cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlmain.c > > cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/include -static -o miniperl miniperlmain.o -lperl -lm -lcrypt > > ===> gnu/usr.bin/perl/perl > > find: build: No such file or directory > > find: build: No such file or directory > > sh config_h.sh > > Extracting config.h (with variable substitutions) > > sh writemain.sh > > Extracting writemain (with variable substitutions) > > sh writemain lib/auto/DynaLoader/DynaLoader.a > perlmain.c > > cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -I/usr/obj/usr/src/tmp/usr/include -c perlmain.c > > miniperl /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm Config.pm Porting/Glossary myconfig config.sh > > cd lib ; ln -sf ../Config.pm > > miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' lib/*.pm lib/*/*.pm > > Can't open perl script "-e": Device not configured > > *** Error code 6 > > > > Stop. > > *** Error code 1 > > > > Stop. > > [...] > > *** Error code 1 > > > > Stop. > > # -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message