Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Error building Python with musl in 2020.02
Date: Thu, 26 Mar 2020 16:50:04 +0100	[thread overview]
Message-ID: <20200326165004.015bff28@gmx.net> (raw)
In-Reply-To: <1585215897497.45733@citrix.com>

Hello Simon,

re-add CC: buildroot at busybox.net

On Thu, 26 Mar 2020 09:44:57 +0000, Simon Rowe <Simon.Rowe@citrix.com> wrote:

> Thanks for looking at this Peter, I did a cleanup of my work directory and a rebuild worked. Must have has some stale junk, sorry for the noise,

That's good news ;-), thanks for the feedback...

Regards,
Peter

>
> Simon
> ________________________________________
> From: Peter Seiderer <ps.report@gmx.net>
> Sent: 23 March 2020 17:42
> To: Simon Rowe
> Cc: buildroot at busybox.net
> Subject: Re: [Buildroot] Error building Python with musl in 2020.02
>
> Hello Simon,
>
> On Mon, 23 Mar 2020 09:33:21 +0000, Simon Rowe <Simon.Rowe@citrix.com> wrote:
>
> > [Apologies for the top posting, stuck with web-based email]
> >
> > python3, defconfig attached. This config has been working with 2019.02, I loaded and re-saved it
>
> Given defconfig still compiles fine here....
>
> - ./build/python3-3.8.2/Modules/posixmodule.c:
>   The usage of copy_file_range() is protected by HAVE_COPY_FILE_RANGE
>
> - HAVE_COPY_FILE_RANGE is defined in pyconfig.h:
>         $ grep HAVE_COPY_FILE_RANGE build/python3-3.8.2/pyconfig.h
> #define HAVE_COPY_FILE_RANGE 1
>
> - the buildroot compiled musl libc proviedes copy_file_range:
>
>         $ nm -A host/x86_64-buildroot-linux-musl/sysroot/lib/libc.so | grep copy_file_range
> host/x86_64-buildroot-linux-musl/sysroot/lib/libc.so:000000000001f4bd T copy_file_range
>
> - the header file provides copy_file_range() (protected by _GNU_SOURCE)
>
>         $ grep copy_file_range host/x86_64-buildroot-linux-musl/sysroot/usr/include/unistd.h
> ssize_t copy_file_range(int, off_t *, int, off_t *, size_t, unsigned);
>
> Please try a plain defconfig (without EXTERNALs), make sure no additional patches/config files
> are used.....otherwise out of ideas...
>
> Regards,
> Peter

      parent reply	other threads:[~2020-03-26 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 15:12 [Buildroot] Error building Python with musl in 2020.02 Simon Rowe
2020-03-20 21:39 ` Peter Seiderer
2020-03-23  9:33   ` Simon Rowe
2020-03-23 17:42     ` Peter Seiderer
     [not found]       ` <1585215897497.45733@citrix.com>
2020-03-26 15:50         ` Peter Seiderer [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=20200326165004.015bff28@gmx.net \
    --to=ps.report@gmx.net \
    --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