Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[arrayfire] build failure #32862

Open
Bzz2745 opened this issue Aug 1, 2023 · 11 comments
Open

[arrayfire] build failure #32862

Bzz2745 opened this issue Aug 1, 2023 · 11 comments
Assignees
Labels
requires:repro The issue is not currently repro-able

Comments

@Bzz2745
Copy link

Bzz2745 commented Aug 1, 2023

Operating system

Linux(rhel 9)

Compiler

GCC

Steps to reproduce the behavior

`vcpkg install arrayfire[core,cpu,cuda,unified]:x64-linux`

Failure logs

Building arrayfire[core,cpu,cuda,unified]:x64-linux...
-- Downloading https://github.com/arrayfire/arrayfire/archive/d99887ae431fcd58168b653a1e69f027f04d5188.tar.gz -> arrayfire-arrayfire-d99887ae431fcd58168b653a1e69f027f04d5188.tar.gz...
-- Extracting source /home/bazunzhi/Environment/vcpkg/downloads/arrayfire-arrayfire-d99887ae431fcd58168b653a1e69f027f04d5188.tar.gz
-- Applying patch build.patch
-- Applying patch Fix-constexpr-error-with-vs2019-with-half.patch
-- Applying patch fix-dependency-clfft.patch
-- Using source at /home/bazunzhi/Environment/vcpkg/buildtrees/arrayfire/src/27f04d5188-42e72796d0.clean
-- Downloading https://github.com/arrayfire/threads/archive/b666773940269179f19ef11c8f1eb77005e85d9a.tar.gz -> arrayfire-threads-b666773940269179f19ef11c8f1eb77005e85d9a.tar.gz...
-- Extracting source /home/bazunzhi/Environment/vcpkg/downloads/arrayfire-threads-b666773940269179f19ef11c8f1eb77005e85d9a.tar.gz
-- Using source at /home/bazunzhi/Environment/vcpkg/buildtrees/arrayfire/src/7005e85d9a-64aebcce4b.clean
-- Downloading https://github.com/arrayfire/forge/archive/1a0f0cb6371a8c8053ab5eb7cbe3039c95132389.tar.gz -> arrayfire-forge-1a0f0cb6371a8c8053ab5eb7cbe3039c95132389.tar.gz...
-- Extracting source /home/bazunzhi/Environment/vcpkg/downloads/arrayfire-forge-1a0f0cb6371a8c8053ab5eb7cbe3039c95132389.tar.gz
-- Using source at /home/bazunzhi/Environment/vcpkg/buildtrees/arrayfire/src/9c95132389-511398ace8.clean
-- Configuring x64-linux
-- Building x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: /home/bazunzhi/Environment/vcpkg/downloads/tools/cmake-3.25.1-linux/cmake-3.25.1-linux-x86_64/bin/cmake --build . --config Debug --target install -- -v -j13
Working Directory: /home/bazunzhi/Environment/vcpkg/buildtrees/arrayfire/x64-linux-dbg
See logs for more information:
/home/bazunzhi/Environment/vcpkg/buildtrees/arrayfire/install-x64-linux-dbg-out.log

Call Stack (most recent call first):
installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
ports/arrayfire/portfile.cmake:93 (vcpkg_cmake_install)
scripts/ports.cmake:147 (include)

Additional context

install-x64-linux-dbg-out.log

@Bzz2745 Bzz2745 added the category:port-bug The issue is with a library, which is something the port should already support label Aug 1, 2023
@FrankXie05
Copy link
Contributor

FrankXie05 commented Aug 1, 2023

@Bzz2745 Could you please make sure whether cuda and cudnn are installed locally?

/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h: In instantiation of ‘constexpr fmt::v10::detail::value<Context> fmt::v10::detail::make_value(T&&) [with Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; T = cudnnStatus_t&]’:
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1711:29:   required from ‘constexpr fmt::v10::detail::value<Context> fmt::v10::detail::make_arg(T&&) [with bool IS_PACKED = true; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; fmt::v10::detail::type <anonymous> = fmt::v10::detail::type::custom_type; T = cudnnStatus_t&; typename std::enable_if<IS_PACKED, int>::type <anonymous> = 0]’
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1827:77:   required from ‘constexpr fmt::v10::format_arg_store<Context, Args>::format_arg_store(T&& ...) [with T = {cudnnStatus_t&, const char*&}; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; Args = {cudnnStatus_t, const char*}]’
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1844:31:   required from ‘constexpr fmt::v10::format_arg_store<Context, typename std::remove_cv<typename std::remove_reference<T>::type>::type ...> fmt::v10::make_format_args(T&& ...) [with Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; T = {cudnnStatus_t&, const char*&}]’
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:2817:44:   required from ‘std::string fmt::v10::format(fmt::v10::format_string<T ...>, T&& ...) [with T = {cudnnStatus_t&, const char*}; std::string = std::__cxx11::basic_string<char>; fmt::v10::format_string<T ...> = fmt::v10::basic_format_string<char, cudnnStatus_t&, const char*>]’
/home/bazunzhi/Environment/vcpkg/buildtrees/arrayfire/src/27f04d5188-42e72796d0.clean/src/backend/cuda/platform.cpp:126:39:   required from here
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1691:7: error: static assertion failed: Cannot format an argument. To make type T formattable provide a formatter<T> specialization: https://fmt.dev/latest/api.html#udt
 1691 |       formattable,
      |       ^~~~~~~~~~~
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1691:7: note: ‘formattable’ evaluates to false

