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] gdb/configure is not generated from gdb/configure.in Date: Sat, 02 Mar 2024 21:48:13 +0000 [thread overview] Message-ID: <bug-31446-4717-XQnl8zxQ5D@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31446-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31446 --- Comment #9 from kloczek <kloczko.tomasz at gmail dot com> --- (In reply to Simon Marchi from comment #2) > Precision: the configure file is generated from configure.ac. Of course because it is gdb/configure.ac https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdb/configure.ac;h=aa91bfb3a1731ebd2421d4c482354cd86be987b5;hb=HEAD(In reply to Sam James from comment #7) > https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdb/configure; > h=d0fd1760b889c6ac30ecf1004ac1d39622081cbb;hb=HEAD#l27035 Nevertheless in dist tar ball there is no that change. Is it possible to release 14.1.1? -- 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:48 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 ` [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 [this message] 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-XQnl8zxQ5D@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: linkBe 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).