From: Reuben Thomas <rrt@sc3d.org>
To: musl@lists.openwall.com
Subject: Re: printf POSIX compliance
Date: Fri, 8 Jun 2012 17:58:34 +0100 [thread overview]
Message-ID: <CAOnWdojyC95xaahoNPbJ38v0XrGdJtgrxTXXHGxNT+Mz9AwVig@mail.gmail.com> (raw)
In-Reply-To: <20120608165134.GT163@brightrain.aerifal.cx>
On 8 June 2012 17:51, Rich Felker <dalias@aerifal.cx> wrote:
>> 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.
>
> Someone building the package should not have to do this.
I agree. Again, I suspect that pointing out the problems you go on to
cite may influence change in gnulib. I suspect that, as you said
earlier, the maintainers of gnulib have been primarily concerned in
the past with porting to old, broken systems, not new ones which don't
so much need their help.
--
http://rrt.sc3d.org
next prev parent reply other threads:[~2012-06-08 16:58 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
2012-06-08 16:51 ` Rich Felker
2012-06-08 16:58 ` Reuben Thomas [this message]
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=CAOnWdojyC95xaahoNPbJ38v0XrGdJtgrxTXXHGxNT+Mz9AwVig@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=musl@lists.openwall.com \
/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).