From: Nick Dokos <nicholas.dokos@hp.com>
To: Greg Lucas <greg@glucas.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unable to 'make oldorg'
Date: Fri, 18 May 2012 14:08:42 -0400 [thread overview]
Message-ID: <9044.1337364522@alphaville> (raw)
In-Reply-To: Message from Greg Lucas <greg@glucas.net> of "Fri, 18 May 2012 18:02:20 -0000." <loom.20120518T195029-146@post.gmane.org>
Greg Lucas <greg@glucas.net> wrote:
> I'm trying to build using the "oldorg" target. (I'm use el-get and the
> recipe relies on "oldorg".) On my OS X machine this is failing because
> I don't have Tex (see output below). This was not a requirement
> before.
>
> I believe the problem is a recent change to targets.mk that made "doc"
> a prerequisite to "compile". I'm not familiar enough with this build
> to understand the reason for this change or propose an alternative
> that would keep "oldorg" working as before.
>
Try editing local.mk and uncomment the line
# ORG_MAKE_DOC = info # html pdf
Nick
> output:
>
> make -C doc info
> make[1]: Nothing to be done for `info'.
> make -C doc html
> make[1]: Nothing to be done for `html'.
> make -C doc pdf
> texi2pdf --batch --clean org.texi
> You don't have a working TeX binary (tex) installed anywhere in
> your PATH, and texi2dvi cannot proceed without one. If you want to use
> this script, you'll need to install TeX (if you don't have it) or change
> your PATH or TEX environment variable (if you do). See the --help
> output for more details.
>
> For information about obtaining TeX, please see http://www.tug.org. If
> you happen to be using Debian, you can get it with this command:
> apt-get install tetex-bin
> make[1]: *** [org.pdf] Error 1
> make: *** [pdf] Error 2
>
>
next prev parent reply other threads:[~2012-05-18 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 18:02 Unable to 'make oldorg' Greg Lucas
2012-05-18 18:08 ` Nick Dokos [this message]
2012-05-18 18:32 ` Achim Gratz
2012-05-19 6:27 ` Bastien
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=9044.1337364522@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=greg@glucas.net \
/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).