Subject: Re: How to properly use shell commands that are defined in make(1)
To: Gilles Dauphin <Gilles.Dauphin@enst.fr>
From: Roland Illig <rillig@NetBSD.org>
List: tech-pkg
Date: 11/27/2005 21:02:12
Gilles Dauphin wrote:
> when i make a bulk build from a clean distrib. i have the following error
> in the bulk build log file for gzip-base:
> 
> ---------------------------------------------------------------------
> 2005/11/24 14:23:30  15/5718= 0.3% archivers/gzip-base @ i386> x - extracting 
> gzip-1.2.4a/algorith
> m.doc (text)
> 2005/11/24 14:23:30  15/5718= 0.3% archivers/gzip-base @ i386> x - extracting 
> gzip-1.2.4a/gzip.tex
> i (text)
> 2005/11/24 14:23:30  15/5718= 0.3% archivers/gzip-base @ i386> /bin/ksh[15274]: 
> syntax error at li
> ne 15275 : `(' unexpected

That's weird. My copy of gzip-1.2.4a.shar does not contain a '(' in 
lines 15274--15275.

> 2005/11/24 14:23:30  15/5718= 0.3% archivers/gzip-base @ i386> grep: can't open 
> "/usr/pkgsrc/.broken.html"

This warning needs some code to disappear, but in this case, it doesn't 
do any harm. grep(1) checks here whether a package appears in the top 
level list of broken packages. Now that the file does not exist, grep(1) 
returns non-zero, meaning that the package does not exist in that file.

The solution is to create an empty ${BULKFILESDIR:Q}/${BROKENFILE:Q} 
before starting the package builds.

> I have a similar problem making bulk build with audio/nas
> ------------------------------------------------------------
> 2005/11/24 16:30:46  207/5718= 3.6% audio/nas @ i386> ===> Patching for 
> nas-1.7bnb1
> 2005/11/24 16:30:46  207/5718= 3.6% audio/nas @ i386> ===> Applying pkgsrc 
> patches for nas-1.7bnb1
> 2005/11/24 16:30:46  207/5718= 3.6% audio/nas @ i386> ===> Overriding tools for 
> nas-1.7bnb1
> 2005/11/24 16:30:46  207/5718= 3.6% audio/nas @ i386> ===> Creating toolchain 
> wrappers for nas-1.7
> bnb1
> 2005/11/24 16:30:46  207/5718= 3.6% audio/nas @ i386> ===> Configuring for 
> nas-1.7bnb1
> 2005/11/24 16:30:46  207/5718= 3.6% audio/nas @ i386> /usr/bin/env: No such file 
> or directory

You mean you have a system without /usr/bin/env? Or is it that 
/usr/bin/env cannot find the binary it is supposed to exec()?

Roland