From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Kuroishi Mitsuo <kuroishi@iij.ad.jp>
Cc: help-gnu-emacs@gnu.org
Subject: Re: makeinfo: missing file argument
Date: Thu, 5 Apr 2012 15:31:51 +0200 [thread overview]
Message-ID: <1F227D90-7C7A-48CF-A303-93745460FCC2@Web.DE> (raw)
In-Reply-To: <20120405.222206.806577941401312353.kuroishi@iij.ad.jp>
Am 5.4.2012 um 15:22 schrieb Kuroishi Mitsuo:
> You mean it needs to try to do entire build process in another
> Emacs or so, right?
No, it was just meant to use a build environment that is not polluted or limited by some terminal emulation programme. This programme can be the culprit. Or a setting. Settings can be in your shell or they can be for the programme (or X client). This is much too hard to debug. So some GNU Emacs is a perfect choice.
> Do you have the file ~/download/emacs/doc/emacs/emacs.texi?
>
> Yes, like below.
>
> % ls -la ~/download/emacs/doc/emacs/emacs.texi
> -rw-r--r-- 1 kuroishi staff 71616 4 4 10:17 /home/kuroishi/download/emacs/doc/emacs/emacs.texi
Has the same size as mine – there must be some bug in the build system.
Since the docs are not really necessary to run GNU Emacs, you could try to compile with 'make -k bootstrap' or just 'make -k' if the bootstrap argument makes make very picky and not forgive errors in this early stage. Then make will not stop when it sees an error. This way the src/emacs binary could be built. And it is, without installation, fully usable!
--
Greetings
Pete
Bake pizza not war!
next prev parent reply other threads:[~2012-04-05 13:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 1:53 makeinfo: missing file argument Kuroishi Mitsuo
2012-04-04 16:00 ` Peter Dyballa
2012-04-05 0:18 ` Kuroishi Mitsuo
2012-04-05 9:23 ` Peter Dyballa
2012-04-05 13:22 ` Kuroishi Mitsuo
2012-04-05 13:31 ` Peter Dyballa [this message]
2012-04-05 16:26 ` Glenn Morris
2012-04-05 18:14 ` Peter Dyballa
2012-04-06 0:38 ` Kuroishi Mitsuo
2012-04-06 7:06 ` Glenn Morris
2012-04-06 7:22 ` Kuroishi Mitsuo
2012-04-06 7:32 ` Glenn Morris
2012-04-06 7:37 ` Glenn Morris
2012-04-06 9:16 ` Peter Dyballa
2012-04-07 19:26 ` Glenn Morris
2012-04-08 0:13 ` Peter Dyballa
2012-04-08 6:01 ` Kuroishi Mitsuo
2012-04-06 8:01 ` Kuroishi Mitsuo
2012-04-06 8:47 ` Kuroishi Mitsuo
2012-04-06 8:59 ` Peter Dyballa
2012-04-06 9:15 ` Kuroishi Mitsuo
2012-04-06 9:52 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1F227D90-7C7A-48CF-A303-93745460FCC2@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=kuroishi@iij.ad.jp \
/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).