From: Tuomo Keskitalo <tuomo.keskitalo@iki.fi>
To: Brian Gough <bjg@gnu.org>
Cc: GSL Discuss Mailing List <gsl-discuss@sourceware.org>
Subject: Re: make doc, problem with derivative/prime/apostrophe
Date: Tue, 26 Apr 2011 11:01:00 -0000 [thread overview]
Message-ID: <BANLkTi=PcAXjcJyg4pgJ1FX6WgSGrDHdOA@mail.gmail.com> (raw)
In-Reply-To: <43hb9mimmy.wl%bjg@gnu.org>
Ok, thanks for confirmation! I finally got it to work (I'm not too
familiar with texinfo..)
For others who might have this problem: The file doc/texinfo.tex seems
to be overwritten by the system's version of texinfo.tex when you run
autoreconf. I simply replaced the original doc/texinfo.tex file from
GSL source before making the documentation via e.g. "make ps". At
least that worked for me.
On Mon, Apr 25, 2011 at 2:41 PM, Brian Gough <bjg@gnu.org> wrote:
> At Mon, 25 Apr 2011 12:58:38 +0300,
> Tuomo Keskitalo wrote:
>> I still have this problem in Ubuntu 10.04 and 10.10, even after
>> upgrading info, install-info and texinfo .debs to version
>> 4.13a.dfsg.1-6. Are you sure the problem is texinfo and not e.g.
>> texlive? In my case etex process hangs in a loop using lot of CPU
>> cycles.. I'm not sure where to file this bug.
>
> The problem was definitely in Texinfo and it was fixed in CVS in Feb
> 2010 after I reported it. There have only been snapshot releases of
> the texinfo.tex file since then and a not full Texinfo release so the
> distributions have not picked it up.
>
> http://cvs.savannah.gnu.org/viewvc/texinfo/texinfo/doc/texinfo.tex?r1=1.306&r2=1.307
>
> --
> Brian Gough
>
>
--
Tuomo.Keskitalo@iki.fi
http://iki.fi/tuomo.keskitalo
next prev parent reply other threads:[~2011-04-26 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 11:45 Tuomo Keskitalo
2010-10-12 15:11 ` Brian Gough
2011-04-26 11:01 ` Tuomo Keskitalo
2011-04-25 11:42 ` Brian Gough
2011-04-26 11:01 ` Tuomo Keskitalo [this message]
2011-04-25 21:06 ` Brian Gough
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=PcAXjcJyg4pgJ1FX6WgSGrDHdOA@mail.gmail.com' \
--to=tuomo.keskitalo@iki.fi \
--cc=bjg@gnu.org \
--cc=gsl-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).