Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Flaviu Nistor <flaviu.nistor@gmail.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Flaviu Nistor <flaviu.nistor@gmail.com>,
	James Hilliard <james.hilliard1@gmail.com>,
	Julien Olivain <ju.o@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 RESEND 1/3] package/python-cramjam: new package
Date: Thu, 15 Oct 2026 20:01:01 +0300	[thread overview]
Message-ID: <20261015170101.5001-1-flaviu.nistor@gmail.com> (raw)
In-Reply-To: <87ld80s06p.fsf@dell.be.48ers.dk>

On Wed, Oct 14, 2026 at 7:42 PM, Peter Korsgaard wrote:

>Hi,
>
>>> So presumably something is not initialized to cause this null pointer
>>> exception. The fact that PyImport_ResolveNameWithPackageContext gets
>>> called with a null pointer is already odd.
>>> 
>>> Care to report it upstream? I see that there is in the mean time a 2.13
>>> release.
>
>> I saw a related issue reported with a similar topic that it can't be tested
>> on 32-bit architectures. This is way I specified depends on !BR2_ARM_CPU_ARMV5,
>
>OK, but then it should presumably have been blocked on all 32bit
>architectures and not just ARMv5. This is really the kind of nonobvious
>stuff that should go into the commit message.
>

Yes, you are write. I have checked after your initial reply and also armv7 was failing.
Once I realized that 32-bit will fail I switch directly to aarch64 and forget to
include also armv7 together with armv5.
In similar situations I will take care in the future to explain such details in the commit.

>> since at that time I found no other solution. I have tested today and version
>> 2.14.0 (released today) does not have this issue any more, so it runs on armv5.
>> James Hilliard just send a bump for 2.14.0, so for v5 I will not include this.
>> Here is the link to the bump:
>> https://lore.kernel.org/all/20261013164254.1476592-6-james.hilliard1@gmail.com/
>
>OK, good.
>
>-- 
>Bye, Peter Korsgaard

Thanks again,
Flaviu Nistor
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-15 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87cxtgh7kp.fsf@dell.be.48ers.dk>
2026-10-13 18:45 ` [Buildroot] [PATCH v4 RESEND 1/3] package/python-cramjam: new package Flaviu Nistor
2026-10-14 16:42   ` Peter Korsgaard
2026-10-15 17:01     ` Flaviu Nistor [this message]
2026-10-02 10:31 Flaviu Nistor
2026-10-11  7:53 ` Peter Korsgaard

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=20261015170101.5001-1-flaviu.nistor@gmail.com \
    --to=flaviu.nistor@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --cc=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox