search

viking-gps / viking

Viking is a free/open source program to manage GPS data (inc GPX, FIT, TCX and KML files). You can import and plot tracks, routes and waypoints, show OpenStreetMaps (OSM), Bing Aerial and other maps, generate Mapnik maps, geotag images, make new tracks, routes and waypoints, see real-time GPS position, etc. It is written mostly in C with GTK
http://sourceforge.net/projects/viking/
GNU General Public License v2.0
230 stars 56 forks source link

viking v1.10 build fails with an error #297

Open svetlemodry opened 2 months ago

svetlemodry commented 2 months ago

Hi! I am attempting to build the viking 1.10 package on Arch Linux and the build is failing for me with an error. For the build I am using the current PKGBUILD And here is the output of the build run. I've tried to search the current issues on github, but did not find anything relevant, hence this report. I'd be glad for any hints on how to get this sorted out. Cheers! Jaro

rnorris commented 2 months ago

It appears to be failing on compiling: /usr/include/unicode/stringpiece.h

Which comes from libicu-dev package or similar - so what version of libicu is on your system?

See https://icu.unicode.org/ ; so if ICU 75, then needs C++17 - whereas the build for Viking in v1.10 says C++11.

This is co-incidentally solved by https://sourceforge.net/p/viking/bugs/170/

The easiest way to work around it in v1.10, should be by disabling the Mapnik component (but obviously then any usage of the related features won't be available).

./configure --disable-mapnik

svetlemodry commented 2 months ago

It appears to be failing on compiling: /usr/include/unicode/stringpiece.h

Thanks for checking this!

Which comes from libicu-dev package or similar - so what version of libicu is on your system?

We have icu 75.1-1 in the repository.

See https://icu.unicode.org/ ; so if ICU 75, then needs C++17 - whereas the build for Viking in v1.10 says C++11. This is co-incidentally solved by https://sourceforge.net/p/viking/bugs/170/

Quick try to cherry pick that patch seemed not to fix the build for me.

The easiest way to work around it in v1.10, should be by disabling the Mapnik component (but obviously then any usage of the related features won't be available). ./configure --disable-mapnik

I went with disabling mapnik for now, package builds again. Will wait for the new release to enable mapnik again. Cheers & thanks! J