@FrankXie05 FrankXie05 added requires:more-information This Issue requires more information to solve and removed category:port-bug The issue is with a library, which is something the port should already support labels Aug 1, 2023
@Bzz2745
Copy link
Author

Bzz2745 commented Aug 1, 2023

@Bzz2745 Could you please make sure whether cuda and cudnn are installed locally?

/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h: In instantiation of ‘constexpr fmt::v10::detail::value<Context> fmt::v10::detail::make_value(T&&) [with Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; T = cudnnStatus_t&]’:
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1711:29:   required from ‘constexpr fmt::v10::detail::value<Context> fmt::v10::detail::make_arg(T&&) [with bool IS_PACKED = true; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; fmt::v10::detail::type <anonymous> = fmt::v10::detail::type::custom_type; T = cudnnStatus_t&; typename std::enable_if<IS_PACKED, int>::type <anonymous> = 0]’
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1827:77:   required from ‘constexpr fmt::v10::format_arg_store<Context, Args>::format_arg_store(T&& ...) [with T = {cudnnStatus_t&, const char*&}; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; Args = {cudnnStatus_t, const char*}]’
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1844:31:   required from ‘constexpr fmt::v10::format_arg_store<Context, typename std::remove_cv<typename std::remove_reference<T>::type>::type ...> fmt::v10::make_format_args(T&& ...) [with Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; T = {cudnnStatus_t&, const char*&}]’
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:2817:44:   required from ‘std::string fmt::v10::format(fmt::v10::format_string<T ...>, T&& ...) [with T = {cudnnStatus_t&, const char*}; std::string = std::__cxx11::basic_string<char>; fmt::v10::format_string<T ...> = fmt::v10::basic_format_string<char, cudnnStatus_t&, const char*>]’
/home/bazunzhi/Environment/vcpkg/buildtrees/arrayfire/src/27f04d5188-42e72796d0.clean/src/backend/cuda/platform.cpp:126:39:   required from here
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1691:7: error: static assertion failed: Cannot format an argument. To make type T formattable provide a formatter<T> specialization: https://fmt.dev/latest/api.html#udt
 1691 |       formattable,
      |       ^~~~~~~~~~~
/home/bazunzhi/Environment/vcpkg/installed/x64-linux/include/fmt/core.h:1691:7: note: ‘formattable’ evaluates to false

This step cannot be reached without installing CUDA and CUDNN, because vcpkg needs to install CUDA and CUDNN before that, and will automatically check whether it is installed.

@FrankXie05 FrankXie05 added requires:repro The issue is not currently repro-able and removed requires:more-information This Issue requires more information to solve labels Aug 8, 2023
@FrankXie05
Copy link
Contributor

@Bzz2745 It seems that fmt does not provide special formatting operations for type cudnnStatus_t, it should be reported to fmt. Let the fmt upstream know. https://github.com/fmtlib/fmt

@JackBoosY
Copy link
Contributor

@Bzz2745 It seems that fmt does not provide special formatting operations for type cudnnStatus_t, it should be reported to fmt. Let the fmt upstream know. https://github.com/fmtlib/fmt

Any upstream issue link here?

@Bzz2745
Copy link
Author

Bzz2745 commented Aug 9, 2023

It seems that fmt does not provide special formatting operations for type cudnnStatus_t

fmtlib/fmt#3579
I have just open this issue today ,waitting for there reply.

@github-actions
Copy link

github-actions bot commented Sep 7, 2023

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added Stale and removed Stale labels Sep 7, 2023
@trenta3
Copy link

trenta3 commented Sep 7, 2023

I'm still interested in the resolution of this issue

@anya-nlp
Copy link

This looks like an arrayfire issue, is that right?

@dg0yt
Copy link
Contributor

dg0yt commented Sep 27, 2023

This looks like an arrayfire issue, is that right?

Yes.

@anya-nlp
Copy link

This looks like an arrayfire issue, is that right?

Yes.

I created an issue for arrayfire to hopefully take a look at: arrayfire/arrayfire#3506

@github-actions
Copy link

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added Stale and removed Stale labels Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
requires:repro The issue is not currently repro-able
Projects
None yet
Development

No branches or pull requests

6 participants