Hmm, double make cleandir fixed it.

Could a conveniently located perl wizard try to figure out what
this is tripping over and fix the build ?

In message <9459.926593...@critter.freebsd.dk>, Poul-Henning Kamp writes:
>
>Is anybody but me seeing this ?
>
>===> 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/p
>erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl   
>-I/usr/obj/usr/src/tmp/usr/i
>nclude -c 
>/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlm
>ain.c
>cc -nostdinc -O -pipe 
>-I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p
>erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl   
>-I/usr/obj/usr/src/tmp/usr/i
>nclude  -static -o miniperl miniperlmain.o  -lperl -lm -lcrypt
>===> gnu/usr.bin/perl/perl
>make: don't know how to make writemain.sh. Stop
>*** Error code 2
>
>
>--
>Poul-Henning Kamp             FreeBSD coreteam member
>p...@freebsd.org               "Real hackers run -current on their laptop."
>FreeBSD -- It will take a long time before progress goes too far!
>
>
>To Unsubscribe: send mail to majord...@freebsd.org
>with "unsubscribe freebsd-current" in the body of the message
>

--
Poul-Henning Kamp             FreeBSD coreteam member
p...@freebsd.org               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Reply via email to