Re: Warnings from fwrite() in git head

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Warnings from fwrite() in git head
Date: 2012-10-11 02:17:10
Message-ID: 20121011021710.GJ11890@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 8, 2012 at 12:12:54PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I am seeing the following warnings in git head from zic.c:
> > zic.c:1505: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
>
> Yeah, this is probably a consequence of the _FORTIFY_SOURCE addition.
> I believe that ratchets up warning pickiness as well as other things.
>
> I'm inclined to think we should make zic.c bail out on write errors.
> Otherwise, "make install" could fail to notice an out-of-disk-space
> situation during install. The analogy you are drawing to ignoring
> errors while writing log messages is quite faulty.
>
> We're overdue for another round of syncing the tz code with upstream,
> too. Might be best to do that first, just in case Olson's crew already
> fixed this.

My warnings have disappeared now that _FORTIFY_SOURCE has been removed
on Linux.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2012-10-11 02:21:10 Re: [PATCH 8/8] Introduce wal decoding via catalog timetravel
Previous Message Greg Stark 2012-10-11 02:16:39 Re: [PATCH 8/8] Introduce wal decoding via catalog timetravel