[postgis-devel] pgxs cflags override

Paul Ramsey pramsey at cleverelephant.ca
Tue Oct 17 13:39:15 PDT 2017


Thanks, I have committed a hack sufficient for my purposes, but
unfortunately still leaving the original hack in place. The build sure has
a smell on it.
P.

On Tue, Oct 17, 2017 at 1:07 PM, Regina Obe <lr at pcorp.us> wrote:

> Looks like it got changed by  Greg's patch
>
>
>
> https://trac.osgeo.org/postgis/changeset/15051
>
>
>
>
>
>
>
> *From:* postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] *On
> Behalf Of *Paul Ramsey
> *Sent:* Tuesday, October 17, 2017 3:46 PM
> *To:* PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> *Subject:* [postgis-devel] pgxs cflags override
>
>
>
> So, I found today I couldn't debug into a portion of postgis, because it
> was building w/o debugging flags. Which was odd, since I force -g into
> everything at configure time, and use --debug everywhere.
>
>
>
> The cflags in ./postgis are supposed to get inherited from pg_config of
> the pgsql one is building againt, but I found an over-ride on them.
>
>
>
> The attached patch fixes the problem, for me, (moving the include into the
> "correct" pgxs variable and leaving the cflags un-overridden) but it's one
> of those deep voodoo build things that makes we want to know: does anyone
> remember why this is the way it is?
>
>
> P
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20171017/eeeff7ad/attachment.html>


More information about the postgis-devel mailing list