Monday, 16 May 2016

[gccsdk] GnuTLS/autobuilder/4.7.4 and other findings

I only have a limited internet via cell phone networking, and have been using !SMTPS and !POP3S to access gmail and yahoo accounts.
The TLS for gmail failed to work some time ago, but I have found building a newer libgnutls(from Jessie) and rebuilding !POP3S as worked, and as long as you are reading this, !SMTPS is now working also.

A quick tip here for a simple way to avoid the repeating of downloading the debian archives when the autobuilder fails.
I can recall there being another way, But by putting the downloaded archive in the root directory of my Iyonix, running !Ftps and using
AB_URL=ftp://<iyonix ip>/archive name
in setvars and the problem is solved without changing settings in the autobuilder globally.

I think I've found that if libtasn1 have not been built, gnutls will use it's internal version and there is no need to link to libtasn1 or libintl when compiling SMTPS/POP3S also.
libcrypt is no longer needed with this version either.
So for depends I only had libnettle and libgmp.
It could depend on libgnutls end use, the full external libs version is probably better.

To get a pic free libgnutls.a I had to specify --disable-shared
The result was I still got the shared libraries and then the archive passed the Libtool check.
The latest gnutls30 setvars uses --with-pic=no , sounds better.
--with-libnettle-prefix=$GCCSDK_INSTALL_ENV
was getting ignored so I deleted that

As libtool installs libraries it checks them, and it found that libgnutls.a had pic left in, causing an error. It is worth noting that ro-make install on its own would miss this check.

Note that building libgnutls with the 4.7.4 crosscompiler means that the compiling of SMTPS/POP3S has to be done with GCC 4.7.4 (or the crosscompiler I guess) as there is lack of support for flockfile and funlockfile in the earlier versions. I dont know what would have happened if I had used the 4.1.2 setup, but where there is encryption involved the later compiler may give the option for a boost for some hardware.

Ron M.












_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

No comments:

Post a Comment