From: Simon Marchi <firstname.lastname@example.org>
To: 好 <email@example.com>, firstname.lastname@example.org
Subject: Re: 【question】steps to regenerate configure file
Date: Sun, 10 Jul 2022 15:47:30 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
On 2022-07-08 06:38, 好 via Gdb wrote:
> Hi ,
> I want to modify some code of gdb, so I have to regenerate the configure file, but I didn't find the relevant documentation, I'm not sure which version of autogen to use?
> This is a bit confusing for newbies like me.
> I am going to regenerate the configuration as follows:
> autogen Makefile.def
> autogen Makefile.tpl
> When I type the command ```autogen Makefile.def``` the following error will appear, is my step wrong?
So, we're talking about top-level files here. I just tried with:
$ autogen --version
autogen (GNU AutoGen) 5.18.16
$ autogen Makefile.def
re-generates Makefile.in exactly as the version checked in the repo.
If you need to modify the configure files in gdbsupport, gdbserver and
gdb, I suggest using autoreconf, that will call all the right tools.
However, you must use the right version (2.69, at the moment) and use
the upstream version of autoconf/automake, not those packaged in
distros. Those often contain patches that modify the output, so you'll
get different results that don't match what is checked in the repo.
For example, in the gdb/ directory, I run:
$ autoreconf -f
prev parent reply other threads:[~2022-07-10 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 10:38 好
2022-07-10 19:47 ` Simon Marchi [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).