Postgres Pro
Downloads
Home   >   mailing lists

Re: [COMMITTERS] pgsql: Disable _FORTIFY_SOURCE with ICC - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Disable _FORTIFY_SOURCE with ICC
Date
Msg-id 27946.1349408278@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Disable _FORTIFY_SOURCE with ICC  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Disable _FORTIFY_SOURCE with ICC  (Peter Geoghegan <peter@2ndquadrant.com>)
List pgsql-hackers
Tree view 
I wrote:
> I've seen this warning in recent Fedora builds, though not on my F16
> production box.  Some googling suggests the locution

> #if __OPTIMIZE__
> #define _FORTIFY_SOURCE 2
> #endif

> but I've not tested that.

A bit later: testing on an F17 box (glibc-2.15-56.fc17.x86_64)
confirms Peter G's complaint, and also confirms that putting
the above into port/linux.h (instead of the template file) fixes the
problem.  Don't know how to disable it on ICC, but I suppose there's
some way to test for ICC via an #if.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Disable _FORTIFY_SOURCE with ICC
Next
From: Amit Kapila
Date:
Subject: Re: Sharing more infrastructure between walsenders and regular backends (was Re: Switching timeline over streaming replication)