All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Rowe <Simon.Rowe@citrix.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error building Python with musl in 2020.02
Date: Fri, 20 Mar 2020 15:12:07 +0000	[thread overview]
Message-ID: <1584717125169.78577@citrix.com> (raw)

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?


Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200320/29f1874a/attachment.html>

             reply	other threads:[~2020-03-20 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 15:12 Simon Rowe [this message]
2020-03-20 21:39 ` [Buildroot] Error building Python with musl in 2020.02 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

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=1584717125169.78577@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 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.