From: Bernhard Schuster <schuster.bernhard@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] glib-networking when using gtlsconnection fails
Date: Wed, 16 Oct 2013 15:50:51 +0002 [thread overview]
Message-ID: <525eb564.c664cc0a.66a5.6cee@mx.google.com> (raw)
Hi,
I am trying to cross compile a application which works just fine on my
x86_64 machine for a ARMv5TE "gadget". Unfortunately something really
weird happens: Altough having selected gnutls in order to use TLS with
glib-networking (GTlsConnection), I always get an error as soon as the
combined cert/key pem file is read (it exists, has proper permissions,
all tripple checked). The error always contains "TLS unsupported" or
"no TLS support" (can not recall, currently away from that machine)
altough the config.h of glib-networking says the opposite. The binary
is statically compiled (which worked fine so far).
I am puzzled on how to fix my issue, I already tried to fix it by
adding a couple of commandline opts explicitly (though they say that
they are enabled by default, thus - as expected - nothing changed).
Also note that I have a similar issue with pcre (required for GRegex),
where I pass --enable-utf8 but it still did not fix anything.
Any help, hint, tip is appreciated.
Buildroot 2013.08 is used together with the code sourcery 2011/2013
toolchain
Best
Bernhard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131016/f53289b7/attachment.html>
next reply other threads:[~2013-10-16 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 15:48 Bernhard Schuster [this message]
2013-10-16 15:56 ` [Buildroot] glib-networking when using gtlsconnection fails Thomas Petazzoni
2013-10-17 19:48 ` Bernhard Schuster
2013-10-22 14:38 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2013-10-16 22:43 Bernhard Schuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525eb564.c664cc0a.66a5.6cee@mx.google.com \
--to=schuster.bernhard@googlemail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox