All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wget: use GnuTLS instead of OpenSSL
Date: Thu, 17 Jul 2014 12:44:35 +0100	[thread overview]
Message-ID: <53C7B723.6020301@communistcode.co.uk> (raw)
In-Reply-To: <53C7B5F1.1030302@communistcode.co.uk>

Wait, that config.log is bad. It's from my build with the patch
reverted. Hold up I'll get the proper one out.

On 17/07/14 12:39, Jack Mitchell wrote:
> config.log: http://ix.io/dr3
> 
> and yes, gnutls is being built, or at least it's in the work dir.
> 
> [jack@jackArch gnutls]$ pwd
> /home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/gnutls
> [jack@jackArch gnutls]$ ls
> 2.12.23-r8.4  3.2.13-r0  3.2.15-r0  3.3.5-r0
> [jack@jackArch gnutls]$
> 
> On 17/07/14 12:33, Richard Purdie wrote:
>> On Thu, 2014-07-17 at 12:06 +0100, Jack Mitchell wrote:
>>> So this error is still blocking my master build, any ideas?
>> Share the config.log so we can see how the configure test is failing? Is
>> gnutls actually built and in the sysroot or not?
>>
>> Cheers,
>>
>> Richard
>>
> 
> 


-- 
  Jack Mitchell (jack@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 


  reply	other threads:[~2014-07-17 11:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 10:52 [PATCH] wget: use GnuTLS instead of OpenSSL Ross Burton
2014-07-04  9:08 ` Jack Mitchell
2014-07-17 11:06   ` Jack Mitchell
2014-07-17 11:33     ` Richard Purdie
2014-07-17 11:39       ` Jack Mitchell
2014-07-17 11:44         ` Jack Mitchell [this message]
2014-07-17 11:46         ` Jack Mitchell
2014-07-17 12:39           ` Richard Purdie
2014-07-17 12:48             ` Richard Purdie
2014-07-25 16:40               ` Khem Raj
2014-07-25 16:59                 ` Richard Purdie
2014-07-25 10:42   ` Koen Kooi
2014-07-25 16:22 ` Khem Raj
2014-07-25 16:27   ` Burton, Ross

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=53C7B723.6020301@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.