Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKNyY-0000RY-38 for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Mar 2021 16:15:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lKNyW-0006Bt-TE for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Mar 2021 16:15:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKNyW-0006Bm-ID for pgsql-bugs@lists.postgresql.org; Thu, 11 Mar 2021 16:15:48 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lKNyP-00078j-KT for pgsql-bugs@lists.postgresql.org; Thu, 11 Mar 2021 16:15:47 +0000 Received: by mail-wm1-x329.google.com with SMTP id r10-20020a05600c35cab029010c946c95easo13147749wmq.4 for ; Thu, 11 Mar 2021 08:15:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pcorp-us.20150623.gappssmtp.com; s=20150623; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=DaeT0tZuAgH1vDUgvJqXnoJNj4m0J/56kyJRg2xGkIs=; b=T3nCRExhtZD9ZmnjM+M/7y6XHsR1Gpm3nOr+R9+H6UkAGrewaL26KlKR/BSpu9vswr RjweHEmXIBCBmBt0U5L5tLNHbshnMNYJdjQU3KZjtCNru3o6pV/9A1aSvFfAIurRKYFn HjEB8yhC0jC5I46WTtoT9IVTbJt4afz3Fa53wa4aWPca5Bc5huVaHrOQD/2YNBclpwA4 Z1Am2/o2maiLkGdWXL9sRBO5EvP+AQI4ibW9YPUOV5RVk4+0CNAjHDuh58+71s6WTyYY v6XEKlUYFCu9Ew758cdDe0zKfVn2N1qgFYg6pGwAteLfYULl67DUwz1UnLzbI8Yj36qH Arag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=DaeT0tZuAgH1vDUgvJqXnoJNj4m0J/56kyJRg2xGkIs=; b=FePibpVCX/EIp2VKIY9UEWvN3O8x5O3CYSX2q94iFPpmoicSTn5koeFoErOSjk7wn4 6ielX68hGApGnH42zkZrHPL6c/vbjdGgcZ/nboBfm50C+hO+o5+KC22irw14393gWFpu gS2AzuSW48CvLezy9uMMsA0OktdCrTKhEMKDVc8UI7mCL+gsgYeqK5KP3CHDMPFRod4k 5/rUia8ACwWiBPP/iRbE/19GLCr3lHQUDb9YS+0ZiMpgxVt5CMnKC14Jy5+UsuWWLl6j FVfEN1Zs8FczjIwdZkIQ5Hg+zcK4z6v6iE5vWWiyoLqcpnvQQV8juUxnqROSivRIFR3P 3zLw== X-Gm-Message-State: AOAM533zxdCOq1dhneJeFQYebDUPF0lqgnOJl8wVlX2RGEQDc4LsjJJL jwaDDj7/ftD5pEiBEBQKF4B8KIq+VBlRuw== X-Google-Smtp-Source: ABdhPJzkinnJ6PU5ZrPfkTEPFH3AmIhaPp9tJL2Datk+zat3M1ywFZKJibU/brccHAWSuPN8aEMhGg== X-Received: by 2002:a7b:ce19:: with SMTP id m25mr9021811wmc.74.1615479339091; Thu, 11 Mar 2021 08:15:39 -0800 (PST) Received: from F (50-78-240-110-static.hfc.comcastbusiness.net. [50.78.240.110]) by smtp.gmail.com with ESMTPSA id r11sm4389795wrx.37.2021.03.11.08.15.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Mar 2021 08:15:38 -0800 (PST) From: "Regina Obe" To: "'Tom Lane'" Cc: References: <16920-2332590daf58407c@postgresql.org> <2291040.1615474929@sss.pgh.pa.us> In-Reply-To: <2291040.1615474929@sss.pgh.pa.us> Subject: RE: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head Date: Thu, 11 Mar 2021 11:15:36 -0500 Message-ID: <000501d71691$c616a200$5243e600$@pcorp.us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHCjUPo5BIH9fF+WOyrxdMuyoS6VgH0iV+7qphi+8A= Content-Language: en-us List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: Thursday, March 11, 2021 10:02 AM > To: r@pcorp.us > Cc: pgsql-bugs@lists.postgresql.org > Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against > PostgreSQL 14 head > > PG Bug reporting form writes: > > I pulled PostgreSQL 14 earlier today to troubleshoot an issue we were > > having and discovered I can not compile PostGIS with Mingw64 against > > PostgreSQL 14 head. > > Hmm, our mingw64 buildfarm animals aren't detecting any particular > problem here. Is PostGIS doing anything unusual with injecting special > symbols via -D switches? Or maybe including something else before > postgres.h? The symptoms look like a header-inclusion-order problem ... > > regards, tom lane The order in one of the problem files looks like this: Starting: https://git.osgeo.org/gitea/postgis/postgis/src/branch/master/postgis/lwgeom _in_gml.c#L50 #include #include #include #include #include "postgres.h" #include "executor/spi.h" #include "utils/builtins.h" #include "../postgis_config.h" #include "lwgeom_pg.h" #include "liblwgeom.h" #include "lwgeom_transform.h" Note I didn't have issue compiling PostgreSQL under mingw64 (no change) - I need to double-check the output, but I think all tests passed. What extensions does the buildfarm animals test? Thanks, Regina