public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "kloczko.tomasz at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/31446] New: gdb/configure is not generated from gdb/configure.in
Date: Sat, 02 Mar 2024 21:17:45 +0000 [thread overview]
Message-ID: <bug-31446-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31446
Bug ID: 31446
Summary: gdb/configure is not generated from gdb/configure.in
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: kloczko.tomasz at gmail dot com
Target Milestone: ---
Looks like
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=4c9066e322f46faf9d753be6ff3e6a09ae668f86;hp=f8ab28d773dbf37d6e8ab4318ff0042dd742e9b8
shows that kept in VCS configure script has nothing to do with what is in
configure.in.
As long as now is not possible to regenerate all GNU autotools files this is
real problem
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-03-02 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 21:17 kloczko.tomasz at gmail dot com [this message]
2024-03-02 21:33 ` [Bug build/31446] " simon.marchi at polymtl dot ca
2024-03-02 21:34 ` 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@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).