Re: texinfo problem

[Tom Tromey]

 Tim == Tim Van Holder [EMAIL PROTECTED] writes:

Tim Then again, you could simply mention this problem with missing in
Tim the docs and tell developers to configure using MAKEINFO=makeinfo
Tim if they intend to change the docs; that way, missing wouldn't be
Tim run and the problem wouldn't occur.

I wouldn't want to have to remember to do that.

Tom

Re: texinfo problem

[Tom Tromey]

 Alexandre == Alexandre Oliva [EMAIL PROTECTED] writes:

 I've noticed that if you try to build a texi file that has an error
 you get a warning from the `missing' program:

Alexandre Presumably missing should check, when the execution of a
Alexandre program fails, whether the program can be found in the PATH
Alexandre or not, and only report its warning if it finds the program
Alexandre is indeed missing.

Right now AM_MISSING_PROG looks like this:

AC_DEFUN([AM_MISSING_PROG],
[AC_REQUIRE([AM_MISSING_HAS_RUN])
$1=${$1-${am_missing_run}$2}
AC_SUBST($1)])

Ok, this makes sense.

Maybe for makeinfo and other GNU programs we could add a check to see
if `$1 --version' works.  If it does then we know we've found the
program.  That is, have a new AM_MISSING_GNU_PROG.  Comments?

Tom

Re: texinfo problem

[Alexandre Oliva]

On May 29, 2001, Tom Tromey [EMAIL PROTECTED] wrote:

 Alexandre == Alexandre Oliva [EMAIL PROTECTED] writes:
 I've noticed that if you try to build a texi file that has an error
 you get a warning from the `missing' program:

Alexandre Presumably missing should check, when the execution of a
Alexandre program fails, whether the program can be found in the PATH
Alexandre or not, and only report its warning if it finds the program
Alexandre is indeed missing.

 Right now AM_MISSING_PROG looks like this:

I was not thinking of AM_MISSING_PROG, but of the missing script
itself.

Currently, we have:

case $1 in
--run)
  # Try to run requested program, and just exit if it succeeds.
  run=
  shift
  $@  exit 0

My suggestion is to add a PATH search for $1 right after this command,
and just bail out if we find it, without getting a chance to print the
warning.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

texinfo problem

[Tom Tromey]

I've noticed that if you try to build a texi file that has an error
you get a warning from the `missing' program:

cd ../automake \
   /bin/sh /x2/egcs-stuff/automake/automake/lib/missing --run makeinfo `echo 
../automake/automake.texi | sed 's,.*/,,'`
./automake.texi:1675: Next field of node `A Library' not pointed to.
./automake.texi:1821: This node (LIBOBJS) has the bad Prev.
./automake.texi:1726: Prev field of node `Program and Library Variables' not pointed 
to.
./automake.texi:1675: This node (A Library) has the bad Next.
makeinfo: Removing output file `/x2/egcs-stuff/automake/automake/automake.info' due to 
errors; use --force to preserve.
WARNING: `makeinfo' is missing on your system.  You should only need it if
 you modified a `.texi' or `.texinfo' file, or any other file
 indirectly affecting the aspect of the manual.  The spurious
 call might also be the consequence of using a buggy `make' (AIX,
 DU, IRIX).  You might want to install the `Texinfo' package or
 the `GNU make' package.  Grab either from any GNU archive site.


This is bad because it is confusing.

Tom