public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/31446] gdb/configure is not generated from gdb/configure.in
Date: Sat, 02 Mar 2024 21:33:43 +0000 [thread overview]
Message-ID: <bug-31446-4717-XGkvUpJ7CO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31446-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31446
Simon Marchi <simon.marchi at polymtl dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simon.marchi at polymtl dot ca
--- Comment #1 from Simon Marchi <simon.marchi at polymtl dot ca> ---
configure.in does not even exists, not sure what you are talking about. We
regenerate configure (and the other files that go along with it) all the time.
You just need the proper version of autoconf (2.69) and automake (1.15.1). It
is encouraged to build your own rather than use the distro provided ones,
because some distros (e.g. Debian) have local patches that make the output
different from what is checked in.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-02 21:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 21:17 [Bug build/31446] New: " kloczko.tomasz at gmail dot com
2024-03-02 21:33 ` simon.marchi at polymtl dot ca [this message]
2024-03-02 21:34 ` [Bug build/31446] " simon.marchi at polymtl dot ca
2024-03-02 21:35 ` sam at gentoo dot org
2024-03-02 21:40 ` kloczko.tomasz at gmail dot com
2024-03-02 21:41 ` sam at gentoo dot org
2024-03-02 21:43 ` kloczko.tomasz at gmail dot com
2024-03-02 21:43 ` sam at gentoo dot org
2024-03-02 21:45 ` kloczko.tomasz at gmail dot com
2024-03-02 21:48 ` kloczko.tomasz at gmail dot com
2024-03-02 21:49 ` sam at gentoo dot org
2024-03-02 21:54 ` kloczko.tomasz at gmail dot com
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=bug-31446-4717-XGkvUpJ7CO@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).