All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "Wojciech M . Zabolotny" <wzab01@gmail.com>,
	Asaf Kahlon <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-msgpack: fix build without cpp toolchain
Date: Sun, 26 Nov 2023 21:56:54 +0100	[thread overview]
Message-ID: <20231126205654.GD3177259@scaer> (raw)
In-Reply-To: <20231126203341.2116704-1-james.hilliard1@gmail.com>

James, All,

On 2023-11-26 13:33 -0700, James Hilliard spake thusly:
> Prior to being updated to version 1.0.7 in
> 014a66fcde68bd0b612b62ec722ccc93bdc0d7f9 python-msgpack would
> automatically fall back to the pure python version if the cpp based
> optimized extension would fail to build for any reason.
> 
> This however is no longer the case after updating to 1.0.7 where it
> is now required that we explicitely set the MSGPACK_PUREPYTHON=1 if
> we do not have cpp support enabled in the toolchain.
> 
> Fixes:
>  - http://autobuild.buildroot.net/results/361/36185a19bed4bd57421a4d909bce1976c89d130f
>  - http://autobuild.buildroot.net/results/477/477f822cb196ebc2246bcbdc1b6eaf940fc018cd
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
>  package/python-msgpack/python-msgpack.mk | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/package/python-msgpack/python-msgpack.mk b/package/python-msgpack/python-msgpack.mk
> index 061ff5a761..82110b1776 100644
> --- a/package/python-msgpack/python-msgpack.mk
> +++ b/package/python-msgpack/python-msgpack.mk
> @@ -11,4 +11,8 @@ PYTHON_MSGPACK_LICENSE = Apache-2.0
>  PYTHON_MSGPACK_LICENSE_FILES = COPYING
>  PYTHON_MSGPACK_SETUP_TYPE = setuptools
>  
> +ifeq ($(BR2_INSTALL_LIBSTDCPP),)
> +PYTHON_MSGPACK_ENV = MSGPACK_PUREPYTHON=1
> +endif

As you explained on IRC, the value we set it to does not matter:
whatever the value (even empty!), it forces to use pure python code.
I.e. there is no way to force it to use C++.

Applied to master with a comment explaining that, thanks.

Regards,
Yann E. MORIN.

>  $(eval $(python-package))
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-11-26 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 20:33 [Buildroot] [PATCH 1/1] package/python-msgpack: fix build without cpp toolchain James Hilliard
2023-11-26 20:56 ` Yann E. MORIN [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=20231126205654.GD3177259@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=wzab01@gmail.com \
    /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.