Francesco wrote:
> Hamish
> I tried to update opencpn to the current upstream version,
> but got an error:
> /usr/bin/c++   -D_FILE_OFFSET_BITS=64
> -DUSE_GARMINHOST -g -O2  -pthread -isystem
> /usr/lib/wx/include/gtk2-unicode-release-2.8 -isystem
> /usr/include/wx-2.8 -I/tmp/buildd/opencpn-2.4.606/include
> -I/tmp/buildd/opencpn-2.4.606/src -I/usr/include/gtk-2.0
> -I/usr/include/freetype2 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0
> -I/usr/lib/gtk-2.0/include -I/usr/include/cairo
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0
> -I/tmp/buildd/opencpn-2.4.606/src/nmea0183
> -I/tmp/buildd/opencpn-2.4.606/src/mygdal
> -I/tmp/buildd/opencpn-2.4.606/src/garmin/jeeps   -Wall
> -g -fexceptions -rdynamic -O3 -fno-strict-aliasing -o
> CMakeFiles/S57ENC.dir/src/s52plib.cpp.o -c
> /tmp/buildd/opencpn-2.4.606/src/s52plib.cpp
> /tmp/buildd/opencpn-2.4.606/src/s52plib.cpp: Assembler
> messages:
> /tmp/buildd/opencpn-2.4.606/src/s52plib.cpp:5550: Error:
> symbol `l0' is already defined
> /tmp/buildd/opencpn-2.4.606/src/s52plib.cpp:5555: Error:
> symbol `l1' is already defined
> /tmp/buildd/opencpn-2.4.606/src/s52plib.cpp:5562: Error:
> symbol `l2' is already defined
> make[3]: *** [CMakeFiles/S57ENC.dir/src/s52plib.cpp.o]
> Error 1


I've just built it (the new 2.4.612) ok in a sid amd64 VM, could
you try again?  Dave wrote about it:


Check out my ugly code

This is a hack to inline an assembly code version of memset3.
It is conditional on __WXGTK__ and __INTEL__.

I did this long ago after looking at the instructions generated by gcc3. Made 
me cringe....

Maybe it breaks with 64? Is this optimization used on your build?


(fwiw I'm building using a amd phenom chip)

> so please load your version on the svn repository under
> tarballs/ branch to at least try building the previous version.

> I noted the upstream tree is full of binaries which require
> apparently a nearby licensing analysis....

yes, PaulW picked that up too. The main problematic one I see is
the MS VC++ runtime redistributable. I looked on their download
page but no terms, I guess you have to look at the click-through
upon install. I suspect the terms are similar to Java's JAI array
support redistributable.

I do not disagree that the other binaries shouldn't be in the
code repo, but AFAIR Nullsoft made the installer binary and that
is all gpl-compatible, and the other is produced by the project

no useful action on that yet AFAIK.

re tarballs:
how to "svn export" from the upstream git repo to make the .orig
tarball for Alioth? Can it be done automatically? Can it be set
to --exclude= (in the rsync sense) the buildwin/ and buildosx/
dirs from the upstream git repo automatically?

or should I just do all that by hand?


Pkg-grass-devel mailing list

Reply via email to