-On [2211 20:00], Jordan K. Hubbard ([EMAIL PROTECTED]) wrote:
Unless the docs people can actually make the doc tools build
again and successfully format the docs under -current. :)
Sorry for what sounds like a threat of sorts, but I've been building
the -current snapshots with NODOC=YES for
The build environment is a definite factor here. I built jade on
FreeBSD 4.0-2209-CURRENT (GENERIC) with no problems.
Same on a -stable box. But a -stable release, on a -stable box
that build docproj-1.1 just fine in the ports tree, fell over
building jade.
Kuriyama's USE_GMAKE commit
From: "Jordan K. Hubbard" [EMAIL PROTECTED]
=== Generating temporary packing list
strip /usr/local/bin/jade
strip /usr/local/bin/nsgmls
/usr/libexec/elf/strip: /usr/local/bin/nsgmls: No such file or directory
*** Error code 1
Stop in /usr/ports/textproc/jade.
*** Error code 1
Sorry for
* From: "Jordan K. Hubbard" [EMAIL PROTECTED]
* Tail end of last failure (as of this morning):
*
* === Generating temporary packing list
* strip /usr/local/bin/jade
* strip /usr/local/bin/nsgmls
* /usr/libexec/elf/strip: /usr/local/bin/nsgmls: No such file or directory
* *** Error
On Feb 12 Jun Kuriyama wrote:
From: "Jordan K. Hubbard" [EMAIL PROTECTED]
=== Generating temporary packing list
strip /usr/local/bin/jade
strip /usr/local/bin/nsgmls
/usr/libexec/elf/strip: /usr/local/bin/nsgmls: No such file or directory
*** Error code 1
Stop in
* From: Jun Kuriyama [EMAIL PROTECTED]
* Sorry for that trouble. I have experience to see that, but it does
* not occur everytime in my environment.
Really? Interesting...I only have one jade failure in my entire list
of build logs (which date back to September 1999) and that one appears
Hi,
jack [EMAIL PROTECTED]wrote:
This isn't limited to -current. I just had something similar
happen with -stable.
=== Generating temporary packing list
strip /usr/local/bin/jade
/usr/libexec/elf/strip: /usr/local/bin/jade: No such file or directory
*** Error code 1
I also