From owner-freebsd-current Wed Oct 31 13:59: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 228FE37B401 for ; Wed, 31 Oct 2001 13:59:01 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id f9VLx1I45943 for current@FreeBSD.ORG; Wed, 31 Oct 2001 13:59:01 -0800 (PST) (envelope-from david) Date: Wed, 31 Oct 2001 13:59:01 -0800 (PST) From: David Wolfskill Message-Id: <200110312159.f9VLx1I45943@bunrab.catwhisker.org> To: current@FreeBSD.ORG Subject: Re: buildworld breakage during "make depend" at usr.bin/kdump In-Reply-To: <200110312138.f9VLcHX45849@bunrab.catwhisker.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Wed, 31 Oct 2001 13:38:17 -0800 (PST) >From: David Wolfskill >Well, I got beyond that point ["make depends" for usr.bin/kdump] by hacking >src/usr.bin/kdump/mkioctls: [See previous note for patch/hack.] And now for something that smells as if it's related to awk suddenly(?) taking an intense dislike to newline characters in variable values: >>> stage 4: building everything.. ... ===> gnu/lib/libregex ===> gnu/lib/libregex/doc awk -f /usr/src/gnu/lib/libregex/doc/include.awk -vsource=/usr/src/gnu/lib/libregex/doc/../regex.h < /usr/src/gnu/lib/libregex/doc/xregex.texi | expand >regex.texi awk: null file name in print or getline input record number 487, file source line number 5 makeinfo --no-split -I /usr/src/gnu/lib/libregex/doc -I /usr/src/gnu/lib/libregex/doc regex.texi -o regex.info regex.texi:487: No matching `@end example'. ./regex.texi:266: Next reference to nonexistent node `Common Operators'. ./regex.texi:464: Next reference to nonexistent node `Collating Elements vs. Characters'. ... ./regex.texi:102: Menu reference to nonexistent node `Common Operators'. makeinfo: Removing output file `regex.info' due to errors; use --force to preserve. *** Error code 2 Stop in /usr/src/gnu/lib/libregex/doc. *** Error code 1 Stop in /usr/src/gnu/lib/libregex. *** Error code 1 Stop in /usr/src/gnu/lib. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 For the historically-minded, the log from yesterday's -CURRENT buildworld shows the following in that area: ===> gnu/lib/libregex ===> gnu/lib/libregex/doc awk -f /usr/src/gnu/lib/libregex/doc/include.awk -vsource=/usr/src/gnu/lib/libre gex/doc/../regex.h < /usr/src/gnu/lib/libregex/doc/xregex.texi | expand >regex .texi makeinfo --no-split -I /usr/src/gnu/lib/libregex/doc -I /usr/src/gnu/lib/librege x/doc regex.texi -o regex.info regex.texi:876: warning: unlikely character , in @var. regex.texi:880: warning: unlikely character , in @var. gzip -cn regex.info > regex.info.gz ===> gnu/lib/libreadline ===> gnu/lib/libreadline/history So all in all, it seems that awk is now a great deal pickier about ceratin constructs, and that appears to be having a rather adverse effect on the ability to build a -CURRENT world.... I'll go hack for a while, unless someone comes up with a more useful idea. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message