From: Peter Dyballa <Peter_Dyballa@web.de>
To: Samuel Wales <samologist@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: configuring emacs: AM_INIT_AUTOMAKE: command not found
Date: Tue, 21 Jun 2011 00:48:39 +0200 [thread overview]
Message-ID: <8B5DF23C-2E4A-4262-8576-65DD42CBE145@web.de> (raw)
In-Reply-To: <BANLkTin+ZO2+3WRx2X3CwJL7b9mQeKj6cw@mail.gmail.com>
Am 20.06.2011 um 23:53 schrieb Samuel Wales:
>> Update (bzr pull -v) and try again!
>
> Is it OK to use the git version?
I don't know! In my assumption the GIT repository is a bit unofficial...
> Ran ./configure
>
> Same error.
In which tool are you running git and configure? Emacs? In compilation-
mode? Is PATH set correctly that the up-to-date tools are found? (In a
shell 'echo $PATH ; which autoconf automake' will work, in a
*compilation* buffer the same as compile command works as well.)
>
> Of course all this last stuff is me not knowing what I am doing with
> these tools, not me saying they should work.
I am also kind of a newbie with these tools. OTOH, I am pretty sure
that one does not need to know how these tools work and how and why
they get invoked. Usually the configure script and make/Makefile know
exactly what they need to do. My assumption is that two things can be
wrong: your environment (PATH value, tools, their versions) or the
source. The latter gets healed automatically... Waiting one or two
(more) days should help. (Otherwise you could send an eMail to the
address given when you select 'Send Bug Report…' from the Help menu.)
--
Greetings
Pete
If we don't succeed, we run the risk of failure.
– George W. Bush
next prev parent reply other threads:[~2011-06-20 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 21:12 configuring emacs: AM_INIT_AUTOMAKE: command not found Samuel Wales
2011-06-20 12:43 ` Peter Dyballa
2011-06-20 17:30 ` Samuel Wales
2011-06-20 21:26 ` Peter Dyballa
2011-06-20 21:53 ` Samuel Wales
2011-06-20 22:48 ` Peter Dyballa [this message]
2011-06-20 23:15 ` Samuel Wales
2011-06-20 23:24 ` Peter Dyballa
2011-06-20 23:41 ` Samuel Wales
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=8B5DF23C-2E4A-4262-8576-65DD42CBE145@web.de \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=samologist@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.
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).