Hi -
I have been told that the netperf.texi file for the netperf manual
(http://www.netperf.org/svn/netperf2_trunk/doc/ will successfully
convert to DVI when using version 5.X of texi2dvi, but not when using
version 4.13. I have been told this by some folks on the automake
mailing list.
4.13 is the version I happen to have on my development box (Ubuntu 12.04
distro), and I think that something other than 5.X is what the Debian
package maintainer for netperf has. He has asked that I disable
generation of .ps files to simplify the diffs between netperf upstream
and Debian. That is why I was starting at the automake mailing list -
looking to see if there was a way to get automake to not automagically
generate the .ps instructions. (There neither is, nor will there be a
way to...)
I suppose one path forward is just say "you must have texi2dvi from
5.x", but I am wondering if there might be something I could do with
netperf.texi to allow the pre 5.X texi2dvi to work with it successfully?
thanks and happy benchmarking,
rick jones
http://www.netperf.org/
--- Begin Message ---
On 05/01/2013 01:39 PM, Stefano Lattarini wrote:
On 05/01/2013 08:53 PM, Rick Jones wrote:
Anyway, what I have is whatever Ubuntu provides in 12.04:
raj@tardy:~$ automake --version
automake (GNU automake) 1.11.3
raj@tardy:~$ texi2dvi --version
texi2dvi (GNU Texinfo 4.13) 1.135
So this isn't a "bad versions of tools" issue.
Anyway, I can reproduce the failure with the vanilla tarball:
<http://ftp.de.debian.org/debian/pool/non-free/n/netperf/netperf_2.6.0.orig.tar.gz>
With that, "make dvi" fails for me. But so does this simple command:
$ cd doc && TEXINPUTS=".:$TEXINPUTS" /usr/bin/texi2dvi netperf.texi
which shows the issue has nothing to do with Automake. In fact, the above
works if I use Texinfo 5.x instead of Texinfo 4.13!
So, having estabilished Automake is not the guilty party, I'll let you
chase the issue from ere on. Good luck ;-)
To the texinfo mailing list I go then :)
rick
--- End Message ---
