From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: make doc failing
Date: Sun, 29 Dec 2013 12:58:01 -0500 [thread overview]
Message-ID: <87bnzzlety.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: CAJ+TeoeNh5hsjSw1mgSqb3=5njFbC+ZeXMfTaW_5H3rJGZFeHg@mail.gmail.com
Rustom Mody <rustompmody@gmail.com> writes:
> Nick wrote:
>> I tried last night and again tonight after pulling: I get no errors
>> with `make doc'.
>
> And I continue to get the errors with no doc (pdf) built.
> I can attach the build messages (800 lines)
> For now some snippets of what I see
>
> git pull
> Already up-to-date.
> ...
>
> texi2pdf --batch --clean --expand org.texi
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LANG = "C "
> are supported and installed on your system.
Where does perl come into the picture? Both texi2pdf and the program it
calls, texi2dvi, are shell scripts. The only references to perl I find
are in the run_hevea() function of texi2dvi and in the target making
the orgcard in the doc Makefile. But that should not cause the PDF
manual problems
>
> ...
>
> Cannot open load file: ob-sh
ob-sh does not exist any more. Check your local.mk and delete it if it's
there - I had the same problem because I had added it to
BTEST_OB_LANGUAGES.
Nick
next prev parent reply other threads:[~2013-12-29 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 3:36 make doc failing Rustom Mody
2013-12-28 5:01 ` Rustom Mody
2013-12-29 17:15 ` Rustom Mody
2013-12-29 17:58 ` Nick Dokos [this message]
2013-12-30 2:21 ` Rustom Mody
2013-12-30 5:47 ` Nick Dokos
2013-12-30 5:57 ` Rustom Mody
2013-12-30 10:06 ` Vladimir Lomov
2013-12-30 15:23 ` Rustom Mody
2013-12-31 5:12 ` Rustom Mody
2013-12-30 10:33 ` Achim Gratz
2013-12-29 5:07 ` Nick Dokos
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bnzzlety.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).