question
stringlengths
235
464k
answer
stringlengths
11
2.11k
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [rubygem(actionpack) = 8.0.2]: [The `rubygem(actionpack)` dependency can't be installed.]
Issue: The `rubygem(actionpack)` dependency can't be installed. This dependency would be satisfied by `rubygem-actionpack` package. In this specific case, the package is not available for ppc64le platform. Resolution: Make sure the `rubygem-actionpack` is available for the ppc64le platform
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: rubygem(actionpack) = 8.0.2
The `rubygem(actionpack)` dependency can't be installed.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [error: command '/usr/bin/gcc' failed with exit code 1]: [Gcc with exit code 1 means that the compilation phase failed.] ============= [error: Bad exit status from /var/tmp/rpm-tmp.iulThE (%build)]: [Compilation failure failed the whole %build phase.] ============= [+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP']: [Gcc is executed using `python3 setup.py build` - so a "setuptools compilation" case.] ============= [gensim_addons/models/word2vec_inner.c:10941:76: error: assignment to ‘__pyx_t_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs_ptr’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, unsigned int *, const float, float *, int, int, int, int)’} from incompatible pointer type ‘void (*)(const __pyx_t_5numpy_uint32_t *, const __pyx_t_5numpy_uint8_t *, int *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, const int, const __pyx_t_5numpy_uint32_t *, const __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, int, int, int, int)’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, const unsigned int *, const float, float *, int, int, int, int)’} [-Wincompatible-pointer-types] 10941 | __pyx_v_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs = __pyx_f_13gensim_addons_6models_14word2vec_inner_fast_sentence0_cbow_hs; | ^ gensim_addons/models/word2vec_inner.c:11008:76: error: assignment to ‘__pyx_t_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs_ptr’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, unsigned int *, const float, float *, int, int, int, int)’} from incompatible pointer type ‘void (*)(const __pyx_t_5numpy_uint32_t *, const __pyx_t_5numpy_uint8_t *, int *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, const int, const __pyx_t_5numpy_uint32_t *, const __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, int, int, int, int)’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, const unsigned int *, const float, float *, int, int, int, int)’} [-Wincompatible-pointer-types] 11008 | __pyx_v_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs = __pyx_f_13gensim_addons_6models_14word2vec_inner_fast_sentence1_cbow_hs; | ^ gensim_addons/models/word2vec_inner.c:11066:76: error: assignment to ‘__pyx_t_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs_ptr’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, unsigned int *, const float, float *, int, int, int, int)’} from incompatible pointer type ‘void (*)(const __pyx_t_5numpy_uint32_t *, const __pyx_t_5numpy_uint8_t *, int *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, const int, const __pyx_t_5numpy_uint32_t *, const __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, int, int, int, int)’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, const unsigned int *, const float, float *, int, int, int, int)’} [-Wincompatible-pointer-types] 11066 | __pyx_v_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs = __pyx_f_13gensim_addons_6models_14word2vec_inner_fast_sentence2_cbow_hs; | ^]: [These seem like incompatible pointer assignment errors.]
Issue: Incompatible C/C++ pointer assignment in source code. Resolution: The source code needs a fix. Either the source or the destination pointer needs to be fixed.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: error: command '/usr/bin/gcc' failed with exit code 1
Gcc with exit code 1 means that the compilation phase failed.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: error: Bad exit status from /var/tmp/rpm-tmp.iulThE (%build)
Compilation failure failed the whole %build phase.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP'
Gcc is executed using `python3 setup.py build` - so a "setuptools compilation" case.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: gensim_addons/models/word2vec_inner.c:10941:76: error: assignment to ‘__pyx_t_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs_ptr’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, unsigned int *, const float, float *, int, int, int, int)’} from incompatible pointer type ‘void (*)(const __pyx_t_5numpy_uint32_t *, const __pyx_t_5numpy_uint8_t *, int *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, const int, const __pyx_t_5numpy_uint32_t *, const __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, int, int, int, int)’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, const unsigned int *, const float, float *, int, int, int, int)’} [-Wincompatible-pointer-types] 10941 | __pyx_v_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs = __pyx_f_13gensim_addons_6models_14word2vec_inner_fast_sentence0_cbow_hs; | ^ gensim_addons/models/word2vec_inner.c:11008:76: error: assignment to ‘__pyx_t_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs_ptr’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, unsigned int *, const float, float *, int, int, int, int)’} from incompatible pointer type ‘void (*)(const __pyx_t_5numpy_uint32_t *, const __pyx_t_5numpy_uint8_t *, int *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, const int, const __pyx_t_5numpy_uint32_t *, const __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, int, int, int, int)’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, const unsigned int *, const float, float *, int, int, int, int)’} [-Wincompatible-pointer-types] 11008 | __pyx_v_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs = __pyx_f_13gensim_addons_6models_14word2vec_inner_fast_sentence1_cbow_hs; | ^ gensim_addons/models/word2vec_inner.c:11066:76: error: assignment to ‘__pyx_t_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs_ptr’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, unsigned int *, const float, float *, int, int, int, int)’} from incompatible pointer type ‘void (*)(const __pyx_t_5numpy_uint32_t *, const __pyx_t_5numpy_uint8_t *, int *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, const int, const __pyx_t_5numpy_uint32_t *, const __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t, __pyx_t_13gensim_addons_6models_14word2vec_inner_REAL_t *, int, int, int, int)’ {aka ‘void (*)(const unsigned int *, const unsigned char *, int *, float *, float *, float *, const int, const unsigned int *, const float, float *, int, int, int, int)’} [-Wincompatible-pointer-types] 11066 | __pyx_v_13gensim_addons_6models_14word2vec_inner_fast_sentence_cbow_hs = __pyx_f_13gensim_addons_6models_14word2vec_inner_fast_sentence2_cbow_hs; | ^
These seem like incompatible pointer assignment errors.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [curl: (22) The requested URL returned error: 404 ]: [Download of the external script has failed with HTTP return code 404 (can't be reached).] ============= [error: Executing url helper "/usr/bin/curl --proto -all,+https,+ftps --silent --show-error --fail --globoff --location -o /var/lib/copr-rpmbuild/results/run-mozilla.sh https://hg.mozilla.org/mozilla-central/raw-file/tip/build/unix/run-mozilla.sh" failed with status 22 error: Couldn't download https://hg.mozilla.org/mozilla-central/raw-file/tip/build/unix/run-mozilla.sh]: [During the SRPM creation the helper script (https://hg.mozilla.org/mozilla-central/raw-file/tip/build/unix/run-mozilla.sh) used to create the RPM couldn't be downloaded by curl so execution of the script has failed.]
Issue: A script used to create RPM during the SRPM creation step can't be downloaded because it is not reachable on the given URL. Because SRPM can't be created the RPM build can't be executed. Resolution: Please make sure that the script is available on the given link. If not please fix the link. Another possibility is that the build environment doesn't have internet access or doesn't have access to this specific URL. In that case you should enable access of this URL in the build environment.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: curl: (22) The requested URL returned error: 404
Download of the external script has failed with HTTP return code 404 (can't be reached).
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: error: Executing url helper "/usr/bin/curl --proto -all,+https,+ftps --silent --show-error --fail --globoff --location -o /var/lib/copr-rpmbuild/results/run-mozilla.sh https://hg.mozilla.org/mozilla-central/raw-file/tip/build/unix/run-mozilla.sh" failed with status 22 error: Couldn't download https://hg.mozilla.org/mozilla-central/raw-file/tip/build/unix/run-mozilla.sh
During the SRPM creation the helper script (https://hg.mozilla.org/mozilla-central/raw-file/tip/build/unix/run-mozilla.sh) used to create the RPM couldn't be downloaded by curl so execution of the script has failed.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl]: [Error message with build failure cause.] ============= [xsltproc --nonet -o doc/ambiguous_words.1 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl -]: [Origin call for internet access.]
Issue: There was intention to download data from the internet during the build. This is not allowed as per https://docs.fedoraproject.org/en-US/packaging-guidelines/#_build_time_network_access Resolution: Make sure the package doesn't require downloading anything during the build phase.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
Error message with build failure cause.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: xsltproc --nonet -o doc/ambiguous_words.1 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl -
Origin call for internet access.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [No matching package to install: 'gstreamer1-devel' No matching package to install: 'gtk2-devel']: [shows that the following packages cannot be installed]
Issue: because DNF command failed to install some packages Resolution: make sure that the packages can be installed on the build system
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: No matching package to install: 'gstreamer1-devel' No matching package to install: 'gtk2-devel'
shows that the following packages cannot be installed
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [error: ‘uint64_t’ was not declared in this scope ]: [The relevant error message from the compiler saying that 'uint64_t' is not declared.] ============= [note: ‘uint64_t’ is defined in header ‘<cstdint>’; this is probably fixable by adding ‘#include <cstdint>’]: [The relevant compiler suggestion that the missing symbol is declared in the 'cstdint' header.]
Issue: An undeclared symbol caused build failure of a particular 'sample_vpp_frc_adv' object and failed the complete build. Resolution: Add '#include <cstdint>' in the 'sample_vpp_frc_adv.cpp' source file.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: error: ‘uint64_t’ was not declared in this scope
The relevant error message from the compiler saying that 'uint64_t' is not declared.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: note: ‘uint64_t’ is defined in header ‘&lt;cstdint&gt;’; this is probably fixable by adding ‘#include &lt;cstdint&gt;’
The relevant compiler suggestion that the missing symbol is declared in the 'cstdint' header.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-path] - a... FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-path-custom-msg] FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-obj] - as... FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-obj-custom-msg] FAILED tests/test_compat.py::TestDeprecated::test_deprecated[no-warning-has-attr] FAILED tests/test_compat.py::TestDeprecated::test_deprecated[no-warning-has-getattr]]: [Six tests failed during the %check section.] ============= [E assert [<_py_warning...7fa480e129f0>] == [] E E Left contains one more item: <_py_warnings.WarningMessage object at 0x7fa480e129f0> E Use -v to get more diff]: [One of the test failures indicates an assertion failed because of an unexpected warning. The other failures have similar messages.]
Issue: The build uses version 7.1.3 of the software, and previously passed with Python 3.13. These warnings are new for Python 3.14. The upstream tests for this version of the software are not yet compatible with Python 3.14. Resolution: Update the version to an upstream version that is compatible with Python 3.14.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-path] - a... FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-path-custom-msg] FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-obj] - as... FAILED tests/test_compat.py::TestDeprecated::test_deprecated[import-obj-custom-msg] FAILED tests/test_compat.py::TestDeprecated::test_deprecated[no-warning-has-attr] FAILED tests/test_compat.py::TestDeprecated::test_deprecated[no-warning-has-getattr]
Six tests failed during the %check section.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: E assert [<_py_warning...7fa480e129f0>] == [] E E Left contains one more item: <_py_warnings.WarningMessage object at 0x7fa480e129f0> E Use -v to get more diff
One of the test failures indicates an assertion failed because of an unexpected warning. The other failures have similar messages.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [Received signal SIGTERM activating orphansKill ]: [This is the only indication of why the build didn't complete.]
Issue: The build tool received a SIGTERM signal, likely due to a timeout or exceeding a maximum execution duration. Resolution: Try it again.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: Received signal SIGTERM activating orphansKill
This is the only indication of why the build didn't complete.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [not ok /fwupd/polkit-agent - ERROR:../src/fu-polkit-test.c:19:fu_polkit_agent_func: assertion failed (error == NULL): missing pkttyagent (FwupdError, 10)]: [It contains the error message which caused unit tests to fail.]
Issue: Unit tests failed due to a missing build-time dependency on pkttyagent, which is a binary provided by polkit. Resolution: The polkit package should be added to BuildRequires in the spec file.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: not ok /fwupd/polkit-agent - ERROR:../src/fu-polkit-test.c:19:fu_polkit_agent_func: assertion failed (error == NULL): missing pkttyagent (FwupdError, 10)
It contains the error message which caused unit tests to fail.
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package. Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation. Snippets are delimited with '================'. Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution. Explanation of the issue, and recommended solution, should take a handful of sentences. Snippets: [gcc -c -D_REENTRANT -D_GNU_SOURCE -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fwrapv -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -DVERSION=\"0.310100\" -DXS_VERSION=\"0.310100\" -fPIC "-I/usr/lib64/perl5/CORE" CommonMark.c CommonMark.c: In function ‘XS_CommonMark__Node_interface_get_node’: CommonMark.c:682:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 1 682 | RETVAL = XSFUNCTION(node); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_get_int’: CommonMark.c:708:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 1 708 | RETVAL = XSFUNCTION(node); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_set_int’: CommonMark.c:736:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 736 | RETVAL = XSFUNCTION(node, value); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_get_utf8’: CommonMark.c:761:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 1 761 | RETVAL = XSFUNCTION(node); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_set_utf8’: CommonMark.c:790:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 790 | RETVAL = XSFUNCTION(node, value); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_move_node’: CommonMark.c:889:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 889 | RETVAL = XSFUNCTION(node, other); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_render’: CommonMark.c:927:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 927 | RETVAL = XSFUNCTION(root, options); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_render_width’: CommonMark.c:973:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 3 973 | RETVAL = XSFUNCTION(root, options, width); | ^~~~~~~~~~ ~~~~ make: *** [Makefile:351: CommonMark.o] Error 1]: [contains the actual failures (essentially the same one several times over)]
Issue: The build ran with GCC 15, which bumps the default C version to C23. C23 changed the meaning of an empty prototype from "unspecified number of arguments" to "no arguments", so now the functions generated by perlxs always expect zero arguments, which will usually break. Resolution: A real fix is still pending in upstream perl - see https://github.com/Perl/perl5/issues/23192 - but a quick fix is to build with -std=c17 to use an older C version with the older meaning of an empty prototype.
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution. Your analysis must be as concise as possible, while keeping relevant information intact. Snippet: gcc -c -D_REENTRANT -D_GNU_SOURCE -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fwrapv -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -DVERSION=\"0.310100\" -DXS_VERSION=\"0.310100\" -fPIC "-I/usr/lib64/perl5/CORE" CommonMark.c CommonMark.c: In function ‘XS_CommonMark__Node_interface_get_node’: CommonMark.c:682:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 1 682 | RETVAL = XSFUNCTION(node); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_get_int’: CommonMark.c:708:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 1 708 | RETVAL = XSFUNCTION(node); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_set_int’: CommonMark.c:736:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 736 | RETVAL = XSFUNCTION(node, value); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_get_utf8’: CommonMark.c:761:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 1 761 | RETVAL = XSFUNCTION(node); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_set_utf8’: CommonMark.c:790:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 790 | RETVAL = XSFUNCTION(node, value); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_move_node’: CommonMark.c:889:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 889 | RETVAL = XSFUNCTION(node, other); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_render’: CommonMark.c:927:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 2 927 | RETVAL = XSFUNCTION(root, options); | ^~~~~~~~~~ ~~~~ CommonMark.c: In function ‘XS_CommonMark__Node_interface_render_width’: CommonMark.c:973:18: error: too many arguments to function ‘XSFUNCTION’; expected 0, have 3 973 | RETVAL = XSFUNCTION(root, options, width); | ^~~~~~~~~~ ~~~~ make: *** [Makefile:351: CommonMark.o] Error 1
contains the actual failures (essentially the same one several times over)