From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] BUG: no https support with midori
Date: Thu, 11 Aug 2011 09:17:20 +0200 [thread overview]
Message-ID: <1313047041.16546.2.camel@sven> (raw)
In-Reply-To: <20110810233055.596f53cb@gmail.com>
Hi,
On Wed, 2011-08-10 at 23:30 +0200, Frederic Bassaler wrote:
> Sorry I forgot to tell, but I did remove the --disable-ssl configuration
> directive in libsoup.mk
>
> As shown below, configure fails to find the libgcrypt library...
>
> Does it work for you? (Maybe I have to delete my output directory and
> rebuild again from scratch)
It works for me. But I've just checked and it appears that we have the
following in libsoup.mk:
ifeq ($(BR2_PACKAGE_GNUTLS),y)
LIBSOUP_DEPENDENCIES += gnutls
LIBSOUP_CONF_OPT += --enable-ssl \
--with-libgcrypt-prefix=$(STAGING_DIR)/usr
else
LIBSOUP_CONF_OPT += --disable-ssl
endif
You might also try "--without-libgcrypt-prefix". I heard rumours that
this would work as well.
Sven
next prev parent reply other threads:[~2011-08-11 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 17:25 [Buildroot] BUG: no https support with midori Frederic Bassaler
2011-08-10 19:33 ` Sven Neumann
2011-08-10 21:30 ` Frederic Bassaler
2011-08-11 7:17 ` Sven Neumann [this message]
2011-08-11 9:36 ` Frederic Bassaler
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=1313047041.16546.2.camel@sven \
--to=s.neumann@raumfeld.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