Re: pytorch FTBFS with Python 3.11 as default version
Hi,
Am Sat, Jan 28, 2023 at 03:09:47AM +0800 schrieb Aron Xu:
> On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille <tille@debian.org> wrote:
> >
> > So what help could I (as someone who does not know pytorch at all, just
> > maintains some packages that are depending from it) can I provide?
> >
>
> Here is the fail log just in case you can have a look...
>
> /build/pytorch/build$ ninja
> [1/5] Building CXX object
> caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o
> FAILED: caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o
> /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DBUILDING_TESTS
> -DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT
> -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1
> -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS
> -DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx
> -DTHP_BUILD_MAIN_LIB -DUSE_C10D -DUSE_C10D_GLOO -DUSE_DISTRIBUTED
> -DUSE_EXTERNAL_MZCRC -DUSE_NUMPY -DUSE_RPC -DUSE_TENSORPIPE
> -DUSE_VALGRIND -D_FILE_OFFSET_BITS=64 -Dtorch_python_EXPORTS
> -I/build/pytorch/build/aten/src -I/build/pytorch/aten/src
> -I/build/pytorch/build -I/build/pytorch
> -I/build/pytorch/cmake/../third_party/benchmark/include
> -I/build/pytorch/debian/foxi -I/build/pytorch/build/debian/foxi
> -I/build/pytorch/torch/.. -I/build/pytorch/torch/../aten/src
> -I/build/pytorch/torch/../aten/src/TH
> -I/build/pytorch/build/caffe2/aten/src
> -I/build/pytorch/build/third_party
> -I/build/pytorch/build/third_party/onnx
> -I/build/pytorch/torch/../third_party/valgrind-headers
> -I/build/pytorch/torch/../third_party/gloo
> -I/build/pytorch/torch/../third_party/onnx
> -I/build/pytorch/torch/../third_party/flatbuffers/include
> -I/build/pytorch/debian/kineto/libkineto/include
> -I/build/pytorch/torch/csrc -I/build/pytorch/torch/csrc/api/include
> -I/build/pytorch/torch/lib -I/build/pytorch/torch/lib/libshm
> -I/build/pytorch/torch/csrc/api -I/build/pytorch/c10/..
> -I/build/pytorch/torch/lib/libshm/../../../torch/lib -isystem
> /build/pytorch/build/third_party/gloo -isystem
> /build/pytorch/cmake/../third_party/gloo -isystem
> /build/pytorch/cmake/../third_party/googletest/googlemock/include
> -isystem /build/pytorch/cmake/../third_party/googletest/googletest/include
> -isystem /usr/include/opencv4 -isystem /usr/include/eigen3 -isystem
> /usr/include/python3.11 -isystem
> /usr/lib/python3/dist-packages/numpy/core/include -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/pytorch=.
> -fstack-protector-strong -Wformat -Werror=format-security
> -gsplit-dwarf -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp
> -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE
> -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra
> -Werror=return-type -Werror=non-virtual-dtor
> -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds
> -Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter
> -Wno-unused-function -Wno-unused-result -Wno-strict-overflow
> -Wno-strict-aliasing -Wno-error=deprecated-declarations
> -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic
> -Wno-error=redundant-decls -Wno-error=old-style-cast
> -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable
> -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math
> -Werror=format -Werror=cast-function-type -Wno-stringop-overflow
> -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O2 -g
> -DNDEBUG -fPIC -DCAFFE2_USE_GLOO -DTH_HAVE_THREAD -Wno-unused-variable
> -fno-strict-aliasing -Wno-write-strings -Wno-strict-aliasing
> -std=gnu++14 -MD -MT
> caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o -MF
> caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o.d -o
> caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o -c
> /build/pytorch/torch/csrc/Exceptions.cpp
> /build/pytorch/torch/csrc/Exceptions.cpp: In destructor
> 'torch::PyWarningHandler::~PyWarningHandler()':
> /build/pytorch/torch/csrc/Exceptions.cpp:264:23: error: no matching
> function for call to 'format_to(fmt::v9::memory_buffer&,
> torch::PyWarningHandler::~PyWarningHandler()::<lambda()>::FMT_COMPILE_STRING,
> std::__cxx11::basic_string<char>&, const char*&, uint32_t&)'
> 264 | fmt::format_to(
> | ~~~~~~~~~~~~~~^
> 265 | buf,
> | ~~~~
> 266 | FMT_STRING("{} (Triggered internally at {}:{}.)"),
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 267 | msg,
> | ~~~~
> 268 | source_location.file,
> | ~~~~~~~~~~~~~~~~~~~~~
> 269 | source_location.line);
> | ~~~~~~~~~~~~~~~~~~~~~
> In file included from /usr/include/fmt/format.h:48,
> from /build/pytorch/torch/csrc/Exceptions.cpp:10:
> /usr/include/fmt/core.h:3233:17: note: candidate: 'template<class
> OutputIt, class ... T, typename
> std::enable_if<fmt::v9::detail::is_output_iterator<OutputIt,
> char>::value, int>::type <anonymous> > OutputIt
> fmt::v9::format_to(OutputIt, format_string<T ...>, T&& ...)'
> 3233 | FMT_INLINE auto format_to(OutputIt out, format_string<T...>
> fmt, T&&... args)
> | ^~~~~~~~~
> /usr/include/fmt/core.h:3233:17: note: template argument
> deduction/substitution failed:
> /usr/include/fmt/core.h:3232:11: error: no type named 'type' in
> 'struct std::enable_if<false, int>'
> 3232 | FMT_ENABLE_IF(detail::is_output_iterator<OutputIt,
> char>::value)>
> | ^~~~~~~~~~~~~
> /usr/include/fmt/format.h:4202:17: note: candidate: 'template<class
> OutputIt, class Locale, class ... T, typename
> std::enable_if<(fmt::v9::detail::is_output_iterator<OutputIt,
> char>::value && fmt::v9::detail::is_locale<Locale>::value), int>::type
> <anonymous> > OutputIt fmt::v9::format_to(OutputIt, const Locale&,
> format_string<T ...>, T&& ...)'
> 4202 | FMT_INLINE auto format_to(OutputIt out, const Locale& loc,
> | ^~~~~~~~~
> /usr/include/fmt/format.h:4202:17: note: template argument
> deduction/substitution failed:
> /usr/include/fmt/format.h:4200:11: error: no type named 'type' in
> 'struct std::enable_if<false, int>'
> 4200 | FMT_ENABLE_IF(detail::is_output_iterator<OutputIt,
> char>::value&&
> | ^~~~~~~~~~~~~
> ninja: build stopped: subcommand failed.
I have no idea about fmtlib but I noticed:
[2022-09-04] fmtlib 9.1.0+ds1-2 MIGRATED to testing (Debian testing watch)
[2022-09-04] Accepted fmtlib 9.1.0+ds1-2 (source) into unstable (Shengjing Zhu)
[2022-08-27] Accepted fmtlib 9.1.0+ds1-1 (source) into experimental (Shengjing Zhu)
[2022-08-24] fmtlib 9.0.0+ds1-4 MIGRATED to testing (Debian testing watch)
Is this failure dating back to August last year and possibly connected to
the version bump from 9.00 to 9.1.0?
May be my question is naive but just asking.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: