Texinfo is a package for writing documentation, with tools to produce the
on-line and printed docs in several formats. Most GNU packages come with
their docs written and produced by Texinfo programs. The docs written as
part of the DJGPP project also use Texinfo.
By default info.exe looks at /dev/env/DJDIR/share/info to locate the info
docs, so there should be no more difficulties if other gnu packages place
their documentation in this new canonical directory.
See the file NEWS for a list of major changes in the current release.
DJGPP specific changes.
=======================
- This is a bug fix release. The previous version of this port was broken
because the used libsupp was brocken.
- To be able to compile the sources, towlower(), mblen(), mbsinit(),
mbtowc(), mbrtowc(), memmem(), snprintf() and the argz family of functions
are required. Also a mbstate_t structure (like the one provided by GNU glibc)
that allows to store the conversion state information is required. All this
will avoid to have to adjust the texinfo sources (to be more explicitly, the
multibyte iterator provided by gnulib) to the DJGPP peculiarities.
These functions are provided by libsupp.a, so you will need to install the
package:
ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/lsupp61a.zip
to configure and compile the source package, no matter if you use djdev203
or djev204. No one of the provided functions will offer reentrancy support
neither any multi-byte nor wide character support beyond the one provided
by DJGPP's libc itself. This also implies that the texinfo binaries will
not provide any multi-byte support except for the one that DJGPP provides.
- To run the testsuite the program mktemp.exe will be required, so you will
need to install the package:
ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/mktmp15b.zip
Both packages must be installed before you configure and compile the sources;
of course, if you are not interested in compiling the sources you do not need
at all to download and install neither lsupp61a.zip nor mktmp15b.zip.
As usual, all changes against the original sources are documented in the diffs
file stored in the /djgpp subdir.
Compiling the sources.
======================
As usual the sources are configured for stock djdev203.
- If you compile the sources with djdev203, you must proceed as usual running
the following commands from the top srcdir, this is texinfo4.13:
make
make check
make install
The tests ii-0041-test and ii-0050-test will always fail because the zdiff
script from the gzip port is brocken. I will fix this some day or may be
some interested user provides me with a solution.
- If you compile the sources with djdev204 it will be essential to
reconfigure sources because the distributed one have been configured for
djdev203. For this purpose you *must* delete the cache file config.cache
or you will get a broken binary.
In conclusion, to rebuild the sed binary with djdev204 to get a binary
usefull for WinXP run the following commands from the top srcdir (texinfo4.13):
rm config.cache
config.bat
make
make check
make install
Please note that the removing of the cache file is essential. As told
before the tests ii-0041-test and ii-0050-test will always fail because the
zdiff script from the gzip port is brocken.
Please do *not* report anything to <bug-t...@gnu.org>, if there
are problems with this port there are probably DJGPP originated and must
be discussed and solved here.
As usual, all djgpp specific files (config.bat, diffs, readme files, etc.)
are located in the /djgpp subdir.
The port consists of the usual three packages produced using stock djdev203
that can be downloaded from ftp.delorie.com and mirrors as (timestamp 2009-01-09):
Texinfo 4.13 binary, info and man format documentation:
ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/txi413br2.zip
Texinfo 4.13 dvi, html and ps format documentation:
ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/txi413dr2.zip
Texinfo 4.13 source:
ftp://ftp.delorie.com/pub/djgpp/current/v2gnu/txi413sr2.zip
For the convenience of the WinXP users the binaries has been produced a
second time using the djdev204 beta library. This package is available
at ftp.delorie.com and mirrors as (timestamp 2009-01-09):
Texinfo 4.13 binary, info and man format documentation:
ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/txi413br2.zip
Send texinfo specific bug reports to <bug-t...@gnu.org>
Send suggestions and bug reports concerning the DJGPP port to
comp.os.msdos.djgpp or <dj...@delorie.com>.
Enjoy.
Guerrero, Juan Manuel <juan.g...@gmx.de>
On Jan 9, 4:54 pm, "Juan Manuel Guerrero" <juan.guerr...@gmx.de>
wrote:
>
> This is release 2 of the port of GNU Texinfo 4.13 to MSDOS/DJGPP.
>
> - This is a bug fix release. The previous version of this port was broken
> because the used libsupp was brocken.
Okay, tested this r2 /beta/ version under Vista, no more crashes. So I
assume everything is okay now. ;-)
This is faulty. Your file names are exceeding 8 chars, and thus
are not DOS compatible. If you remove the final 'r' they will be
satisfactory.
--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home.att.net>
Try the download section.
Thanks!
> For the convenience of the WinXP users the binaries has been produced a
> second time using the djdev204 beta library.
What is special about Windows XP that its users might want the 2.04
version? I thought the v2.03 that's on DJGPP sites is fixed to work
around any XP DPMI-related bugs.
V2.03 fixed most, but not all XP problems. V2.04 is just more stable on XP.
Which XP problems aren't fixed in the latest v2.03 binaries?
I have encountered mysterious hangup problems with V2.03, but not with
V2.04. (Hangup like in freezing or stop responding).
Interesting. I use many pieces of the DJGPP toolchain daily on XP and have
never seen a problem. But those are mostly simple utilities.
My hanging programs are networking programs involving real-mode
callbacks from a packet driver and no or very few DOS operations
although BIOS is called regularly. I have also seen it happen on very
CPU intensive programs.
I suspect (without any proof) that XP decides that the process need
not be scheduled any more. Why V 2.04 solves the problem, I have no
idea.
Is anyone correcting these FAULTY file names.
The final b, d, or s normally describe binary, doc, and source
zips. So you would be better off removing the 'r' from the
filenames.
My point is that the filenames should be fixed on delorie.com, so
they can be properly downloaded onto DOS machines.