From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Error building Python with musl in 2020.02
Date: Fri, 20 Mar 2020 22:39:39 +0100 [thread overview]
Message-ID: <20200320223939.6d9972dc@gmx.net> (raw)
In-Reply-To: <1584717125169.78577@citrix.com>
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
next prev parent reply other threads:[~2020-03-20 21:39 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 [this message]
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
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=20200320223939.6d9972dc@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.