emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Olaf Meeuwissen <olaf.meeuwissen@avasys.jp>
To: Jude DaShiell <jdashiel@shellworld.net>
Cc: Michael Brand <michael.ch.brand@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: why was makefile changed to produce this?
Date: Tue, 18 Oct 2011 17:41:47 +0900	[thread overview]
Message-ID: <87ty767ktw.fsf@avasys.jp> (raw)
In-Reply-To: <alpine.BSF.2.00.1110180352370.10218@freire1.furyyjbeyq.arg> (Jude DaShiell's message of "Tue, 18 Oct 2011 03:54:44 -0400 (EDT)")

Jude DaShiell <jdashiel@shellworld.net> writes:

> For the record, this is a new installation of debian wheezy and 
> the makeinfo utility doesn't appear to be in the distribution let alone 
> on my system.

  sudo apt-get install texinfo

I usually keep a (somewhat stale) copy of Contents-$arch.gz around and
find necessary packages with

  zegrep bin/makeinfo Contents-$arch.gz

There is (was?) a package that would make package suggestions if a
command isn't found but I can't recall its name.
# Somewhat annoying when you make a typo but ...

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962               Help support software freedom
                 http://www.fsf.org/jf?referrer=1962

  reply	other threads:[~2011-10-18  8:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18  5:02 why was makefile changed to produce this? Jude DaShiell
2011-10-18  7:15 ` Michael Brand
2011-10-18  7:54   ` Jude DaShiell
2011-10-18  8:41     ` Olaf Meeuwissen [this message]
2011-10-18 13:10       ` [OT] " Nick Dokos
  -- strict thread matches above, loose matches on Subject: below --
2011-10-18  8:27 Jude DaShiell
2011-10-18 12:49 ` Nick Dokos
2011-10-18 23:14   ` Olaf Meeuwissen
2011-10-18 23:41     ` Nick Dokos
2011-10-19 11:26     ` Rémi Vanicat
2011-10-19 14:59       ` 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=87ty767ktw.fsf@avasys.jp \
    --to=olaf.meeuwissen@avasys.jp \
    --cc=emacs-orgmode@gnu.org \
    --cc=jdashiel@shellworld.net \
    --cc=michael.ch.brand@gmail.com \
    /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).