All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Cavallari <Nicolas.Cavallari@green-communications.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python: disable _ssl.c build when --disable-ssl
Date: Fri, 13 Jan 2017 10:31:14 +0100	[thread overview]
Message-ID: <39092efc-7691-8091-8ae2-fb1e60e170e5@green-communications.fr> (raw)
In-Reply-To: <1484169742-28866-1-git-send-email-matthew.weber@rockwellcollins.com>

On 11/01/2017 22:22, Matt Weber wrote:
> From: Adam <adam.allison@rockwellcollins.com>
> 
> When --disable-ssl is provided as an option,
> prevent the building of _ssl.c.
> Without this change, some GCC toolchains fail
> to build the _ssl module depending on the
> build configuration
> (we observed 4.85 worked and 4.9.4).
> 
> Signed-off-by: Adam Allison <adam.allison@rockwellcollins.com>
> Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com>
> ---
>  package/python/111-optional-ssl.patch | 20 +++++++++++++++++++-
>  1 file changed, 19 insertions(+), 1 deletion(-)

I sent a patch doing the same thing, which was marked as superseeded
in patchwork: https://patchwork.ozlabs.org/patch/696139/

  reply	other threads:[~2017-01-13  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 21:22 [Buildroot] [PATCH 1/1] python: disable _ssl.c build when --disable-ssl Matt Weber
2017-01-13  9:31 ` Nicolas Cavallari [this message]
2017-03-09 23:04 ` Thomas Petazzoni
2017-03-10 18:15   ` Matthew Weber
     [not found]     ` <CAO1odpw8E=b2eTsVX8vCjhUF_vpg34WJvUxCKGCm+p0OSMsdkw@mail.gmail.com>
     [not found]       ` <CAO1odpzng87mcYwEFs72B9bRTdLgewtGscH1GsuEAyndOVuntw@mail.gmail.com>
     [not found]         ` <CAO1odpzB59BT3cgh3AVznLzcWz+nShYsok1GqEv_SV9N3wXbLA@mail.gmail.com>
2017-03-10 20:30           ` 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=39092efc-7691-8091-8ae2-fb1e60e170e5@green-communications.fr \
    --to=nicolas.cavallari@green-communications.fr \
    --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 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.