[darktable-dev] Re: latest darktable git & tarbal failed to build

2016-03-20 Thread wim vandenbussche
Roman Lebedev writes: > > On Sun, Mar 20, 2016 at 9:40 PM, wim vandenbussche > wrote: > >> especially libexif: > >> # cd /usr/local && find -name *libexif* -delete > >> > >> This looks very much like C++ ABI difference, i.e. darktable is being compiled >

Re: [darktable-dev] Re: latest darktable git & tarbal failed to build

2016-03-20 Thread Roman Lebedev
On Sun, Mar 20, 2016 at 9:40 PM, wim vandenbussche wrote: >> especially libexif: >> # cd /usr/local && find -name *libexif* -delete >> >> This looks very much like C++ ABI difference, i.e. darktable is being >> compiled >> with new C++11 ABI, while that libexif2 is

[darktable-dev] Re: latest darktable git & tarbal failed to build

2016-03-19 Thread wim vandenbussche
Pascal Obry writes: > > > A corrupt or a wrong libexiv2 being used? > > What is your distribution? > ubuntu 15.10 libexiv2-14 ___ darktable developer mailing list to unsubscribe send a mail to

[darktable-dev] Re: latest darktable git & tarbal failed to build

2016-03-19 Thread wim vandenbussche
Tobias Ellinghaus writes: > > Am Mittwoch, 16. März 2016, 17:10:19 schrieb wim vandenbussche: > > Tobias Ellinghaus ...> writes: > > > Am Montag, 14. März 2016, 16:28:33 schrieb wim vandenbussche: > > > > Darktable build script > > > > > > Please try deleting build/ and then running

Re: [darktable-dev] Re: latest darktable git & tarbal failed to build

2016-03-18 Thread Pascal Obry
Le jeudi 17 mars 2016 à 19:46 +, wim vandenbussche a écrit : > Linking C executable darktable > libdarktable.so: undefined reference to `Exiv2::XmpProperties:: > registerNs(std::string const&, std::string const&)' > libdarktable.so: undefined reference to `Exiv2::XmpParser::e >

[darktable-dev] Re: latest darktable git & tarbal failed to build

2016-03-15 Thread wim vandenbussche
Tobias Ellinghaus writes: > > Am Montag, 14. März 2016, 16:28:33 schrieb wim vandenbussche: > > Darktable build script > > Please try deleting build/ and then running build.sh again. > > [...] Hi Tobias, I removed it, I even tried by removing the