[Top][All Lists]

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

Re: pdf documents won't build

From: Neil Jerram
Subject: Re: pdf documents won't build
Date: Thu, 02 Nov 2006 21:22:55 +0000
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

Ross Boylan <address@hidden> writes:

> I got the tarball for guile-1.6.8 and ran configure at the top level.  I
> did this solely to get the documentation.
> When I do make pdf from the top, I get (excerpt)
> make[1]: Entering directory `/usr/local/src/tools/guile-1.6.8/doc'
> Making pdf in ref
> make[2]: Entering directory `/usr/local/src/tools/guile-1.6.8/doc/ref'
> GUILE="/usr/local/src/tools/guile-1.6.8/pre-inst-guile" 
> ../../scripts/snarf-guile-m4-docs ../../guile-config/guile.m4 
> autoconf-macros.texi
> /usr/local/src/tools/guile-1.6.8/pre-inst-guile: line
> 83: /usr/local/src/tools/guile-1.6.8/libguile/guile: No such file or
> directory
> /usr/local/src/tools/guile-1.6.8/pre-inst-guile: line 83:
> exec: /usr/local/src/tools/guile-1.6.8/libguile/guile: cannot execute:
> No such file or directory
> make[2]: *** [autoconf-macros.texi] Error 126
> make[2]: Leaving directory `/usr/local/src/tools/guile-1.6.8/doc/ref'
> It looks as if maybe some other stuff needs to be built first, and the
> Makefile isn't picking up on it.

That's correct.  It's currently the case that you need to run a plain
"make" first.  Are you in a position to do that?

> I posted this to guile-user a few days ago.  Someone sent me prebuilt
> docs (for 1.8 actually, which isn't the one I'm using), along with the
> information that they built their docs on MS-Windows and could not build
> them under Linux.  That's been the only response, so I figured this
> might be a real bug and am filing this report.

Thanks; we appreciate your report.  Given that there is an easy
workaround, though, how important is this for you?

> I'm a bit surprised you don't have people enter bugs in the bug tracker;
> the BUGS file said to send an email like this.

I agree that it is unusual not to use a tracker these days, but
address@hidden is still for now our primary mechanism for reporting
and dealing with bug reports.


reply via email to

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