Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 May 2012 08:59:38 +0200
From:      "coder.tuxfamily" <coder@tuxfamily.org>
To:        Rainer Hurling <rhurlin@gwdg.de>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: gdal 1.9.1 (Was Re: graphics/gdal 1.9.0 does not build on CURRENT)
Message-ID:  <4FC3225A.2060306@tuxfamily.org>
In-Reply-To: <4FC1D51C.6000404@gwdg.de>
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> <4FBFF060.9070706@gwdg.de> <4FC0FB76.2070702@tuxfamily.org> <4FC107D7.5060905@gwdg.de> <4FC1D51C.6000404@gwdg.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Le 27.05.2012 09:17, Rainer Hurling a écrit :
> On 26.05.2012 18:41 (UTC+1), Rainer Hurling wrote:
>> On 26.05.2012 17:49 (UTC+2), coder.tuxfamily wrote:
>>> Le 25.05.2012 22:49, Rainer Hurling a écrit :
>>>> 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).
>>>>
>>>
>>> Maybe you're right. I've see on trac.osgeo.org that it uses swig-1.3.40.
>>> I will try without specify version of swig.
>>
>> I saw in the news on http://www.swig.org/, that swig 2.0.6 is out with
>> many bug fixes and enhancements for templates and target languages like
>> php and python. Perhaps swig 2.0.6 is ready now for gdal?
>
> I made a patch to update from swig 2.0.4 to 2.0.6. Could you please try
> if at least some of the observed problems will disappear?
>
> If this helps we should create a PR and ask the maintainer for an update.
>
>> I just checked, that swig 1.3.40 and 2.0.4 should be able to coexist at
>> the same time. At least they do not share any filenames.
>

The patch works but don't solve gdal problems. I think i've found were 
it's wrong.

For Ruby/Swig :
See the page on GDAL : http://trac.osgeo.org/gdal/wiki/GdalOgrInRuby
SWIG 2 is required to build the Ruby bindings against Ruby 1.9.2. (SWIG 
1.3.40 is fine for Ruby 1.8.7)

When i try to compile, i've two errors :

"ogr_wrap.o: relocation R_X86_64_32 against `a local symbol' can not be 
used when making a shared object; recompile with -fPIC
ogr_wrap.o: relocation R_X86_64_32 against `a local symbol' can not be 
used when making a shared object; recompile with -fPIC"







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FC3225A.2060306>