public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16355] syslog.h's SYSLOG_NAMES namespace violation and utter mess
Date: Fri, 20 Dec 2013 23:04:00 -0000	[thread overview]
Message-ID: <bug-16355-131-h0WFYOuRO6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16355-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> ---
Andreas, what? Your comment makes no sense. First you say it's defined by an
application (FreeBSD syslogd, which probably is not the one used on most
glibc-based systems...) to get these definitions, and then you say it's safe to
remove (it's not; it would break the application).

At the very least, several syslogd implementations, including Busybox syslogd,
define SYSLOG_NAMES to get these definitions. So just removing them would need
to be coordinated with programs using them. It's _probably_ safe to just move
the whole mess under __USE_MISC though to fix the conformance issue.

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


  parent reply	other threads:[~2013-12-20 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 18:18 [Bug libc/16355] New: " bugdal at aerifal dot cx
2013-12-20 22:46 ` [Bug libc/16355] " schwab@linux-m68k.org
2013-12-20 23:04 ` bugdal at aerifal dot cx [this message]
2013-12-20 23:56 ` schwab@linux-m68k.org
2014-06-13 11:23 ` fweimer at redhat dot com
2022-04-15 21:13 ` adhemerval.zanella at linaro dot org

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-16355-131-h0WFYOuRO6@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).