Hi Riccardo, Am 01.10.2015 um 19:56 schrieb Riccardo Mottola <[email protected]>: > Hi Dagobert (and hi to everybody else too), > > since gnutls is important, let's bite the 3.x series. > > I noticed you just commited some small tweaks. I have imported your BUILD64 > suggestion into this branch. > > Current status for me is on solaris 9: > serv.c: In function 'listen_socket': > serv.c:774:40: error: 'IPV6_V6ONLY' undeclared (first use in this function) > serv.c:774:40: note: each undeclared identifier is reported only once for > each function it appears in > > while solaris10 bails out just little later with: > > CXX ex-cxx.o > In file included from /usr/include/sys/time.h:421:0, > from ../../gl/sys/time.h:39, > from /usr/include/sys/select.h:23, > from ../../gl/sys/select.h:36, > from /usr/include/sys/types.h:629, > from ../../gl/sys/types.h:27, > from ../../gl/stdio.h:58, > from ../../gl/wchar.h:71, > from /opt/csw/include/c++/4.9.2/cwchar:44, > from /opt/csw/include/c++/4.9.2/bits/postypes.h:40, > from /opt/csw/include/c++/4.9.2/iosfwd:40, > from /opt/csw/include/c++/4.9.2/ios:38, > from /opt/csw/include/c++/4.9.2/ostream:38, > from /opt/csw/include/c++/4.9.2/iostream:39, > from ex-cxx.cpp:2: > ../../gl/stdio.h:1034:1: error: 'char* gets(char*)' conflicts with a previous > declaration > _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead"); > ^ > In file included from /usr/include/stdio.h:66:0, > from ../../gl/stdio.h:43, > from ../../gl/wchar.h:71, > from /opt/csw/include/c++/4.9.2/cwchar:44, > from /opt/csw/include/c++/4.9.2/bits/postypes.h:40, > from /opt/csw/include/c++/4.9.2/iosfwd:40, > from /opt/csw/include/c++/4.9.2/ios:38, > from /opt/csw/include/c++/4.9.2/ostream:38, > from /opt/csw/include/c++/4.9.2/iostream:39, > from ex-cxx.cpp:2: > /opt/csw/lib/gcc/sparc-sun-solaris2.10/4.9.2/include-fixed/iso/stdio_iso.h:242:14: > note: previous declaration 'char* std::gets(char*)' > extern char *gets(char *); > ^ > Makefile:1968: recipe for target 'ex-cxx.o' failed > > the receipe is for 3.1.24 > > The gnutls website states; > current stable: 3.3.18 > next stable (what does this mean, unstable?) 3.4.5 > > should we try out directly 3.3 or any reason to remain on 3.1 ? did things > get even worse solaris-wise for newer releases?
Just jump to the latest version, we can then see how the soname works out, GnuTLS 3 still ships with a .so.28 sonar AFAIK. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
smime.p7s
Description: S/MIME cryptographic signature
