public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Gallager <egall@gwmail.gwu.edu>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Zopolis0 <creatorsmithmdt@gmail.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: How to regenerate aclocal.m4?
Date: Mon, 2 May 2022 16:50:00 -0400	[thread overview]
Message-ID: <CAMfHzOuveR9YA0SCdQROGtX0b7B78XBahiyuBMf5FuAOL7h7RQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2205020006000.9383@angie.orcam.me.uk>

On Sun, May 1, 2022 at 7:09 PM Maciej W. Rozycki <macro@orcam.me.uk> wrote:
>
> On Sat, 30 Apr 2022, Zopolis0 via Gcc wrote:
>
> > I'm trying to regenerate autotools files in liboffloadmic (and other
> > directories) but when running automake it tells me I need to run aclocal,
> > which gives me a warning about not finding AM_ENABLE_MULTILIB in library,
> > which then translates into an autoconf error. How do I fix this? Is there a
> > specific aclocal version?
>
>  You need to use the same options that automatic regeneration via `make'
> would.  They are given in ACLOCAL_AMFLAGS near the top of Makefile.am.
>
>  HTH,
>
>   Maciej

To go a bit further into detail, what's necessary is that the correct
directory is searched for macro includes. AM_ENABLE_MULTILIB is
defined in `config/multi.m4`, so you need `-I config` in the flags you
use with aclocal (or whatever the relative path to config is from your
current working directory).

Eric

      reply	other threads:[~2022-05-02 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30  1:29 Zopolis0
2022-05-01 23:08 ` Maciej W. Rozycki
2022-05-02 20:50   ` Eric Gallager [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=CAMfHzOuveR9YA0SCdQROGtX0b7B78XBahiyuBMf5FuAOL7h7RQ@mail.gmail.com \
    --to=egall@gwmail.gwu.edu \
    --cc=creatorsmithmdt@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=macro@orcam.me.uk \
    /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).