On 07/29/2012 03:41 AM, address@hidden wrote:
> Message: 2
> Date: Sun, 29 Jul 2012 08:47:03 +0200
> From: marco atzeri <address@hidden>
> To: "address@hidden" <address@hidden>
> Subject: doc-J and doc-j anchors
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> it seems makeinfo does not like a latest doc change
>
> Is it cygwin specific ?
>
> -----------------------------------------------------------------------------
> if /bin/sh /pub/hg/octave/build-aux/missing --run makeinfo --html -I
> ../../../octave/doc/interpreter \
> -o octave.htp ../../../octave/doc/interpreter/octave.texi; \
> then \
> rm -rf octave.html; \
> if test ! -d octave.htp && test -d octave; then \
> mv octave octave.html; else mv octave.htp octave.html; fi; \
> else \
> if test ! -d octave.htp && test -d octave; then \
> rm -rf octave; else rm -Rf octave.htp octave.html; fi; \
> exit 1; \
> fi
> ./arith.texi:2289: Anchors `doc-J' and `doc-j' map to the same file name.
> ./arith.texi:2289: @anchor command ignored; references to it will not work.
> ./arith.texi:2289: Rename this anchor or use the `--no-split' option.
> ./arith.texi:2291: Anchors `doc-I' and `doc-i' map to the same file name.
> ./arith.texi:2291: @anchor command ignored; references to it will not work.
> ./arith.texi:2291: Rename this anchor or use the `--no-split' option.
> makeinfo: Removing output file
> `/pub/hg/octave_build/doc/interpreter/octave.htp/index.html' due to
> errors; use --force to preserve.
> Makefile:1947: recipe for target `octave.html' failed
> make[3]: *** [octave.html] Error 1
> ---------------------------------------------------------------------
Marco,
It sure looks like it is Cygwin specific. It passes on Linux and Mac OS
systems which probably means it is related to case sensitivity in file names.
The warning message mentions a possible fix. Could you try executing the
command that generates the html documentation but include the '--no-split
option'?
This will actually affect any Windows-based system. Is it possible to avoid case-sensitivity issued in the .texi file instead?
Michael.