All of 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: Mon, 23 Mar 2020 18:42:04 +0100	[thread overview]
Message-ID: <20200323184204.4aab32ad@gmx.net> (raw)
In-Reply-To: <1584956001741.25630@citrix.com>

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

>
> Simon
>
> ________________________________________
> From: Peter Seiderer <ps.report@gmx.net>
> Sent: 20 March 2020 21:39
> To: Simon Rowe
> Cc: buildroot at busybox.net
> Subject: Re: [Buildroot] Error building Python with musl in 2020.02
>
> Hello Simon,
>
> On Fri, 20 Mar 2020 15:12:07 +0000, Simon Rowe <Simon.Rowe@citrix.com> wrote:
>
> > I'm getting the following error when trying out 2020.02 with the latest musl-based toolchain
> >
> >
> > /build/host/bin/x86_64-buildroot-linux-musl-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Os   -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Os    -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration  -I./Include/internal  -I. -I./Include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -fPIC -DPy_BUILD_CORE_BUILTIN  -c ./Modules/xxsubtype.c -o Modules/xxsubtype.o
> > ./Modules/posixmodule.c: In function 'os_copy_file_range_impl':
> > ./Modules/posixmodule.c:9704:15: error: implicit declaration of function 'copy_file_range'; did you mean 'sync_file_range'? [-Werror=implicit-function-declaration]
> >  9704 |         ret = copy_file_range(src, p_offset_src, dst, p_offset_dst, count, flags);
> >       |               ^~~~~~~~~~~~~~~
> >       |               sync_file_range
> > cc1: some warnings being treated as errors
> > Makefile:1938: recipe for target 'Modules/posixmodule.o' failed
> >
> >
> > Has anyone else seen this?
>
> Python or python3? Could you provide a .config or defconfig file
> for the failure?
>
> Regards,
> Peter
>
> >
> >
> > Simon
>

  reply	other threads:[~2020-03-23 17:42 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 [this message]
     [not found]       ` <1585215897497.45733@citrix.com>
2020-03-26 15:50         ` Peter Seiderer

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=20200323184204.4aab32ad@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 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.