[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOnWdoihoSttjvTJfR1sTR5xfSJbNGTY8GF4uDE+aBVWBBeXUA@mail.gmail.com>
Date: Fri, 8 Jun 2012 11:34:04 +0100
From: Reuben Thomas <rrt@...d.org>
To: musl@...ts.openwall.com
Subject: printf POSIX compliance
I notice that the musl FAQ says "the fundamentally broken freadahead
function in gnulib cannot be fixed by adding features to the C
library". I found this question because a user complained about my use
of gnulib in a package I maintain.
I contacted the gnulib maintainers, one of whom replied:
"IIRC, gnulib's freadahead use is caused by musl's printf not being
posix compliant, causing gnulib to pull in its printf replacement,
which doesn't work on musl."
It would be nice to sort this out: either musl's printf is not
POSIX-compliant, or gnulib's detection of POSIX-compliance is buggy.
Does any musl developer fancy looking at a gnulib-using package (e.g.
GNU grep, coreutils &c.) and finding out what gnulib thinks is wrong
with musl's printf? There are obvious benefits to sorting this out,
wherever the fault lies!
--
http://rrt.sc3d.org
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
