[Bug ports/10527] New: SOCK_NONBLOCK does not match the kernel value

View: New views
5 Messages — Rating Filter:   Alert me  

[Bug ports/10527] New: SOCK_NONBLOCK does not match the kernel value

by Bugzilla from sourceware-bugzilla@sourceware.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

SOCK_NONBLOCK on hppa does not match the kernel value as the default value is
not used on this architecture. It needs its own version of bits/socket.h.

Patch will follow

--
           Summary: SOCK_NONBLOCK does not match the kernel value
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ports
        AssignedTo: carlos at systemhalted dot org
        ReportedBy: aurelien at aurel32 dot net
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: hppa-unknown-linux-gnu
  GCC host triplet: hppa-unknown-linux-gnu
GCC target triplet: hppa-unknown-linux-gnu


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug ports/10527] SOCK_NONBLOCK does not match the kernel value

by Bugzilla from sourceware-bugzilla@sourceware.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


------- Additional Comments From aurelien at aurel32 dot net  2009-08-16 13:26 -------
Created an attachment (id=4137)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=4137&action=view)
Patch to fix the problem


--


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug ports/10527] SOCK_NONBLOCK does not match the kernel value

by Bugzilla from sourceware-bugzilla@sourceware.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


------- Additional Comments From carlos at systemhalted dot org  2009-11-08 17:07 -------
I am looking into this.

--
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Keywords|                            |glibc_2.11
   Last reconfirmed|0000-00-00 00:00:00         |2009-11-08 17:07:18
               date|                            |


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug ports/10527] SOCK_NONBLOCK does not match the kernel value

by Bugzilla from sourceware-bugzilla@sourceware.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


------- Additional Comments From carlos at systemhalted dot org  2009-11-15 20:21 -------
Fixed by commit:
http://sources.redhat.com/git/gitweb.cgi?p=glibc-ports.git;a=commitdiff;h=926d329540c726f47a3793840d4a472c24c89c18

--
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug ports/10527] SOCK_NONBLOCK does not match the kernel value

by Bugzilla from sourceware-bugzilla@sourceware.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


------- Additional Comments From carlos at systemhalted dot org  2009-11-15 20:24 -------
Fixed in glibc_2.11.

--
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|glibc_2.11                  |


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.