All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] Python3: Bump to 3.7.0
Date: Fri, 17 Aug 2018 23:35:04 +0200	[thread overview]
Message-ID: <20180817233504.6bea7129@windsurf> (raw)
In-Reply-To: <20180817184607.27639-1-aduskett@gmail.com>

Hello,

On Fri, 17 Aug 2018 11:46:07 -0700, Adam Duskett wrote:
> From: Adam Duskett <aduskett@greenlots.com>
> 
>   Other changes include:
> 
>   - Refreshing all necessary patches for 3.7.0
> 
>   - Add a hash for the license file.
> 
>   - Python no longer has it's own internal libffi, as such, host-libffi is now
>     required to build host-python3, and is added as a dependency.
> 
>   - A new core module "uuid" is now is added in the Config.in file, and relies
>     on util-linux's uuid library.
> 
>   - Also, a new patch: 0030-Fix-cross-compiling-the-uuid-module.patch is
>     required to fix compiling the uuid module, because the include directory
>     search path for uuid.h is hardcoded to /usr/include/uuid, which causes an
>     "unsafe for cross-compilation" error during compiling if the host pc has
>     uuid headers installed.
> 
>     To fix this error, a new variable called uuid_inc_dirs with the original
>     path of "/usr/include/uuid" is added to setup.py, then if the environment
>     variable STAGING_DIR exists, the STAGING_DIR path is added to the
>     beginning of the uuid_inc_dirs variable.
> 
>   - Add a new patch: 0031-fix-building-on-older-distributions.patch
>     This patch changes os.replace to os.rename in the update_file.py
>     script to fix building on older Linux distributions that have
>     older versions of python that don't include os.replace.
> 
>     os.rename acts in the same way as os.replace, but is cross-platform
>     compatible. Because Buildroot is guaranteed to be built in a POSIX
>     environment, it is safe to change replace to rename.
> 
> Tested on CentOS7 and Fedora28, All test results passed:
>              br-arm-full [1/6]: OK
>   br-arm-cortex-a9-glibc [2/6]: OK
>    br-arm-cortex-m4-full [3/6]: SKIPPED
>           br-x86-64-musl [4/6]: OK
>       br-arm-full-static [5/6]: SKIPPED
> armv5-ctng-linux-gnueabi [6/6]: OK
> 6 builds, 2 skipped, 0 build failed, 0 legal-info failed
> 
> Signed-off-by: Adam Duskett <aduskett@greenlots.com>

Ah, I was working on merging your v2 yesterday/today. Still looking at
a few things around UUID support. I'll make sure to use your v3 instead.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-17 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 18:46 [Buildroot] [PATCH v3 1/1] Python3: Bump to 3.7.0 Adam Duskett
2018-08-17 21:35 ` Thomas Petazzoni [this message]
2018-08-18  9:20 ` Thomas Petazzoni
2018-10-12 13:36   ` Matthew Weber
2018-08-19 13:56 ` Thomas Petazzoni
2018-08-19 21:10   ` Thomas Petazzoni
     [not found]   ` <SN6PR14MB21263CD05F33E8BEAAFC5A11C7330@SN6PR14MB2126.namprd14.prod.outlook.com>
     [not found]     ` <SN6PR14MB21260D8517E2E6E173EE7582C7330@SN6PR14MB2126.namprd14.prod.outlook.com>
2018-08-19 21:17       ` Thomas Petazzoni
2018-08-25 21:52 ` 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=20180817233504.6bea7129@windsurf \
    --to=thomas.petazzoni@bootlin.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 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.