[Top][All Lists]

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

Re: [bug #38795] texi2any makes CR in output when input is mixed CR-LF a

From: Vincent Belaïche
Subject: Re: [bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files
Date: Thu, 16 May 2013 22:27:27 +0200


>Yes, MSYS programs always use binary I/O mode, because they simulate a
>Posix environment.  They are therefore inappropriate for installing
>Info manuals on Windows, only for building those manuals.

The question is then what the purpose is for an MSYS install-info. I was
thinking that the purpose of MSYS at all was to install native windows
application using the autoconf system and the mingw compile chain.

If MSYS/install-info cannot be used to install manuals on Windows, then
it is completely useless --- or I misunderstood again what MSYS is for.

Also --- if it is essential to keep the binary mode for other reasons,
like having gzipped binary manual at input --- it would be probably easy
to make some work-around by assuming the potential presence of the CR
before end-of-line when scanning for the DIRENTRY.

That kind of fix could be there in all cases --- as it does not really
harm in the case that there is no addional CR in last position of the
line --- or you could make the fix only when install-info is built for

>You need to use a native Windows build of install-info.

Would that native windows build of install-info be usable instead of the
MSYS one as part of some MSYS automated build: most of the time
probably, but there would be corner cases when the filename path is some
MSYS specific path that is not understandable by Windows, e.g. some
absolute path name, or some fstab wrapped path.

This means that this solution is ok only if you ``curse'' Windows users
to call install-info manually :-(.

>> > However I could not achieve to do that because the Makefile and
>> > configure are not archieved in the CVS repo, and there does not
>> > seem to be any windows specific hand made configure + make like for
>> > EMACS. I tried to re-generate the Makefile+configure but that
>> > failed also: I got the following error
>> > 
>> > /local/bin/autoreconf
>> > Can't spawn "aclocal": No such file or directory at 
>> > /usr/autoconf/Autom4te/FileUtils.pm line 326.
>> > autoreconf: failed to run aclocal: No such file or directory
>This probably means you have an old version of autoconf.

What I get is:
/usr/local/bin>./autoreconf --version
La syntaxe de la commande est incorrecte.
autoreconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.

This is an autoconf which I installed from the savannah GNU source
gzipped-tar. I get the same ``La syntaxe de la commande est
incorrecte.'' preliminary message when the PATH is configured so that
"which perl" gives the PyPy MSYS perl, or when it is configured so that
"which perl" points as asctivestate native Windows perl.

>Do you really want to build Texinfo yourself, or do you just need a
>program that someone else built?  

No I am not trying by all means to build Texinfo myself, I would be
happy to have a Windows port that somebody else compiled, because I have
also some limitation with texi2any --- also because of my deficient
autoconf I could never install it correctly with the locale properly

> If the latter, you can find precompiled binaries here:
> http://sourceforge.net/projects/ezwinports/files/texinfo-5.1-2-w32-bin.zip/download
>There's a corresponding source zip there, which is already configured.
>So perhaps you will be able to build it by typing "make" into the MSYS
>shell window.

I will try that some day, when times allows... thank you so much, as
usual your help is quite precious !


reply via email to

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