Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Vu-Brugier <cvubrugier@fastmail.fm>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] python3: add patch to fix PEP 3147 issue with automake built packages
Date: Sat, 14 Nov 2015 17:01:04 +0100	[thread overview]
Message-ID: <20151114170104.191b0f8a@trantor> (raw)
In-Reply-To: <871tbtlgke.fsf@dell.be.48ers.dk>

Hi,

On Fri, 13 Nov 2015 22:45:05 +0100, Peter Korsgaard wrote :
> >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:  
> 
> Hi,
> 
>  >> 2/ Simply do not regenerate "importlib.h" because it is not
>  >> used.  
> 
>  >  Most likely, the generated importlib.h doesn't change due to your
>  > patch. So the simplest solution is to do a 'touch
>  > $(@D)/Python/importlib.h' in a post-patch hook (with a large
>  > comment explaining why it is necessary and allowed).  

Well importlib.h is changed because it contains the bytecode
of _bootstrap.py which is patched. However, importlib.h is not
installed in staging and Debian does not ship the header even in
development packages so it's useless.


> Yes, sounds sensible. Christophe, care to send a patch?

Patch sent with subject "[PATCH v3] python3: add patch to fix PEP 3147
issue with automake built packages".

Thanks and best regards,

-- 
Christophe Vu-Brugier

      reply	other threads:[~2015-11-14 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 12:21 [Buildroot] [PATCH v2] python3: add patch to fix PEP 3147 issue with automake built packages Christophe Vu-Brugier
2015-11-04 21:55 ` Thomas Petazzoni
2015-11-04 23:04   ` Thomas Petazzoni
2015-11-12 15:31     ` Christophe Vu-Brugier
2015-11-13  7:02       ` Arnout Vandecappelle
2015-11-13 21:45         ` Peter Korsgaard
2015-11-14 16:01           ` Christophe Vu-Brugier [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=20151114170104.191b0f8a@trantor \
    --to=cvubrugier@fastmail.fm \
    --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