public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/13011] GDB fails to build against Linux libc's (e.g. musl) without dladdr and libthread_db
Date: Sat, 26 Sep 2015 05:13:00 -0000	[thread overview]
Message-ID: <bug-13011-4717-GjCrYOM3vo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13011-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=13011

Doug Evans <xdje42 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |xdje42 at gmail dot com
         Resolution|---                         |FIXED

--- Comment #3 from Doug Evans <xdje42 at gmail dot com> ---
gdb and gdbserver build with musl now.
gdb requires a couple of minor patches, but they're not libthread_db related.

There's still a plethora of other issues of course.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


      parent reply	other threads:[~2015-09-26  5:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 16:19 [Bug build/13011] New: GDB accesses internals of glibc's dynamic loader, failing to build with alternate libc wkor97gy0eef1fr at p dot mintemail.com
2011-07-31 18:59 ` [Bug build/13011] GDB fails to build against Linux libc's (e.g. musl) without dladdr and libthread_db ppluzhnikov at google dot com
2011-07-31 19:00 ` ppluzhnikov at google dot com
2012-10-21 14:37 ` bugdal at aerifal dot cx
2015-09-26  5:13 ` xdje42 at gmail dot com [this message]

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-13011-4717-GjCrYOM3vo@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).