From: Reuben Thomas <rrt@sc3d.org>
To: John Spencer <maillist-musl@barfooze.de>
Cc: musl@lists.openwall.com, Szabolcs Nagy <nsz@port70.net>
Subject: Re: printf POSIX compliance
Date: Fri, 8 Jun 2012 17:46:10 +0100 [thread overview]
Message-ID: <CAOnWdoivcwhGoEELHZN5Pasj0eZC+bzFJ2DBfT5cuUHXT0ZCDg@mail.gmail.com> (raw)
In-Reply-To: <4FD22C6C.5040704@barfooze.de>
On 8 June 2012 17:46, John Spencer <maillist-musl@barfooze.de> wrote:
>
> this is bogus, according to Rich:
> "all files are closed when a process terminates normally/calls exit.
> if you want to report write failures, just fflush(stdout) before exit and
> check the return value"
Jim Meyering has an analysis of the problem here:
http://www.gnu.org/ghm/2011/paris/#sec-2-1
> gnulib is simply a huge pile of junk...
Like the stdout problem, it's not that simple! gnulib has many
enthusiastic users, myself included, because it solves many
portability problems and adds much useful functionality. Thanks to
gnulib I was able to remove a total of about 1,000 lines of code from
GNU Zile. I have not heard a single complaint from users, so I guess
no-one tried to build it with musl. However, I have had success
stories from users building on far-out platforms like DOS, and I've
had far fewer bug reports on platforms I don't use since I started
using gnulib.
So, please file bug reports rather than insults! gnulib has receptive
and active maintainers, and we'll all benefit much more from fixed
software than from merely venting frustration.
As regards the particular problem with freadahead, looking at the code
suggests a workaround of -DSLOW_BUT_NO_HACKS to avoid trying to build
the FILE-fiddling code.
--
http://rrt.sc3d.org
next prev parent reply other threads:[~2012-06-08 16:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 10:34 Reuben Thomas
2012-06-08 12:19 ` Luca Barbato
2012-06-08 12:32 ` Reuben Thomas
2012-06-08 14:04 ` Szabolcs Nagy
2012-06-08 14:16 ` Rich Felker
2012-06-08 14:44 ` Rich Felker
2012-06-08 14:55 ` Rich Felker
2012-06-08 15:06 ` Szabolcs Nagy
2012-06-08 15:29 ` Rich Felker
2012-06-08 15:43 ` Reuben Thomas
2012-06-08 15:53 ` Rich Felker
2012-06-08 16:16 ` Reuben Thomas
2012-06-08 16:38 ` John Spencer
2012-06-08 16:37 ` Reuben Thomas
2012-06-09 7:43 ` John Spencer
2012-06-09 14:17 ` Reuben Thomas
2012-06-08 16:46 ` John Spencer
2012-06-08 16:46 ` Reuben Thomas [this message]
2012-06-08 16:51 ` Rich Felker
2012-06-08 16:58 ` Reuben Thomas
2012-06-08 17:00 ` Rich Felker
2012-06-08 17:07 ` Reuben Thomas
2012-06-08 23:25 ` Rich Felker
2012-06-09 2:33 ` Isaac Dunham
2012-06-09 2:45 ` Rich Felker
2012-06-09 12:58 ` Szabolcs Nagy
2012-06-09 14:17 ` Reuben Thomas
2012-06-09 21:11 ` Rich Felker
2012-06-09 21:24 ` Reuben Thomas
2012-06-09 14:15 ` Reuben Thomas
2012-06-11 9:37 Pedro Alves
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=CAOnWdoivcwhGoEELHZN5Pasj0eZC+bzFJ2DBfT5cuUHXT0ZCDg@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=maillist-musl@barfooze.de \
--cc=musl@lists.openwall.com \
--cc=nsz@port70.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).