Date: Fri, 25 May 2012 22:49:36 +0200 From: Rainer Hurling <rhurlin@gwdg.de> To: "coder.tuxfamily" <coder@tuxfamily.org> Cc: sunpoet@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: gdal 1.9.1 (Was Re: graphics/gdal 1.9.0 does not build on CURRENT) Message-ID: <4FBFF060.9070706@gwdg.de> In-Reply-To: <4FBFE2B8.5000601@tuxfamily.org> References: <4FBA9620.3020207@gwdg.de> <4FBA997C.6010000@tuxfamily.org> <4FBAA203.90201@gwdg.de> <4FBAA388.1070906@tuxfamily.org> <4FBB24D3.4010209@gwdg.de> <4FBBC3F2.4050104@tuxfamily.org> <4FBBC504.5010305@gwdg.de> <4FBBD7B4.5090505@tuxfamily.org> <4FBBFADA.6010700@gwdg.de> <4FBD0797.9040803@gwdg.de> <4FBD0EE2.9050703@tuxfamily.org> <4FBD122E.9030606@gwdg.de> <4FBF4303.8020501@gwdg.de> <4FBFE2B8.5000601@tuxfamily.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25.05.2012 21:51 (UTC+1), coder.tuxfamily wrote:
> Can you try to build the "new" port of gdal ?
>
> I have the same problem with swig for php...
Thanks for the update. It builds and installs fine here on two boxes
with 10.0-CURRENT (amd64).
One issue which should be thought about before updating gdal in the ports:
Does gdal-1.9.1 really needs swig 2.0? It seems so for at least libkml?
The problem is, that in your Makefile swig 2.0 conflicts with an
installed swig 1.3.40, which is needed for example by graphics/geos,
graphics/graphviz, math/saga, science/py-scipy and some others.
Affected ports can be found for example with
find /usr/ports -name Makefile -depth 3 -exec grep -l -e "swig13" {} \;
I personally would prefer the newer swig 2.0 version (even for most
other ports). Do you think it is necessary to forbid a parallel swig
1.3.40 installation in your port? I read somewhere that both swig ports
can coexist in principle, only some docs share the same places (which
should be changed, of course).
> Le 25.05.2012 10:29, Rainer Hurling a écrit :
>> On 23.05.2012 18:37 (UTC+1), Rainer Hurling wrote:
>>> On 23.05.2012 18:22 (UTC+1), coder.tuxfamily wrote:
>>>>
>>>>> OK, I think I get it. This failure does not happen, if swig is not
>>>>> installed. Then it builds and installs fine.
>>
>> I tried to install gdal-1.9.0 on another 10.0-CURRENT box and it fails
>> completely. On that box I was not able to build gdal even without swig
>> or with swig 2.0 installed.
>>
>> After that I tried on a 10.0-CURRENT Tinderbox with a totally unmodified
>> gdal-1.9.0 (even without the ${CPPFLAGS} patch). It builds just fine, no
>> problems at all!
>>
>> So it must have to do with some special configurations and/or installed
>> packages.
>>
>> The only clue I have at this time is, that
>> extensions/gdal_wrap.cpp:6845: complains about "'VSIFTruncateL', which
>> was not declared in this scope".
>>
>>
>>>>> Do you have any idea what is going wrong with swig here?
>>>>
>>>>
>>>> OK. Maybe inclue the swig dependancy into the Makefile.
>>>
>>> I just tested three cases:
>>>
>>> (1) No swig installed -> gdal 1.9.0 builds and installs fine
>>>
>>> (2) swig 1.3.40 installed -> the build breaks, see older mails
>>>
>>> (3) swig 2.0.4 installed -> gdal 1.9.0 builds and installs fine
>>>
>>>
>>> So we only have to take care that swig 1.3.40 is not installed.
>>>
>>>
>>> With swig installed, the pkg-plist of gdal is incomplete, 'make
>>> deinstall' shows
>>>
>>> pkg_delete: unable to completely remove directory
>>> '/usr/local/share/gdal'
>>> pkg_delete: unable to completely remove directory
>>> '/usr/local/lib/python2.7/site-packages/GDAL-1.9.0-py2.7-freebsd-10.0-CURRENT-amd64.egg/osgeo'
>>>
>>>
>>>
>>> pkg_delete: unable to completely remove directory
>>> '/usr/local/lib/python2.7/site-packages/GDAL-1.9.0-py2.7-freebsd-10.0-CURRENT-amd64.egg'
>>>
>>>
>>>
>>> pkg_delete: couldn't entirely delete package `gdal-1.9.0'
>>> (perhaps the packing list is incorrectly specified?)
>>>
>>>
>>>> I try to port gdal 1.9.1
>>>
>>> That would be nice!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FBFF060.9070706>