Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 8 Jun 2012 17:06:18 +0200
From: Szabolcs Nagy <>
Subject: Re: printf POSIX compliance

* Rich Felker <> [2012-06-08 10:55:19 -0400]:
> On Fri, Jun 08, 2012 at 10:44:23AM -0400, Rich Felker wrote:
> > Still working on finding whether this long double issue is what's
> > causign the gnulib junk to get pulled in...
> And it's not, at least not in the worst package, GNU m4. I #if'd out
> the broken long double test in configure, re-ran it, and even with no
> printf problems reported, freadahead is still getting pulled in...
> I'll see if I see anything else odd.

i've just checked m4 and it uses freadseek and closein

both functions are from gnulib and depend on freadahead

so m4 will use freadahead independently of the printf issue

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.