public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/15124] New: No way to get correct strerror_r in programs needing newer Linux features, etc.
@ 2013-02-08 19:16 bugdal at aerifal dot cx
  2014-06-13 18:52 ` [Bug libc/15124] " fweimer at redhat dot com
  2015-08-27 22:14 ` [Bug string/15124] " jsm28 at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: bugdal at aerifal dot cx @ 2013-02-08 19:16 UTC (permalink / raw)
  To: glibc-bugs

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

             Bug #: 15124
           Summary: No way to get correct strerror_r in programs needing
                    newer Linux features, etc.
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: unassigned@sourceware.org
        ReportedBy: bugdal@aerifal.cx
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


Most of the Linux-specific features exposed by glibc that aren't covered by
another legacy profile (svr4, bsd, etc.) are only available if _GNU_SOURCE is
defined by the application. This includes mmap flags, clone and clone flags,
cpuset and affinity settings, fcntl flags/commands, etc.

The problem with this arrangement is that _GNU_SOURCE also breaks certain
standard interfaces (at least strerror_r, but there may be others). Thus, a
program that needs both the Linux-specific features and non-broken, conforming
strerror_r, has no recourse but to split up translation units such that all of
the extensions are accessed only from small translation units that don't need
interfaces that might be broken by defining _GNU_SOURCE. This is a really ugly
mess.

To resolve the issue, some method for indicating "want GNU extensions, but
prefer standards whenever there's a conflict" should be available. Ideally this
would be the behavior of defining both _GNU_SOURCE and _POSIX_C_SOURCE or
_XOPEN_SOURCE, but if the risk of breaking existing applications is too great,
another approach would be acceptable. What's not acceptable is the current
situation where there's no way to say "I want to add extensions" without also
saying "I want to break standard functions".

-- 
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.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libc/15124] No way to get correct strerror_r in programs needing newer Linux features, etc.
  2013-02-08 19:16 [Bug libc/15124] New: No way to get correct strerror_r in programs needing newer Linux features, etc bugdal at aerifal dot cx
@ 2014-06-13 18:52 ` fweimer at redhat dot com
  2015-08-27 22:14 ` [Bug string/15124] " jsm28 at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2014-06-13 18:52 UTC (permalink / raw)
  To: glibc-bugs

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug string/15124] No way to get correct strerror_r in programs needing newer Linux features, etc.
  2013-02-08 19:16 [Bug libc/15124] New: No way to get correct strerror_r in programs needing newer Linux features, etc bugdal at aerifal dot cx
  2014-06-13 18:52 ` [Bug libc/15124] " fweimer at redhat dot com
@ 2015-08-27 22:14 ` jsm28 at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: jsm28 at gcc dot gnu.org @ 2015-08-27 22:14 UTC (permalink / raw)
  To: glibc-bugs

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|libc                        |string

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-08-27 22:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-08 19:16 [Bug libc/15124] New: No way to get correct strerror_r in programs needing newer Linux features, etc bugdal at aerifal dot cx
2014-06-13 18:52 ` [Bug libc/15124] " fweimer at redhat dot com
2015-08-27 22:14 ` [Bug string/15124] " jsm28 at gcc dot gnu.org

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).