Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 2/2] sngrep: fix error if gnutls and openssl are both enabled.
Date: Fri, 27 Jan 2017 20:32:11 +1300	[thread overview]
Message-ID: <20170127203211.071997cf@free-electrons.com> (raw)
In-Reply-To: <20170126213931.9987-2-aduskett@codeblue.com>

Hello,

On Thu, 26 Jan 2017 16:39:31 -0500, Adam Duskett wrote:
> With the changes applied by thomas I noticed that sngrep will now
> fail to configure if both openssl and gnutls are selected
> (both can't be enabled at the same time.)  I set openssl to take
> precidence over gnutls, mainly because it's the larger of the two
> dependencies, and if the user has selected it they probably want
> to use it.
> 
> Signed-off-by: Adam Duskett <aduskett@codeblue.com>

Applied, with the following changes:

    [Thomas:
     - regroup CONF_OPTS lines
     - add an 'else' clause to explicitly disable gnutls and openssl when
       none are available
     - add a reference to the autobuilder failure]

I've also made a separate commit to fix the libgcrypt issue, see:

  https://git.buildroot.org/buildroot/commit/?id=6205b75873cefe5376f49934f456729f5de6ee1f

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-01-27  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 21:39 [Buildroot] [V2 1/2] sngrep: fix dependency error Adam Duskett
2017-01-26 21:39 ` [Buildroot] [V2 2/2] sngrep: fix error if gnutls and openssl are both enabled Adam Duskett
2017-01-27  7:32   ` Thomas Petazzoni [this message]
2017-01-27  5:28 ` [Buildroot] [V2 1/2] sngrep: fix dependency error Thomas Petazzoni

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=20170127203211.071997cf@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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