public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "maillist-gdb at barfooze dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/16370] building gdb fails when bash is not installed Date: Mon, 12 May 2014 13:57:00 -0000 [thread overview] Message-ID: <bug-16370-4717-RvMo7xE61o@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16370-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16370 --- Comment #9 from maillist-gdb at barfooze dot de --- ncopa, thanks for your findings. i can confirm that this patch http://git.proteanos.com/pkg/gdb.git/tree/patches/02_fix-opcodes-configure-bfd-version-on-busybox-ash.patch fixes the issue in gdb 7.6.2. i wonder if the new sed command in that line is not ERE conforming. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-05-12 13:57 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-26 22:20 [Bug build/16370] New: building gcc " maillist-gdb at barfooze dot de 2013-12-26 22:21 ` [Bug build/16370] building gdb " maillist-gdb at barfooze dot de 2013-12-27 0:46 ` maillist-gdb at barfooze dot de 2013-12-27 20:26 ` sergiodj at redhat dot com 2014-01-08 4:12 ` sergiodj at redhat dot com 2014-03-21 1:58 ` maillist-gdb at barfooze dot de 2014-03-21 3:44 ` sergiodj at redhat dot com 2014-05-05 11:19 ` ncopa at alpinelinux dot org 2014-05-06 6:20 ` ncopa at alpinelinux dot org 2014-05-06 7:07 ` ncopa at alpinelinux dot org 2014-05-06 15:03 ` ncopa at alpinelinux dot org 2014-05-12 13:57 ` maillist-gdb at barfooze dot de [this message] 2014-05-15 11:22 ` ncopa at alpinelinux dot org 2014-05-15 15:51 ` maillist-gdb at barfooze dot de 2014-06-30 18:44 ` maillist-gdb at barfooze dot de 2022-11-24 5:04 ` amodra 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-16370-4717-RvMo7xE61o@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).