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] [PATCH 2/2] host-python: disable building ossaudiodev module
Date: Thu, 8 Jan 2015 13:49:43 +0100	[thread overview]
Message-ID: <20150108134943.7afbaeb7@free-electrons.com> (raw)
In-Reply-To: <1420714168-4994-2-git-send-email-mr.zoltan.gyarmati@gmail.com>

Dear Zoltan Gyarmati,

On Thu,  8 Jan 2015 11:49:28 +0100, Zoltan Gyarmati wrote:
> Signed-off-by: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
> ---
>  package/python/python.mk | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/python/python.mk b/package/python/python.mk
> index 45b1f7f..bf063e9 100644
> --- a/package/python/python.mk
> +++ b/package/python/python.mk
> @@ -33,6 +33,7 @@ HOST_PYTHON_CONF_OPTS += 	\
>  	--disable-test-modules	\
>  	--disable-bz2		\
>  	--disable-ssl		\
> +	--disable-ossaudiodev	\
>  	--disable-pyo-build
>  
>  # Make sure that LD_LIBRARY_PATH overrides -rpath.

Thanks for the patches.

Should we also make it optional for the target Python?

What about Python 3?

Thanks,

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

  reply	other threads:[~2015-01-08 12:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 10:49 [Buildroot] [PATCH 1/2] Add python patch to make ossaudiodev module building optional Zoltan Gyarmati
2015-01-08 10:49 ` [Buildroot] [PATCH 2/2] host-python: disable building ossaudiodev module Zoltan Gyarmati
2015-01-08 12:49   ` Thomas Petazzoni [this message]
2015-01-10 15:35 ` [Buildroot] [PATCH 1/2] Add python patch to make ossaudiodev module building optional 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=20150108134943.7afbaeb7@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