On 2016-10-13 15:56 +0200, Bas Couwenberg wrote:
> On 2016-10-13 15:52, Bas Couwenberg wrote:
> >On 2016-10-13 15:48, Wookey wrote:
> >>
> >>OK. Yep, just rebuilding gdal (and installing the resulting
> >>libgdal-dev, libgdal20), fixes the postgis configure.
>
> Can you schedule a dep-wait for lib
On 10/13/2016 04:37 PM, Wookey wrote:
> On 2016-10-13 15:56 +0200, Bas Couwenberg wrote:
OK. Yep, just rebuilding gdal (and installing the resulting
libgdal-dev, libgdal20), fixes the postgis configure.
I'll schedule a binNMU.
>>>
>>> Thanks for the confirmation. A binNMU won't
On 2016-10-13 15:52, Bas Couwenberg wrote:
On 2016-10-13 15:48, Wookey wrote:
On 2016-10-12 18:57 +0100, Wookey wrote:
On 2016-10-11 08:16 +0200, Sebastiaan Couwenberg wrote:
> > Seems to me that the issue is probably actually in gdal, rather
> > than postgis, although why the configure behavi
On 2016-10-13 15:48, Wookey wrote:
On 2016-10-12 18:57 +0100, Wookey wrote:
On 2016-10-11 08:16 +0200, Sebastiaan Couwenberg wrote:
> > Seems to me that the issue is probably actually in gdal, rather
> > than postgis, although why the configure behaviour has changd
> > remains a mystery.
>
> Th
On 2016-10-12 18:57 +0100, Wookey wrote:
> On 2016-10-11 08:16 +0200, Sebastiaan Couwenberg wrote:
>
> > > Seems to me that the issue is probably actually in gdal, rather
> > > than postgis, although why the configure behaviour has changd
> > > remains a mystery.
> >
> > The configure behaviour i
On 12/10/16 18:57, Wookey wrote:
That seems quite likely. It might just be the senstivity of C++
symbols to compiler changes. Unfortunately so far as I know one can't
test such a thing on the porter boxes (because there is no way to
unstall the local gdal you just built due to lack of root rights
On 2016-10-11 08:16 +0200, Sebastiaan Couwenberg wrote:
> > Seems to me that the issue is probably actually in gdal, rather
> > than postgis, although why the configure behaviour has changd
> > remains a mystery.
>
> The configure behaviour is weird indeed. On the other architectures
> "none requ
Hi Wookey,
Thanks for looking into this issue.
On 10/11/2016 05:46 AM, Wookey wrote:
> On 2016-10-10 21:50 +0200, Sebastiaan Couwenberg wrote:
>> Dear arm64 porters,
>>
>> The postgis (2.3.0+dfsg-3) upload is failing to build to arm64 because
>> its configure check for GDAL failed, specifically:
On 2016-10-10 21:50 +0200, Sebastiaan Couwenberg wrote:
> Dear arm64 porters,
>
> The postgis (2.3.0+dfsg-3) upload is failing to build to arm64 because
> its configure check for GDAL failed, specifically:
>
> AC_SEARCH_LIBS([GDALAllRegister], [gdal], [], [AC_MSG_ERROR([could not
> find GDAL])], [
Dear arm64 porters,
The postgis (2.3.0+dfsg-3) upload is failing to build to arm64 because
its configure check for GDAL failed, specifically:
AC_SEARCH_LIBS([GDALAllRegister], [gdal], [], [AC_MSG_ERROR([could not
find GDAL])], [])
I can reproduce this issue on the the arm64 porterbox, where I a
10 matches
Mail list logo