From: Simon Rowe <Simon.Rowe@citrix.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error building Python with musl in 2020.02
Date: Mon, 23 Mar 2020 09:33:21 +0000 [thread overview]
Message-ID: <1584956001741.25630@citrix.com> (raw)
In-Reply-To: <20200320223939.6d9972dc@gmx.net>
[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
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: defconfig
Type: application/octet-stream
Size: 122583 bytes
Desc: defconfig
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200323/149ed867/attachment-0001.obj>
next prev parent reply other threads:[~2020-03-23 9:33 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 [this message]
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=1584956001741.25630@citrix.com \
--to=simon.rowe@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox