From: Brian Jones <cbj@gnu.org>
To: Brian Call <bcall@precise.com>
Cc: "'mauve-discuss@sources.redhat.com'" <mauve-discuss@sources.redhat.com>
Subject: Re: Autoconf problems?
Date: Wed, 16 Apr 2003 20:24:00 -0000 [thread overview]
Message-ID: <m3iste196m.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <3FCEB666DA97D511BA840002A564C1D986B4CE@EXCHANGE-CO>
Brian Call <bcall@precise.com> writes:
> Hi Guys,
>
> I'm having some problems getting autoconf to generate the configure script.
> I'm not much of a wiz with autoconf but I've tried everything I can think of
> (including getting the latest version) to no avail. Here are the error
> messages I'm seeing when running the autoconf from the mauve base directory:
I'll probably regret responding without trying myself... but the usual
invocation from CVS is `aclocal;automake;autoconf'. aclocal updates
aclocal.m4 which is where autoconf should find the macros you
mention. aclocal should complain if it cannot find them in
/usr/share/aclocal/. Hope that helps.
Brian
--
Brian Jones <cbj@gnu.org>
prev parent reply other threads:[~2003-04-16 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 18:54 Brian Call
2003-04-16 20:24 ` Brian Jones [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3iste196m.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=bcall@precise.com \
--cc=mauve-discuss@sources.redhat.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).