[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cannot make doc

From: Francisco Vila
Subject: Re: Cannot make doc
Date: Wed, 9 Dec 2009 20:19:33 +0100

2009/12/9 John Mandereau <address@hidden>:
> Le samedi 05 décembre 2009 à 11:18 +0000, Graham Percival a écrit :
>> I've seen similar messages when attempting to build it on GUB,
>> although they specify /contributor/ instead.
> Please send me the same info I asked in my reply to Francisco, otherwise
> there is little chance I see why and/or the
> init file breaks for you in GUB build.

Thank you, now I have upgraded texi2html to v1.82 and have been able
to complete the process.  I uncompressed it from the deb package[1]
because I can no longer compile it:

make[2]: Entering directory `/home/fravd/source/texi2html/po_messages'
/usr/bin/xgettext --default-domain=texi2html --directory=.. \
          --add-comments=TRANSLATORS: --language=Perl -k__ -k\/usr/bin/make_
-k%__ -k__x -k__n:1,2 -k__nx:1,2 -k__xn:1,2 -kN__ \
          --files-from=./ \
          --copyright-holder='Free Software Foundation, Inc.' \
/usr/bin/xgettext: warning: The option --msgid-bugs-address was not specified.
                            If you are using a `Makevars' file, please specify
                            the MSGID_BUGS_ADDRESS variable there;
otherwise please
                            specify an --msgid-bugs-address command line option.
../ invalid variable interpolation at "@"
make[2]: *** [texi2html.pot-update] Error 1
make[2]: Leaving directory `/home/fravd/source/texi2html/po_messages'
make[1]: *** [texi2html.pot] Error 2
make[1]: Leaving directory `/home/fravd/source/texi2html/po_messages'
make: *** [all-recursive] Error 1

The dirty hack was to uncompress the data/ directory from the .deb package with

  $ sudo tar -xvzf data.tar.gz -C /

Installing the package the standard way does not work, either; I need
to upgrade dpkg and libc6 as well. I think this is too much for a
single-file perl script.

Francisco Vila. Badajoz (Spain)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]