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: Fri, 6 Apr 2012 10:59:32 +0200 [thread overview]
Message-ID: <40EE573D-AA6A-4130-9659-599DC472EB90@Web.DE> (raw)
In-Reply-To: <20120406.170147.2111159149405289913.kuroishi@iij.ad.jp>
Am 6.4.2012 um 10:01 schrieb Kuroishi Mitsuo:
> Error: (error "Running bzr status dired.el...FAILED (status 1)")
> Running bzr status ../../../../../a/jc-nhfs/export/nfs/home/kuroishi/download/emacs/lisp/dired.el...FAILED (status 1)
> gmake[3]: *** [autoloads] エラー 255
You need to be on-line, the bzr server needs to be on-line... This is, IMO, not really a build failure – it looks good. The other cure is to use a different method to check-out the sources and update with 'bzr pull'. Then no on-line connection is needed at compile time. I think this method is (or was) also described on the Savannah server.
BTW, Mitsuo, you can use
env LC_ALL=C MAKE=gmake ./configure ...
env LC_ALL=C gmake ...
in order to get output messages in English.
--
Greetings
Pete
"Klingons do not believe in indentation - except perhaps in the skulls of their project managers."
next prev parent reply other threads:[~2012-04-06 8:59 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
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 [this message]
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=40EE573D-AA6A-4130-9659-599DC472EB90@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).