[Bug build/13012] New: build fails because glibc internal __SIGRTMIN is being accessed

[Bug build/13012] New: build fails because glibc internal __SIGRTMIN is being accessed

[wkor97gy0eef1fr at p dot mintemail.com]

http://sourceware.org/bugzilla/show_bug.cgi?id=13012

           Summary: build fails because glibc internal __SIGRTMIN is being
                    accessed
           Product: gdb
           Version: 7.2
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
        AssignedTo: unassigned@sourceware.org
        ReportedBy: wkor97gy0eef1fr@p.mintemail.com


using an alternate libc (musl 0.7.2) the build fails.

linux-nat.c: In function `lin_thread_get_thread_signals':
linux-nat.c:5777: error: `__SIGRTMIN' undeclared (first use in this function)

solution: use SIGRTMIN ?

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug build/13012] build fails because glibc internal __SIGRTMIN is being accessed

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=13012

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2011-08-03 20:41:30 UTC ---
I think if you want this to work, you will have to send
patches and test them against glibc as well.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug build/13012] build fails because glibc internal __SIGRTMIN is being accessed

[simark at simark dot ca]

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|WAITING                     |RESOLVED
                 CC|                            |simark at simark dot ca

--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
I just build GDB on Alpine Linux (musl 1.1.24) and it worked fine.

This was likely fixed by

https://sourceware.org/pipermail/gdb-patches/2015-October/128532.html

So I'm closing the bug.

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