Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: pierluigi.passaro@phoenixsoftware.it
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: curl compilation broken on dizzy
Date: Mon, 24 Nov 2014 10:11:10 -0800	[thread overview]
Message-ID: <547374BE.9060308@gmail.com> (raw)
In-Reply-To: <54711D99.3090003@phoenixsoftware.it>


Pierluigi,

this should be fixed now.

please try again.

regards,
Armin

On 11/22/2014 03:34 PM, Pierluigi Passaro wrote:
> Hi all,
> I'm experiencing some problems compiling curl on dizzy.
> As far as I can see, the backporting of CVE-2014-3613 and CVE-2014-3620
> introduced patches few bytes smaller than those available on master
> branch: it looks like some CR characters are missing.
> The compilation on dizzy is ok using the patches from master branch.
>
> Could anyone sync the patches with those available on master branch?
>
> Thanks
> Regards
> Pierluigi


      parent reply	other threads:[~2014-11-24 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 23:34 curl compilation broken on dizzy Pierluigi Passaro
2014-11-23  1:58 ` akuster808
2014-11-24 18:11 ` akuster808 [this message]

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=547374BE.9060308@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=pierluigi.passaro@phoenixsoftware.it \
    /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