Re: [gccsdk] GCC and GNUTLS - compiling problems

In message <65f121f653.Alex@bavariasound.chiemgau-net.de>
Alexander Ausserstorfer <bavariasound@chiemgau-net.de> wrote:

> In message <c1b197f353.Jo@hobbes.bass-software.com>
> John Tytgat <John.Tytgat@aaug.net> wrote:
>
> > You probably need to throw in more libraries on which libgnutls.a is
> > depending on. Didn't the LibGNUTLS package come with more than one
> > library ? If so, you might need to specify more -l options for each of
> > those. Library order is important, the search for unresolved symbols
> > happens according to the library order you're specifying.
>
> The LibGUTLS package comes with just one library but GNUTLS depends / is
> based on Nettle and p11-kit. On Unix, this doesn't matter, just using
> -lgnutls is fine enough and working. Are there any differents between
> Unix and RISC OS belonging the GCC?

I guess on Unix you're using shared libraries as they are present and
by default have precedence over the static libraries installed.
For the shared library case, as long as its depending libraries are
installed as well, you as libgnutls user should not be worried about them.
The symbol resolving happens at runtime instead of link time.

The moment you specify -static at link time (explicitly requesting to use
static libraries) you will have to list all the static libraries needed by
libgnutls and its depending libraries.

On RISC OS it is exactly the same. Only because you don't have the
shared library libgnutls (and all its depending shared libraries) installed,
you automatically fall in the static library case.

John.
--
John Tytgat, in his comfy chair at home
John.Tytgat@aaug.net

_______________________________________________
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