From: Simon Marchi <simon.marchi@polymtl.ca>
To: Zied Guermazi <zied.guermazi@trande.de>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: issue running automake on GDB source files to generate Makefile.in and config.in
Date: Wed, 10 Mar 2021 18:44:55 -0500 [thread overview]
Message-ID: <f6c37f84-035b-4dbc-b97f-974039787e30@polymtl.ca> (raw)
In-Reply-To: <6fa3c513-b65a-745e-234c-6b229de5d5db@trande.de>
On 2021-03-10 4:14 p.m., Zied Guermazi wrote:
> hi,
>
> to generate Makefile.in and config.in for gdb I am calling aclocal and then automake
>
> when runnig automake in the binutils-gdb and gdb folders, on the head of the master branch, I am getting following error
>
> "configure.ac: error: no proper invocation of AM_INIT_AUTOMAKE was found.
> configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
> configure.ac: that aclocal.m4 is present in the top-level directory,
> configure.ac: and that aclocal.m4 was recently regenerated (using aclocal)
> automake: error: no 'Makefile.am' found for any configure output"
>
> I am using automake (GNU automake) 1.16.1. the same was tried with automake (GNU automake) 1.15.1
>
> please advise on how to generate Makefile.in and config.in files from configure.ac (and gdbsupport/common.m4) file
What I do is:
1. build autoconf/automake with the right versions from source, install
them in a prefix of their own (e.g. /opt/autostuff) and add it to my
PATH when I want to use them. This is because versions distributed by
distros are sometimes patched and produce a different output.
2. in either gdb/, gdbserver/ or gdbsupport/ (and not in the top-level),
run `autoreconf -vf`. This takes care of calling the right autotools
under the hood, which I don't know much about. It calls automake if
there is a Makefile.am (like in gdbsupport) and doesn't if there
isn't (like in gdb) - at least that's what I understand.
> is there a well configured build server I can use to automatically generate those files?
No, unfortunately. But it shouldn't be too difficult to get it working
in your local environment following the steps above. This process is
not too obvious, and should probably be documented in the wiki, if it
isn't already.
Simon
next prev parent reply other threads:[~2021-03-10 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 21:14 Zied Guermazi
2021-03-10 23:44 ` Simon Marchi [this message]
2021-03-11 8:26 ` Andreas Schwab
2021-03-11 15:37 ` Mike Frysinger
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=f6c37f84-035b-4dbc-b97f-974039787e30@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=zied.guermazi@trande.de \
/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).