Ok finally I understand from where can come the trouble. We have a patch gdal-libproj.patch which was not updated to pick the new proj in App:Geo (and thus TW)

I've a test build available here https://build.opensuse.org/package/show/home:bruno_friedmann:branches: Application:Geo/gdal

@Robby would you mind to test it and confirm it fix the problem you have The rpm are available here https://build.opensuse.org/package/binaries/home:bruno_friedmann:branches: Application:Geo/gdal/openSUSE_Tumbleweed

@Martin shouldn't we remove this patch as it is hardcoded, and if we want one day to stop building gdal for all in App:Geo except for factory, we can have conflict like for Leap 15.0 libproj (4.9x) and libproj in App:Geo ? Or what would be our solution. As we certainly have the need to point the build to the right libproj, perhaps we should move this path to a dynamic version ? We might just not use libproj from project for building (this interesting

http://bugzilla.novell.com/show_bug.cgi?id=1102889 http://bugzilla.novell.com/show_bug.cgi?id=1102889#c7 --- Comment #7 from Martin Pluskal <mpluskal@suse.com> --- (In reply to Bruno Friedmann from comment #6) option is not known much, but its possible).

I mean something like PROJSOVER=$(ls -1 %_libdir/libproj.so.?? | awk -F '.' '{print $3}') sed -i "s,# define LIBNAME \"libproj.so\",# define LIBNAME \"libproj.so.${PROJSOVER}\",g" b/ogr/ogrct.cpp

So we should be safe, whatever the libproj used during the build ?

-- You are receiving this mail because: You are on the CC list for the bug.