Re: BUG #5318: Inconsistent PHP pg_result_error_field PGSQL_DIAG_SOURCE_FUNCTION across instalations - Mailing list pgsql-bugs

From Zdenek Kotala
Subject Re: BUG #5318: Inconsistent PHP pg_result_error_field PGSQL_DIAG_SOURCE_FUNCTION across instalations
Date
Msg-id 1265572644.3942.12.camel@localhost
Whole thread Raw
In response to Re: BUG #5318: Inconsistent PHP pg_result_error_field PGSQL_DIAG_SOURCE_FUNCTION across instalations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5318: Inconsistent PHP pg_result_error_field PGSQL_DIAG_SOURCE_FUNCTION across instalations  ("IP" <ireneusz.pastusiak@poczta.fm>)
List pgsql-bugs
Tom Lane píše v so 06. 02. 2010 v 10:57 -0500:
> "IP" <ireneusz.pastusiak@poczta.fm> writes:
> > Issue: no value returned for 8.4.2 Solaris 10 x86 installation
>
> This isn't necessarily a bug.  The source-function report depends
> on having used a C compiler that supports the __func__ or __FUNCTION__
> symbol, and not all do.

Yes it is the problem

> Most likely your Solaris 10 version was
> built with a compiler that doesn't.

SunStudio has __func__ since version 10. Solaris 10 is compiled with
version 11. Problem is that __func__ is defined in C99 and PostgreSQL is
compiled with -xc99=none. Which means that compiler should be strict C89
like PostgreSQL ;-).

I think that there is no reason to use this flag.

    Zdenek

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: Possible stability issue: permanent hang on dropdb
Next
From: John R Pierce
Date:
Subject: Re: [GENERAL] weird bug in rebuilding RPMs