Re: [bug #45759] Can't find Texinfo::ModulePath

[Vincent Belaïche]

Hello Gavin,

My answers below

>
>
>On 14 August 2015 at 20:03, Vincent Belaïche
><address@hidden> wrote:
>>>> Can't locate Texinfo/ModulePath.pm in @INC (@INC contains:
>>>> c:/Nos_Programmes/msys/lib/perl5/site_perl/5.8/../tp 
>>>> /usr/lib/perl5/5.8/msys
>>>> /usr/lib/perl5/5.8 /usr/lib/perl5/site_perl/5.8/msys

[...]

>>
>
>I get:
>
>bash $perl Makefile.PL
>Warning: prerequisite Locale::Messages 0 not found.
>Warning: prerequisite Text::Unidecode 0 not found.
>Warning: prerequisite Unicode::EastAsianWidth 0 not found.
>Writing Makefile for Texinfo
>Writing MYMETA.yml and MYMETA.json
>
>However, up until this point I didn't even know there was such a file
>as Makefile.PL in that directory!
>
>When you run "make install" under the "tp/" subdirectory, that is
>supposed to use a Makefile generated from Makefile.am, not
>Makefile.PL. This is probably the root of your problems: your "svn
>update" updated Makefile.am, but there were no Makefile-updating rules
>in your current Makefile, so you were still using the old Makefile,
>generated from Makefile.PL. That also explains why texi2any.pl was
>installed.
>

Ok, in fact what really happened was that I had a shell script of mine
doing all the svn update, autogen, automake, configure, etc..., but this
script did not work in the first place because my svn working directory
needed svn upgrade. Then I just did it manually without paying attention
to my script, and I mistakenly used the Makefile.PL --- but maybe it did
not work and the Makefile under the tp directory was something from an
older run of automake.

>I'm not sure what the Makefile.PL is doing there; we should probably
>delete it (okay Patrice?).
>
>Vincent: there've been changes to the top-level configure.ac script as
>well, so for the best chance of success, I suggest running
>./autogen.sh at the top-level, followed by configure and make.

I tried that, and it seems that autogen did not fully worked, as what I
got is the following:

 $ ./autogen.sh
-| Preparing Texinfo development infrastructure:
-|   ./tp/maintain/regenerate_file_lists.pl
-|   (cd tp && ./maintain/regenerate_docstr.sh Makefile.docstr)
-|   (cd tp/tests && ../maintain/regenerate_cmd_tests.sh Makefile.onetst . 
-base 'formatting' -long 'sectioning coverage indices nested_formats contents 
layout' -tex_html 'tex_html')
-|   (cd tp/tests/htmlxref && ../../maintain/regenerate_cmd_tests.sh 
Makefile.onetst htmlxref -base .)
-|   (cd tp/tests/htmlxref-only_mono && ../../maintain/regenerate_cmd_tests.sh 
Makefile.onetst htmlxref-only_mono -base .)
-|   (cd tp/tests/htmlxref-only_split && ../../maintain/regenerate_cmd_tests.sh 
Makefile.onetst htmlxref-only_split -base .)
-|   aclocal -I gnulib/m4 && autoconf && autoheader && automake
-|   (cd tp/Texinfo/Convert/XSParagraph && autoreconf --install)
-| configure.ac:64: installing './compile'
-| configure.ac:67: installing './config.guess'
-| configure.ac:67: installing './config.sub'
-| configure.ac:2: installing './install-sh'
-| configure.ac:2: installing './missing'
-| Makefile.am:64: error: Libtool library used but 'LIBTOOL' is undefined
-| Makefile.am:64:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
-| Makefile.am:64:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
-| Makefile.am:64:   If 'LT_INIT' is in 'configure.ac', make sure
-| Makefile.am:64:   its definition is in aclocal's search path.
-| Makefile.am: installing './depcomp'
-| lib/Makefile.am:31: error: Libtool library used but 'LIBTOOL' is undefined
-| lib/Makefile.am:31:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
-| lib/Makefile.am:31:   to 'configure.ac' and run 'aclocal' and 'autoconf' 
again.
-| lib/Makefile.am:31:   If 'LT_INIT' is in 'configure.ac', make sure
-| lib/Makefile.am:31:   its definition is in aclocal's search path.
-| autoreconf: failed to run automake: Bad file number

FYI, I checked that there is no LT_INIT in the configure.ac, neither
AM_PROG_LIBTOOL.


> If you get errors relating to an "XSParagraph" subdirectory, try using
>a different Perl installation, if you have one, with "./configure
>PERL=/where/ever/perl".

Ok, good to know, I have two perl installations on my machine, the MSYS
perl, and the activestate perl. I can use whichever to run texi2any
because I did a CPP wrapper to call it, and this wrapper will call the
correct perl installation.

> The Perl installation must be set up to compile
>extension modules. Running "perl -V" can provide some clues as to
>whether this is possible. If this fails, try "./configure
>--disable-perl-xs"; this, however, will lead makeinfo to be
>considerably slower when outputting an Info file.
>
>
  VBR,
        Vincent Belaïche,


---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
http://www.avast.com