Subject: Re: strange build failure
To: Steven M. Bellovin <smb@cs.columbia.edu>
From: Dheeraj Reddy <dheerajr@gmail.com>
List: current-users
Date: 08/24/2006 22:03:22
This is because of rev 1.75 of /src/bin/sh/expand.c

updating to rev1.76 of the said file fixes it.

You could either build /bin/sh separately or use a different shell for
building.

dheeraj
On 8/24/06, Steven M. Bellovin <smb@cs.columbia.edu> wrote:
> On my laptop -- running -current from a day or two ago -- I can't build
> a new system.  On a desktop, running -current from about Aug 19, I can.
> Both have up-to-date source trees; in both cases, I removed the entire
> build directory before invoking build.sh.  I invoke build.sh via the
> identical shell script on both machines.
>
> On the failing machine, I get this while building the toolchain:
>
>
> touch stamp-ofiles
> /bin/sh ./libtool --mode=link cc -W -Wall -Wstrict-prototypes -Wmissing-prototyp
> es -O    -o libbfd.la -rpath /usr/BUILD/tools/i386-unknown-netbsdelf4.99.1/i386-
> -netbsdelf/lib -release 2.16.1 archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo
>  cache.lo coffgen.lo corefile.lo format.lo init.lo libbfd.lo  opncls.lo reloc.lo
>  section.lo syms.lo targets.lo hash.lo  linker.lo srec.lo binary.lo tekhex.lo ih
> ex.lo stabs.lo  stab-syms.lo merge.lo dwarf2.lo simple.lo archive64.lo `cat ofil
> es`
> mkdir .libs
> libtool: link: cannot find the library `'
>
> *** Failed target:  libbfd.la
> *** Failed command: /bin/sh ./libtool --mode=link cc -W -Wall -Wstrict-prototype
> s -Wmissing-prototypes -O -o libbfd.la -rpath /usr/BUILD/tools/i386-unknown-netb
> sdelf4.99.1/i386--netbsdelf/lib -release 2.16.1 archive.lo archures.lo bfd.lo bf
> dio.lo bfdwin.lo cache.lo coffgen.lo corefile.lo format.lo init.lo libbfd.lo opn
> cls.lo reloc.lo section.lo syms.lo targets.lo hash.lo linker.lo srec.lo binary.l
> o tekhex.lo ihex.lo stabs.lo stab-syms.lo merge.lo dwarf2.lo simple.lo archive64
> .lo `cat ofiles`
> *** Error code 1
>
>
> It looks as if 'make' isn't invoking the shell properly on the laptop
> for that command.  (Both machines have /bin/ksh as root's shell.)
>
> I see nothing in /etc/mk.conf that's even vaguely relevant; virtually
> all of it has to do with pkgsrc.
>