Dataset Viewer
question
stringlengths 236
348k
| answer
stringlengths 10
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:
[+ mv /builddir/build/BUILDROOT/gimp-3.0.2-1.el9.x86_64/usr/share/doc/gimp-3.0.2 devel-docs
mv: cannot stat '/builddir/build/BUILDROOT/gimp-3.0.2-1.el9.x86_64/usr/share/doc/gimp-3.0.2': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.1HZv08 (%install)]: [This is a build error]
| Issue: The build process is trying to move directory that doesn't exist.
Resolution: The build command should be fixed so it points to directory that does exist or it should be removed all together. |
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:
+ mv /builddir/build/BUILDROOT/gimp-3.0.2-1.el9.x86_64/usr/share/doc/gimp-3.0.2 devel-docs
mv: cannot stat '/builddir/build/BUILDROOT/gimp-3.0.2-1.el9.x86_64/usr/share/doc/gimp-3.0.2': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.1HZv08 (%install) | This is a build error |
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:
[/usr/bin/ld: /usr/lib64/libicui18n.so: undefined reference to `__cxa_call_terminate@CXXABI_1.3.15'
collect2: error: ld returned 1 exit status]: [The linker couldn't find the definition for the symbol __cxa_call_terminate@CXXABI_1.3.15. The error message specifies the version CXXABI_1.3.15. It's possible that your compiler is expecting a specific version of libstdc++ that might not be available on your system.]
| Issue: The RPM build failed because the linker couldn't find the definition for the symbol __cxa_call_terminate@CXXABI_1.3.15. This symbol is part of the C++ exception handling mechanism provided by the standard C++ library (libstdc++).
Resolution: Upgrade C++ Libraries: If possible, update your system's C++ libraries to a version that provides CXXABI_1.3.15 or later.
Specify Library Path: If upgrading isn't an option, try adding the path to the specific libstdc++ library version that your compiler expects to the linker search path. This can be achieved through environment variables like LD_LIBRARY_PATH (for temporary fixes) or linker flags specific to your 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:
/usr/bin/ld: /usr/lib64/libicui18n.so: undefined reference to `__cxa_call_terminate@CXXABI_1.3.15'
collect2: error: ld returned 1 exit status | The linker couldn't find the definition for the symbol __cxa_call_terminate@CXXABI_1.3.15. The error message specifies the version CXXABI_1.3.15. It's possible that your compiler is expecting a specific version of libstdc++ that might not be available on your system. |
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:
[ela/date.c:7:16: error: cannot use keyword ‘false’ as enumeration constant
7 | typedef enum { false, true } bool;
| ^~~~~
ela/date.c:7:16: note: ‘false’ is a keyword with ‘-std=c23’ onwards
ela/date.c:7:30: error: expected ‘;’, identifier or ‘(’ before ‘bool’
7 | typedef enum { false, true } bool;
| ^~~~
ela/date.c:7:30: warning: useless type name in empty declaration]: [the relevant error messages saying that false, true and bool are the keyword and cannot be used in ela/date.c]
| Issue: The build failed because gcc15 which defaults to C23 in which bool, true and false are now keywords
Resolution: Remove the line "typedef enum { false, true } bool;" in ela/date.c and replace it with "#include <stdbool.h>" which includes define for false, true and bool
|
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:
ela/date.c:7:16: error: cannot use keyword ‘false’ as enumeration constant
7 | typedef enum { false, true } bool;
| ^~~~~
ela/date.c:7:16: note: ‘false’ is a keyword with ‘-std=c23’ onwards
ela/date.c:7:30: error: expected ‘;’, identifier or ‘(’ before ‘bool’
7 | typedef enum { false, true } bool;
| ^~~~
ela/date.c:7:30: warning: useless type name in empty declaration | the relevant error messages saying that false, true and bool are the keyword and cannot be used in ela/date.c |
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:
[RPM build errors:
gcore.c: In function âdo_gcoreâ:
gcore.c:309:32: error: too few arguments to function âset_contextâ
309 | (void) set_context(tc->task, NO_PID);
| ^~~~~~~~~~~
In file included from gcore.c:16:
/usr/include/crash/defs.h:6097:5: note: declared here
6097 | int set_context(ulong, ulong, uint);
| ^~~~~~~~~~~
gcore.c:343:23: error: too few arguments to function âset_contextâ
343 | (void)set_context(gcore->orig_task, NO_PID);
| ^~~~~~~~~~~
/usr/include/crash/defs.h:6097:5: note: declared here
6097 | int set_context(ulong, ulong, uint);
| ^~~~~~~~~~~
make: *** [gcore.mk:111: gcore.so] Error 1]: [RPM build error, caused by compilation issue.
Function `do_gcore` has been called with wrong number of arguments.]
| Issue: Code that was compiled for this package contained an error. Function `do_gcore` was called with a wrong number of arguments.
Resolution: Ensure your code compiles into binary, before attempting to build and package it. |
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:
RPM build errors:
gcore.c: In function âdo_gcoreâ:
gcore.c:309:32: error: too few arguments to function âset_contextâ
309 | (void) set_context(tc->task, NO_PID);
| ^~~~~~~~~~~
In file included from gcore.c:16:
/usr/include/crash/defs.h:6097:5: note: declared here
6097 | int set_context(ulong, ulong, uint);
| ^~~~~~~~~~~
gcore.c:343:23: error: too few arguments to function âset_contextâ
343 | (void)set_context(gcore->orig_task, NO_PID);
| ^~~~~~~~~~~
/usr/include/crash/defs.h:6097:5: note: declared here
6097 | int set_context(ulong, ulong, uint);
| ^~~~~~~~~~~
make: *** [gcore.mk:111: gcore.so] Error 1 | RPM build error, caused by compilation issue.
Function `do_gcore` has been called with wrong number of arguments. |
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:
[o/main.c:1475:14: error: ‘bfd_mach_common64’ undeclared (first use in this function); did you mean ‘bfd_mach_msp26’?]: [Undeclared type, most likely caused by building on a different architecture than expected.]
| Issue: The build failed because the bfd_architecture enum from the bfd.h library returns architecture specific results, the bfd_mach_common64 is most likely not declared on the ppc64ie arch.
Resolution: Modify the expected output of the bfd_architecture enum based n the architecture being used for building. |
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:
o/main.c:1475:14: error: ‘bfd_mach_common64’ undeclared (first use in this function); did you mean ‘bfd_mach_msp26’? | Undeclared type, most likely caused by building on a different architecture than expected. |
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:
[LookupError: tox configuration not found. To use tox, please ensure tox configuration is located in current directory (in tox.ini, setup.cfg, pyproject.toml, or tox.toml). See https://tox.wiki/en/latest/config.html for details.]: [Build failure description.]
| Issue: Missing tox configuration.
Resolution: Add or generate tox configuration file to expected location. |
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:
LookupError: tox configuration not found. To use tox, please ensure tox configuration is located in current directory (in tox.ini, setup.cfg, pyproject.toml, or tox.toml). See https://tox.wiki/en/latest/config.html for details. | Build failure description. |
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:
[
file /etc/dnf/dnf.conf from install of libdnf5-5.1.12-1.fc40.x86_64 conflicts with file from package dnf-data-4.19.0-1.fc40.noar]: [It's not possible to install all required packages because there's a file conflict between a newly installed (libdnf5) and an already installed package (dnf-data).]
| Issue: It was not possible to install all the required packages needed for building the package.
Resolution: Resolve the conflict first. |
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:
file /etc/dnf/dnf.conf from install of libdnf5-5.1.12-1.fc40.x86_64 conflicts with file from package dnf-data-4.19.0-1.fc40.noar | It's not possible to install all required packages because there's a file conflict between a newly installed (libdnf5) and an already installed package (dnf-data). |
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:
[=========================== short test summary info ============================
ERROR tests/test_packager_dashboard_bodhi.py - ValueError: The 'OIDC_REQUIRE_...
ERROR tests/test_packager_dashboard_bugzilla.py - ValueError: The 'OIDC_REQUI...
ERROR tests/test_packager_dashboard_health_check.py - ValueError: The 'OIDC_R...
ERROR tests/test_packager_dashboard_helpers.py - ValueError: The 'OIDC_REQUIR...
ERROR tests/test_packager_dashboard_koschei.py - ValueError: The 'OIDC_REQUIR...
ERROR tests/test_packager_dashboard_orphans.py - ValueError: The 'OIDC_REQUIR...
ERROR tests/test_packager_dashboard_pagure.py - ValueError: The 'OIDC_REQUIRE...
!!!!!!!!!!!!!!!!!!! Interrupted: 7 errors during collection !!!!!!!!!!!!!!!!!!!!
======================== 2 warnings, 7 errors in 1.97s =========================
py312: exit 2 (2.40 seconds) /builddir/build/BUILD/oraculum-0.2.4> pytest pid=749
py312: FAIL code 2 (2.40 seconds)
evaluation failed :( (2.46 seconds]: [Pytest test cases that failed.]
| Issue: The error message indicates that there were seven errors encountered during the execution of the pytest test suite for the Oracleum project. These errors occurred in seven different test files:
- tests/test_packager_dashboard_bodhi.py
- tests/test_packager_dashboard_bugzilla.py
- tests/test_packager_dashboard_health_check.py
- tests/test_packager_dashboard_helpers.py
- tests/test_packager_dashboard_koschei.py
- tests/test_packager_dashboard_orphans.py
- tests/test_packager_dashboard_pagure.py
Each of these errors is specifically related to a ValueError being raised during the execution of the test. The ValueError indicates that there is an issue with the OIDC_REQUIRE_SCOPES environment variable.
As a result of these errors, the entire test suite was interrupted and failed. The test runner reported two warnings and seven errors, and the overall exit code was 2.
Resolution: To fix this issue, you will need to investigate the cause of the ValueErrors and ensure that the OIDC_REQUIRE_SCOPES environment variable is set correctly for each of the tests. The specific steps for fixing this issue will depend on the exact configuration of your testing environment and the code being tested. |
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:
=========================== short test summary info ============================
ERROR tests/test_packager_dashboard_bodhi.py - ValueError: The 'OIDC_REQUIRE_...
ERROR tests/test_packager_dashboard_bugzilla.py - ValueError: The 'OIDC_REQUI...
ERROR tests/test_packager_dashboard_health_check.py - ValueError: The 'OIDC_R...
ERROR tests/test_packager_dashboard_helpers.py - ValueError: The 'OIDC_REQUIR...
ERROR tests/test_packager_dashboard_koschei.py - ValueError: The 'OIDC_REQUIR...
ERROR tests/test_packager_dashboard_orphans.py - ValueError: The 'OIDC_REQUIR...
ERROR tests/test_packager_dashboard_pagure.py - ValueError: The 'OIDC_REQUIRE...
!!!!!!!!!!!!!!!!!!! Interrupted: 7 errors during collection !!!!!!!!!!!!!!!!!!!!
======================== 2 warnings, 7 errors in 1.97s =========================
py312: exit 2 (2.40 seconds) /builddir/build/BUILD/oraculum-0.2.4> pytest pid=749
py312: FAIL code 2 (2.40 seconds)
evaluation failed :( (2.46 seconds | Pytest test cases that 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:
[collect2: error: ld returned 1 exit status]: [Error that caused the build to fail]
=============
[/usr/bin/ld: failed to set dynamic section sizes: bad value
]: [Explanation how the 'ld' failed]
=============
[/usr/bin/ld: /tmp/ccYmXGlK.ltrans127.ltrans.o: relocation R_X86_64_TPOFF32 against `_ZN5tpoolL15tls_worker_dataE' can not be used when making a shared object; recompile with -fPIC
]: [Suggested solution: recompile with -fPIC]
| Issue: A binary requires to be compiled with '-fPIC' compilation flag, but it is missing.
Resolution: Make sure the compilation flag is propagated correctly through the build process. |
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:
collect2: error: ld returned 1 exit status | Error that caused the build to fail |
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/ld: failed to set dynamic section sizes: bad value
| Explanation how the 'ld' 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:
/usr/bin/ld: /tmp/ccYmXGlK.ltrans127.ltrans.o: relocation R_X86_64_TPOFF32 against `_ZN5tpoolL15tls_worker_dataE' can not be used when making a shared object; recompile with -fPIC
| Suggested solution: recompile with -fPIC |
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 generating index.html: No such file or directory @ rb_sysopen - /usr/share/gems/gems/rdoc-6.8.0/lib/rdoc/generator/template/darkfish/_sidebar_toggle.rhtml (RDoc::Error)
]: [The core issue seems to be a missing file: /usr/share/gems/gems/rdoc-6.8.0/lib/rdoc/generator/template/darkfish/_sidebar_toggle.rhtml. This file is a template used by RDoc to generate the sidebar toggle element in the documentation.]
| Issue: The error message you've provided indicates a problem with the RDoc gem, a tool used for generating documentation for Ruby projects. Specifically, it's failing to generate the index.html file, which is a crucial part of the documentation.
Resolution: Check for RDoc Bugs: Search online forums or issue trackers for similar problems and potential solutions.
Check if sources contain that file and try to track it down. |
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 generating index.html: No such file or directory @ rb_sysopen - /usr/share/gems/gems/rdoc-6.8.0/lib/rdoc/generator/template/darkfish/_sidebar_toggle.rhtml (RDoc::Error)
| The core issue seems to be a missing file: /usr/share/gems/gems/rdoc-6.8.0/lib/rdoc/generator/template/darkfish/_sidebar_toggle.rhtml. This file is a template used by RDoc to generate the sidebar toggle element in the documentation. |
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:
[ !! Copr timeout => sending INT]: [Copr build timeouted, and the build interrupted by SIGINT.]
=============
[ 'timeout': 18000,]: [The build timeout is set to 18000 secons.]
| Issue: The build was still running when the timeout left, so the build has been terminated.
Resolution: Prolong the timeout to a reasonable value, or request powerful builders https://docs.pagure.org/copr.copr/user_documentation/powerful_builders.html so the build can finish faster. |
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:
!! Copr timeout => sending INT | Copr build timeouted, and the build interrupted by SIGINT. |
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:
'timeout': 18000, | The build timeout is set to 18000 secons. |
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:
[/builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:65:84: error: âlibdnf5::OptionNumber<unsigned int>& libdnf5::ConfigMain::get_retries_option()â is deprecated: The option does nothing [-Werror=deprecated-declarations]
65 | OptionChild<OptionNumber<std::uint32_t>> retries{main_config.get_retries_option()};
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
In file included from /builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/repo/config_repo.hpp:23,
from /builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:20:
/builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/conf/config_main.hpp:228:77: note: declared here
228 | [[deprecated("The option does nothing")]] OptionNumber<std::uint32_t> & get_retries_option();
| ^~~~~~~~~~~~~~~~~~
/builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:84:69: error: âlibdnf5::OptionBool& libdnf5::ConfigMain::get_deltarpm_option()â is deprecated: The option does nothing [-Werror=deprecated-declarations]
84 | OptionChild<OptionBool> deltarpm{main_config.get_deltarpm_option()};
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/conf/config_main.hpp:306:60: note: declared here
306 | [[deprecated("The option does nothing")]] OptionBool & get_deltarpm_option();
| ^~~~~~~~~~~~~~~~~~~
/builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:85:108: error: âlibdnf5::OptionNumber<unsigned int>& libdnf5::ConfigMain::get_deltarpm_percentage_option()â is deprecated: The option does nothing [-Werror=deprecated-declarations]
85 | OptionChild<OptionNumber<std::uint32_t>> deltarpm_percentage{main_config.get_deltarpm_percentage_option()};
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/conf/config_main.hpp:310:77: note: declared here
310 | [[deprecated("The option does nothing")]] OptionNumber<std::uint32_t> & get_deltarpm_percentage_option();
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~]: [It shows methods that are deprecated which produces errors.]
=============
[cc1plus: all warnings being treated as errors]: [The deprecated warnings could normally be ignored but since the build is configured to treat all warnings as errors it fails.]
| Issue: Couple methods started to be deprecated which produces warnings and since the build is configured to treat all warnings as errors it fails.
Resolution: There are several possibilities:
- stop using the deprecated methods
- don't treat all warnings as errors which would allow to ignore them for now
- disable the warnings with something like:
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
call_deprecated();
#pragma GCC diagnostic pop |
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:
/builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:65:84: error: âlibdnf5::OptionNumber<unsigned int>& libdnf5::ConfigMain::get_retries_option()â is deprecated: The option does nothing [-Werror=deprecated-declarations]
65 | OptionChild<OptionNumber<std::uint32_t>> retries{main_config.get_retries_option()};
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
In file included from /builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/repo/config_repo.hpp:23,
from /builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:20:
/builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/conf/config_main.hpp:228:77: note: declared here
228 | [[deprecated("The option does nothing")]] OptionNumber<std::uint32_t> & get_retries_option();
| ^~~~~~~~~~~~~~~~~~
/builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:84:69: error: âlibdnf5::OptionBool& libdnf5::ConfigMain::get_deltarpm_option()â is deprecated: The option does nothing [-Werror=deprecated-declarations]
84 | OptionChild<OptionBool> deltarpm{main_config.get_deltarpm_option()};
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/conf/config_main.hpp:306:60: note: declared here
306 | [[deprecated("The option does nothing")]] OptionBool & get_deltarpm_option();
| ^~~~~~~~~~~~~~~~~~~
/builddir/build/BUILD/dnf5-5.2.13.0/libdnf5/repo/config_repo.cpp:85:108: error: âlibdnf5::OptionNumber<unsigned int>& libdnf5::ConfigMain::get_deltarpm_percentage_option()â is deprecated: The option does nothing [-Werror=deprecated-declarations]
85 | OptionChild<OptionNumber<std::uint32_t>> deltarpm_percentage{main_config.get_deltarpm_percentage_option()};
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/builddir/build/BUILD/dnf5-5.2.13.0/include/libdnf5/conf/config_main.hpp:310:77: note: declared here
310 | [[deprecated("The option does nothing")]] OptionNumber<std::uint32_t> & get_deltarpm_percentage_option();
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | It shows methods that are deprecated which produces errors. |
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:
cc1plus: all warnings being treated as errors | The deprecated warnings could normally be ignored but since the build is configured to treat all warnings as errors it fails. |
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:
[stdout: Downloading emacs-29.4.tar.xz from fejfighter/emacs-rpm at github.com:
]: [The tarball emacs-29.4.tar.xz should be downloaded from fejfighter/emacs-rpm at github.com.]
=============
[Removed downloaded invalid file /var/lib/copr-rpmbuild/workspace/workdir-8fqckqg4/emacs-rpm/emacs-29.4.tar.xz
Server returned status code 404.]: [Requested file can't be downloaded. Server returns 404 error (Not Found).]
| Issue: The requested tarball can't be downloaded from the github.com. The file is missing.
Resolution: Please verify your tarball source link is correct. |
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:
stdout: Downloading emacs-29.4.tar.xz from fejfighter/emacs-rpm at github.com:
| The tarball emacs-29.4.tar.xz should be downloaded from fejfighter/emacs-rpm at github.com. |
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:
Removed downloaded invalid file /var/lib/copr-rpmbuild/workspace/workdir-8fqckqg4/emacs-rpm/emacs-29.4.tar.xz
Server returned status code 404. | Requested file can't be downloaded. Server returns 404 error (Not Found). |
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:
[Traceback (most recent call last):
File "/usr/lib/rpm/redhat/pyproject_buildrequires.py", line 560, in main
generate_requires(
File "/usr/lib/rpm/redhat/pyproject_buildrequires.py", line 456, in generate_requires
generate_build_requirements(backend, requirements)
File "/usr/lib/rpm/redhat/pyproject_buildrequires.py", line 274, in generate_build_requirements
new_reqs = get_requires(config_settings=requirements.config_settings)
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=['wheel'])
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
self.run_setup()
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 480, in run_setup
super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 311, in run_setup
exec(code, locals())
File "<string>", line 12, in <module>
ModuleNotFoundError: No module named 'pandas'
error: Bad exit status from /var/tmp/rpm-tmp.MVFH9P (%generate_buildrequires)
Bad exit status from /var/tmp/rpm-tmp.MVFH9P (%generate_buildrequires)
]: [Traceback from the build process. Imported module `pandas` was not found. ]
| Issue: Module `pandas`, which is imported by the code used during the package build, is not present.
Resolution: Before the build begins, make sure that all required modules and other dependencies, are properly specified in the package 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:
Traceback (most recent call last):
File "/usr/lib/rpm/redhat/pyproject_buildrequires.py", line 560, in main
generate_requires(
File "/usr/lib/rpm/redhat/pyproject_buildrequires.py", line 456, in generate_requires
generate_build_requirements(backend, requirements)
File "/usr/lib/rpm/redhat/pyproject_buildrequires.py", line 274, in generate_build_requirements
new_reqs = get_requires(config_settings=requirements.config_settings)
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=['wheel'])
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
self.run_setup()
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 480, in run_setup
super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
File "/usr/lib/python3.9/site-packages/setuptools/build_meta.py", line 311, in run_setup
exec(code, locals())
File "<string>", line 12, in <module>
ModuleNotFoundError: No module named 'pandas'
error: Bad exit status from /var/tmp/rpm-tmp.MVFH9P (%generate_buildrequires)
Bad exit status from /var/tmp/rpm-tmp.MVFH9P (%generate_buildrequires)
| Traceback from the build process. Imported module `pandas` was not found. |
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:
[Copr build error: Build failed]: [Message indicating general build failure.]
=============
[Problem: cannot install the best candidate for the job
- nothing provides clang = 13.0.0 needed by clang-rpm-macros-1-136.el115.noarch from https_download_copr_fedorainfracloud_org_results_fedora_llvm_team_clang_rpm_macros_fedora_releasever_basearch
]: [Required package `clang = 13.0.0` is not available in any of the provided repositories.]
| Issue: One of the dependencies was unmet.
Resolution: Ensure that all dependencies are available from installed repos. |
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:
Copr build error: Build failed | Message indicating general build failure. |
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:
Problem: cannot install the best candidate for the job
- nothing provides clang = 13.0.0 needed by clang-rpm-macros-1-136.el115.noarch from https_download_copr_fedorainfracloud_org_results_fedora_llvm_team_clang_rpm_macros_fedora_releasever_basearch
| Required package `clang = 13.0.0` is not available in any of the provided repositories. |
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:
[../src/backlight/backlight.c: In function âread_brightnessâ:
../src/backlight/backlight.c:389:21: error: unused variable âsubsystemâ [-Werror=unused-variable]
389 | const char *subsystem, *value;
| ^~~~~~~~~]: [Build failed during compilation of src/backlight/backlight.c
There is an unused variable `subsystem`]
| Issue: Compiler detected unused variable
Resolution: Check if unused variables are needed or not. If yes, then use them; otherwise, remove them. |
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:
../src/backlight/backlight.c: In function âread_brightnessâ:
../src/backlight/backlight.c:389:21: error: unused variable âsubsystemâ [-Werror=unused-variable]
389 | const char *subsystem, *value;
| ^~~~~~~~~ | Build failed during compilation of src/backlight/backlight.c
There is an unused variable `subsystem` |
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:
[go: cloud.google.com/go/auth in vendor/modules.txt requires go >= 1.23.0 (running go 1.22.12; GOTOOLCHAIN=local)
error: Bad exit status from /var/tmp/rpm-tmp.u6YRtS (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.u6YRtS (%build)
Child return code was: 1
EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M e324a6a632c340e4b2e4e04c278543ea -D /var/lib/mock/f40-build-58054473-6561875/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.rmyqzvho:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin \'--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"\' \'--setenv=PS1=<mock-chroot> \\s-\\v\\$ \' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c \'/usr/bin/rpmbuild -bb --noclean --target x86_64 --nodeps /builddir/build/SPECS/ignition.spec\'\n', 1)]
Traceback (most recent call last):
File "/usr/lib/python3.13/site-packages/mockbuild/trace_decorator.py", line 93, in trace
result = func(*args, **kw)
File "/usr/lib/python3.13/site-packages/mockbuild/util.py", line 610, in do_with_status
raise exception.Error("Command failed: \n # %s\n%s" % (cmd_pretty(command, env), output), child.returncode)
mockbuild.exception.Error: Command failed:
# /usr/bin/systemd-nspawn -q -M e324a6a632c340e4b2e4e04c278543ea -D /var/lib/mock/f40-build-58054473-6561875/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.rmyqzvho:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --noclean --target x86_64 --nodeps /builddir/build/SPECS/ignition.spec'
]: [It shows the failure]
| Issue: It looks like systemd-nspawn failed
Resolution: Retry the build |
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:
go: cloud.google.com/go/auth in vendor/modules.txt requires go >= 1.23.0 (running go 1.22.12; GOTOOLCHAIN=local)
error: Bad exit status from /var/tmp/rpm-tmp.u6YRtS (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.u6YRtS (%build)
Child return code was: 1
EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M e324a6a632c340e4b2e4e04c278543ea -D /var/lib/mock/f40-build-58054473-6561875/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.rmyqzvho:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin \'--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"\' \'--setenv=PS1=<mock-chroot> \\s-\\v\\$ \' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c \'/usr/bin/rpmbuild -bb --noclean --target x86_64 --nodeps /builddir/build/SPECS/ignition.spec\'\n', 1)]
Traceback (most recent call last):
File "/usr/lib/python3.13/site-packages/mockbuild/trace_decorator.py", line 93, in trace
result = func(*args, **kw)
File "/usr/lib/python3.13/site-packages/mockbuild/util.py", line 610, in do_with_status
raise exception.Error("Command failed: \n # %s\n%s" % (cmd_pretty(command, env), output), child.returncode)
mockbuild.exception.Error: Command failed:
# /usr/bin/systemd-nspawn -q -M e324a6a632c340e4b2e4e04c278543ea -D /var/lib/mock/f40-build-58054473-6561875/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.rmyqzvho:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --noclean --target x86_64 --nodeps /builddir/build/SPECS/ignition.spec'
| It shows the failure |
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:
[
AttributeError: module 'importlib.resources' has no attribute 'content]: [It contains the exact Python error which has occurred with the package build.]
| Issue: Many importlib.resources methods have been removed from Python 3.13. importlib.resources.contents() is one of them.
Resolution: The upstream code has to be ported to the supported importlib.resources.files() API. |
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:
AttributeError: module 'importlib.resources' has no attribute 'content | It contains the exact Python error which has occurred with the package build. |
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: Installed (but unpackaged) file(s) found:
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313d-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313t-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313td-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313d-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313t-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313td-x86_64-linux-gnu.so]: [There are installed but unpackaged files. This makes the build fail.]
| Issue: New installed files were added upstream, but the %files section did not list them.
Resolution: List newly added files in the %files 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:
error: Installed (but unpackaged) file(s) found:
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313d-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313t-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testexternalinspection.cpython-313td-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313d-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313t-x86_64-linux-gnu.so
/usr/lib64/python3.13/lib-dynload/_testlimitedcapi.cpython-313td-x86_64-linux-gnu.so | There are installed but unpackaged files. This makes the build 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:
[Ran 73 tests in 13.327s
FAILED (errors=1, skipped=5)]: [It is a reason why build failed.]
=============
[error: Bad exit status from /var/tmp/rpm-tmp.Vd92jf (%check)]: [It points out that the error happened in a %check section of a spec file.]
| Issue: Build failed because tests in %check section failed.
Resolution: Fix the tests so checks in %check secion can pass and build can continue. |
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:
Ran 73 tests in 13.327s
FAILED (errors=1, skipped=5) | It is a reason why build 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.Vd92jf (%check) | It points out that the error happened in a %check section of a spec file. |
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:
[/home/abuild/rpmbuild/BUILD/opencv-qt6-4.11.0-build/opencv-4.11.0/modules/dnn/include/opencv2/dnn/dnn.inl.hpp:377:21,]: [This snippet suggests strong evidence that the build failure used in the openSUSE Build Service (OBS) for building RPM packages]
=============
[[ 452s] /home/abuild/rpmbuild/BUILD/opencv-qt6-4.11.0-build/opencv-4.11.0/modules/core/include/opencv2/core/utility.hpp:1096:15: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=]
[ 452s] 1096 | ptr = new _Tp[_size];]: [This snippet, repeated multiple times but originating from this specific location (and similar ones in other DNN-related files), highlights the core issue. It shows a warning at a specific line (utility.hpp:1096) where a new allocation is being attempted with an extremely large size. The -Walloc-size-larger-than= flag clearly indicates the nature of the problem. This tells a developer to look at the code leading up to this allocation in opencv2/core/utility.hpp and the calling functions within the DNN module (like caffe_importer.cpp, onnx_importer.cpp, etc.) to understand why such a large size is being requested.]
| Issue: we find that the build failure is due to the OpenCV DNN module attempting to allocate extremely large memory blocks, as indicated by the numerous -Walloc-size-larger-than= warnings. Although reported as warnings, these caused a critical error during the build process, leading to the make command exiting with an error code.
Resolution: To fix this, we would need to investigate the parts of the OpenCV DNN code where these large allocations are being attempted. The logic would need to be handled.
|
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:
/home/abuild/rpmbuild/BUILD/opencv-qt6-4.11.0-build/opencv-4.11.0/modules/dnn/include/opencv2/dnn/dnn.inl.hpp:377:21, | This snippet suggests strong evidence that the build failure used in the openSUSE Build Service (OBS) for building RPM packages |
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:
[ 452s] /home/abuild/rpmbuild/BUILD/opencv-qt6-4.11.0-build/opencv-4.11.0/modules/core/include/opencv2/core/utility.hpp:1096:15: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=]
[ 452s] 1096 | ptr = new _Tp[_size]; | This snippet, repeated multiple times but originating from this specific location (and similar ones in other DNN-related files), highlights the core issue. It shows a warning at a specific line (utility.hpp:1096) where a new allocation is being attempted with an extremely large size. The -Walloc-size-larger-than= flag clearly indicates the nature of the problem. This tells a developer to look at the code leading up to this allocation in opencv2/core/utility.hpp and the calling functions within the DNN module (like caffe_importer.cpp, onnx_importer.cpp, etc.) to understand why such a large size is being requested. |
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: Bad file: /var/lib/copr-rpmbuild/workspace/workdir-1r884s0e/python-APScheduler/apscheduler-3.10.4.tar.gz: No such file or directory]: [Build error indicating that `/var/lib/copr-rpmbuild/workspace/workdir-1r884s0e/python-APScheduler/apscheduler-3.10.4.tar.gz`is not present.]
=============
[RPM build errors:]: [Start of build error report.]
=============
[Traceback (most recent call last):
File "/usr/bin/dist-git-client", line 10, in <module>
main()
~~~~^^
File "/usr/lib/python3.13/site-packages/dist_git_client.py", line 494, in main
srpm(args, config)
~~~~^^^^^^^^^^^^^^
File "/usr/lib/python3.13/site-packages/dist_git_client.py", line 348, in srpm
check_call(command)
~~~~~~~~~~^^^^^^^^^
File "/usr/lib/python3.13/site-packages/dist_git_client.py", line 50, in check_call
subprocess.check_call(cmd)
~~~~~~~~~~~~~~~~~~~~~^^^^^
File "/usr/lib64/python3.13/subprocess.py", line 419, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['rpmbuild', '-bs', '/var/lib/copr-rpmbuild/results/python-APScheduler.spec', '--define', 'dist %nil', '--define', '_sourcedir /var/lib/copr-rpmbuild/workspace/workdir-1r884s0e/python-APScheduler/.', '--define', '_srcrpmdir /var/lib/copr-rpmbuild/results', '--define', '_disable_source_fetch 1']' returned non-zero exit status 1.
]: [RPM build traceback, caused by the detected error but irrelevant for diagnosis.]
| Issue: File, specifically an archive `/var/lib/copr-rpmbuild/workspace/workdir-1r884s0e/python-APScheduler/apscheduler-3.10.4.tar.gz` was missing.
Resolution: Ensure that all required files are present in an appropriate location before build starts. |
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 file: /var/lib/copr-rpmbuild/workspace/workdir-1r884s0e/python-APScheduler/apscheduler-3.10.4.tar.gz: No such file or directory | Build error indicating that `/var/lib/copr-rpmbuild/workspace/workdir-1r884s0e/python-APScheduler/apscheduler-3.10.4.tar.gz`is not present. |
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:
RPM build errors: | Start of build error report. |
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:
Traceback (most recent call last):
File "/usr/bin/dist-git-client", line 10, in <module>
main()
~~~~^^
File "/usr/lib/python3.13/site-packages/dist_git_client.py", line 494, in main
srpm(args, config)
~~~~^^^^^^^^^^^^^^
File "/usr/lib/python3.13/site-packages/dist_git_client.py", line 348, in srpm
check_call(command)
~~~~~~~~~~^^^^^^^^^
File "/usr/lib/python3.13/site-packages/dist_git_client.py", line 50, in check_call
subprocess.check_call(cmd)
~~~~~~~~~~~~~~~~~~~~~^^^^^
File "/usr/lib64/python3.13/subprocess.py", line 419, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['rpmbuild', '-bs', '/var/lib/copr-rpmbuild/results/python-APScheduler.spec', '--define', 'dist %nil', '--define', '_sourcedir /var/lib/copr-rpmbuild/workspace/workdir-1r884s0e/python-APScheduler/.', '--define', '_srcrpmdir /var/lib/copr-rpmbuild/results', '--define', '_disable_source_fetch 1']' returned non-zero exit status 1.
| RPM build traceback, caused by the detected error but irrelevant for diagnosis. |
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 to resolve the transaction:
Package "coreutils-9.5-1.eln136.x86_64" is already installed.
Package "findutils-1:4.9.0-8.eln134.x86_64" is already installed.
No match for argument: nodejs-npm
Package "tar-2:1.35-3.eln134.x86_64" is already installed.
Package "util-linux-2.40.1-1.eln136.x86_64" is already installed.
You can try to add to command line:
--skip-unavailable to skip unavailable packages]: [It shows which packages are available and which ones arent.]
| Issue: Package nodejs-npm can not be installed.
Resolution: Find the correct package name and add it as a build dependency. |
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 to resolve the transaction:
Package "coreutils-9.5-1.eln136.x86_64" is already installed.
Package "findutils-1:4.9.0-8.eln134.x86_64" is already installed.
No match for argument: nodejs-npm
Package "tar-2:1.35-3.eln134.x86_64" is already installed.
Package "util-linux-2.40.1-1.eln136.x86_64" is already installed.
You can try to add to command line:
--skip-unavailable to skip unavailable packages | It shows which packages are available and which ones arent. |
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:
[
Package "python3-pip-23.2.1-1.fc40.noarch" is already installed.
Problem: package python3-pip-23.3.1-2.fc40.noarch conflicts with python-pip < 23.3.1-2.fc40 provided by python3-pip-23.2.1-1.fc40.noarch
- cannot install both python3-pip-23.2.1-1.fc40.noarch and python3-pip-23.3.1-2.fc40.noarch
- cannot install the best candidate for the j]: [It describes the conflicting versions of package needed. The being-built python-pipdeptree requires python3-pip-23.3.1-2.fc40.noarch but in the repository there is available a lower version, python3-pip-23.2.1-1.fc40.noarch]
=============
[
Requirement satisfied: pip >= 19
(installed: pip 23.2.]: [This part says which version of python3-pip has been installed into the buildroot. ]
=============
[ python3-pip noarch 23.2.1-1.fc40 copr_base 14.0 M]: [It says which python3-pip has been installed: version 23.2.1-1.fc40 which has been built in the given copr repository]
=============
[
Handling pip>=23.3.1; extra == 'test' from built wheel metadata: Requires-Dist (pipdeptre]: [It contains the requirements read from the built wheel metadata, including the version constraint - pip's version has to be greater or equal 23.3.1]
| Issue: There is a dependency version conflict that is impossible to resolve. python3-pip version (equal or greater than 23.3.1), required by python-pipdeptree, is not available in the copr repository.
Resolution: Build the required version of python3-pip in the same copr. Then retrigger a new build of python-pipdeptree. |
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:
Package "python3-pip-23.2.1-1.fc40.noarch" is already installed.
Problem: package python3-pip-23.3.1-2.fc40.noarch conflicts with python-pip < 23.3.1-2.fc40 provided by python3-pip-23.2.1-1.fc40.noarch
- cannot install both python3-pip-23.2.1-1.fc40.noarch and python3-pip-23.3.1-2.fc40.noarch
- cannot install the best candidate for the j | It describes the conflicting versions of package needed. The being-built python-pipdeptree requires python3-pip-23.3.1-2.fc40.noarch but in the repository there is available a lower version, python3-pip-23.2.1-1.fc40.noarch |
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:
Requirement satisfied: pip >= 19
(installed: pip 23.2. | This part says which version of python3-pip has been installed into the buildroot. |
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:
python3-pip noarch 23.2.1-1.fc40 copr_base 14.0 M | It says which python3-pip has been installed: version 23.2.1-1.fc40 which has been built in the given copr repository |
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:
Handling pip>=23.3.1; extra == 'test' from built wheel metadata: Requires-Dist (pipdeptre | It contains the requirements read from the built wheel metadata, including the version constraint - pip's version has to be greater or equal 23.3.1 |
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:
[Copr build error: Build failed]: [Build failure message.]
=============
[
Copr repository 3.4 kB/s | 257 B 00:00
Additional repo copr_freeipa_freeipa_master_fed 5.3 kB/s | 341 B 00:00
Errors during downloading metadata for repository 'copr_freeipa_freeipa_master_fedora_releasever_basearch':
- Status code: 404 for https://download.copr.fedorainfracloud.org/results/@freeipa/freeipa-master/fedora-38-aarch64/repodata/repomd.xml (IP: 108.138.85.53)
Error: Failed to download m]: [Final, unsuccessful attempt to download repository metadata.]
=============
[
This system is not registered with an entitlement server. You can use subscription-manager to registe]: [Server isn't enrolled in Red Hat subscription. ]
=============
[[2024-01-30 06:54:14,752][ ERROR][PID:3785726] Backend process error: No success file => build failur]: [Build was declared as failed, since there is no success file. ]
| Issue: Package repository was not available.
Resolution: Ensure that all repositories used by package manager are available before build. |
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:
Copr build error: Build failed | Build failure message. |
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:
Copr repository 3.4 kB/s | 257 B 00:00
Additional repo copr_freeipa_freeipa_master_fed 5.3 kB/s | 341 B 00:00
Errors during downloading metadata for repository 'copr_freeipa_freeipa_master_fedora_releasever_basearch':
- Status code: 404 for https://download.copr.fedorainfracloud.org/results/@freeipa/freeipa-master/fedora-38-aarch64/repodata/repomd.xml (IP: 108.138.85.53)
Error: Failed to download m | Final, unsuccessful attempt to download repository metadata. |
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:
This system is not registered with an entitlement server. You can use subscription-manager to registe | Server isn't enrolled in Red Hat subscription. |
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:
[2024-01-30 06:54:14,752][ ERROR][PID:3785726] Backend process error: No success file => build failur | Build was declared as failed, since there is no success file. |
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:
[+ go build -buildmode pie -compiler gc '-tags=rpm_crashtraceback ' -a -v -x -ldflags '-X github.com/containers/podman/v5/libpod/define.buildInfo=1745452800 -X "github.com/containers/podman/v5/libpod/define.buildOrigin=Fedora Project" -X github.com/containers/podman/v5/libpod/config._installPrefix=/usr -X github.com/containers/podman/v5/libpod/config._etcDir=/etc -X github.com/containers/podman/v5/pkg/systemd/quadlet._binDir=/usr/bin -X github.com/containers/podman/v5/libpod/define.gitCommit=6a597e0e89b0c597b9a5d8ac6b0f7ce66fb1fa14 -B 0xfbcfac1ea82693bdcce2ec673a38fe53dcbb7938 -compressdwarf=false -linkmode=external -extldflags '\''-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '\''' -o bin/rootlessport ./cmd/rootlessport
WORK=/tmp/go-build3800764424
go: go.mod requires go >= 1.23.3 (running go 1.23.1; GOTOOLCHAIN=local)
error: Bad exit status from /var/tmp/rpm-tmp.RU20jy (%build)
Bad exit status from /var/tmp/rpm-tmp.RU20jy (%build)
RPM build errors:
Child return code was: 1]: [This is the build error]
| Issue: The code in Go requires golang of version at least 1.23.3, but there's golang 1.23.1 installed in the build root.
Resolution: Update the build environment so there's golang 1.23.3 or higher. Also, podman has unversioned golang BuildRequire. It should be changed to golang >= 1.23.3 |
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:
+ go build -buildmode pie -compiler gc '-tags=rpm_crashtraceback ' -a -v -x -ldflags '-X github.com/containers/podman/v5/libpod/define.buildInfo=1745452800 -X "github.com/containers/podman/v5/libpod/define.buildOrigin=Fedora Project" -X github.com/containers/podman/v5/libpod/config._installPrefix=/usr -X github.com/containers/podman/v5/libpod/config._etcDir=/etc -X github.com/containers/podman/v5/pkg/systemd/quadlet._binDir=/usr/bin -X github.com/containers/podman/v5/libpod/define.gitCommit=6a597e0e89b0c597b9a5d8ac6b0f7ce66fb1fa14 -B 0xfbcfac1ea82693bdcce2ec673a38fe53dcbb7938 -compressdwarf=false -linkmode=external -extldflags '\''-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '\''' -o bin/rootlessport ./cmd/rootlessport
WORK=/tmp/go-build3800764424
go: go.mod requires go >= 1.23.3 (running go 1.23.1; GOTOOLCHAIN=local)
error: Bad exit status from /var/tmp/rpm-tmp.RU20jy (%build)
Bad exit status from /var/tmp/rpm-tmp.RU20jy (%build)
RPM build errors:
Child return code was: 1 | This is the build error |
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:
[/var/tmp/rpm-tmp.XzD92k: line 46: autoreconf: command not found
error: Bad exit status from /var/tmp/rpm-tmp.XzD92k (%build)
Bad exit status from /var/tmp/rpm-tmp.XzD92k (%build)
RPM build errors:
Child return code was: 1]: [Indication of missing autoreconf.]
| Issue: There was a missing command "autoreconf", which is needed for frr compilation.
Resolution: Check the specfile; if autoreconf is not added as BuildRequires, add it. |
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:
/var/tmp/rpm-tmp.XzD92k: line 46: autoreconf: command not found
error: Bad exit status from /var/tmp/rpm-tmp.XzD92k (%build)
Bad exit status from /var/tmp/rpm-tmp.XzD92k (%build)
RPM build errors:
Child return code was: 1 | Indication of missing autoreconf. |
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:
[copypass.c: In function ‘process_copy_pass’:
copypass.c:104:12: error: too many arguments to function ‘xstat’; expected 0, have 2
104 | if ((*xstat) (input_name.ds_string, &in_file_stat) < 0)]: [The relevant error messages saying that there are too many arguments passed to function ‘xstat’ ]
| Issue: This code just built fine with gcc 14 and older but failed to build with gcc 15 which is defaulting to -std=gnu23 and due to the gcc bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118112
Resolution: The fix for gcc bug is still in progress. Adding -std=gnu17 to CFLAGS is a workaround for the build failure. |
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:
copypass.c: In function ‘process_copy_pass’:
copypass.c:104:12: error: too many arguments to function ‘xstat’; expected 0, have 2
104 | if ((*xstat) (input_name.ds_string, &in_file_stat) < 0) | The relevant error messages saying that there are too many arguments passed to function ‘xstat’ |
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:
[aff.c:17:13: error: 'bool' cannot be defined via 'typedef'
17 | typedef int bool;
| ^~~~
aff.c:17:13: note: 'bool' is a keyword with '-std=c23' onwards
aff.c:17:1: warning: useless type name in empty declaration
17 | typedef int bool;
| ^~~~~~~]: [The typedef of bool failed because gcc recognises it as a keyword as of std c23.]
| Issue: As of the c23 standard and upwards bool is a keyword and connot be defined using typedef.
Resolution: Rename the typedef to something else that does not match a keyword or use the predefined bool if you are using the c23 standard or newer to compile this code. |
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:
aff.c:17:13: error: 'bool' cannot be defined via 'typedef'
17 | typedef int bool;
| ^~~~
aff.c:17:13: note: 'bool' is a keyword with '-std=c23' onwards
aff.c:17:1: warning: useless type name in empty declaration
17 | typedef int bool;
| ^~~~~~~ | The typedef of bool failed because gcc recognises it as a keyword as of std c23. |
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: 'libselinux-devel >= 3.6-1'
No matching package to install: 'libsepol-devel >= 3.6-1'
Not all dependencies satisfied
Error: Some packages could not be foun]: [These are missing dependencies. The package with this version can't be built without them.]
| Issue: There are missing dependencies.
Resolution: Add libsepol-devel >= 3.6-1 and libselinux-devel >= 3.6-1 the the buildroot. |
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: 'libselinux-devel >= 3.6-1'
No matching package to install: 'libsepol-devel >= 3.6-1'
Not all dependencies satisfied
Error: Some packages could not be foun | These are missing dependencies. The package with this version can't be built without them. |
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 -DHAVE_CONFIG_H -I. -I./h -I h -I /usr/include/tirpc -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=z13 -mtune=z14 -fasynchronous-unwind-tables -fstack-clash-protection -fsigned-char -pipe -fcommon -fno-builtin-malloc -fno-builtin-free -fno-PIE -fno-pie -fno-PIC -fno-pic -std=gnu17 -Wall -Wno-empty-body -Wno-unused-but-set-variable -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -I/usr/include/tirpc -O2 -I o -c -o o/main.o o/main.c
In file included from ./h/include.h:39,
from o/main.c:46:
o/main.c: In function ‘fSdisassemble_instruction’:
o/main.c:1475:14: error: ‘bfd_mach_64_bit’ undeclared (first use in this function); did you mean ‘bfd_mach_x64_32’?
1475 | i.mach=OUTPUT_MACH;
| ^~~~~~~~~~~
o/main.c:1475:14: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [Makefile:1830: o/main.o] Error 1
make[1]: Leaving directory '/builddir/build/BUILD/gcl-2.7.1-build/gcl-2.7.1'
make: *** [Makefile:1044: all] Error 2
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.zcV2dz (%build)
Bad exit status from /var/tmp/rpm-tmp.zcV2dz (%build)]: [gcc complains about an undeclared identifier.]
| Issue: The build failed because gcc encountered an undeclared identifier
Resolution: Check if the identifier is spelled correctly, or include the necessary header. |
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 -DHAVE_CONFIG_H -I. -I./h -I h -I /usr/include/tirpc -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=z13 -mtune=z14 -fasynchronous-unwind-tables -fstack-clash-protection -fsigned-char -pipe -fcommon -fno-builtin-malloc -fno-builtin-free -fno-PIE -fno-pie -fno-PIC -fno-pic -std=gnu17 -Wall -Wno-empty-body -Wno-unused-but-set-variable -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -I/usr/include/tirpc -O2 -I o -c -o o/main.o o/main.c
In file included from ./h/include.h:39,
from o/main.c:46:
o/main.c: In function ‘fSdisassemble_instruction’:
o/main.c:1475:14: error: ‘bfd_mach_64_bit’ undeclared (first use in this function); did you mean ‘bfd_mach_x64_32’?
1475 | i.mach=OUTPUT_MACH;
| ^~~~~~~~~~~
o/main.c:1475:14: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [Makefile:1830: o/main.o] Error 1
make[1]: Leaving directory '/builddir/build/BUILD/gcl-2.7.1-build/gcl-2.7.1'
make: *** [Makefile:1044: all] Error 2
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.zcV2dz (%build)
Bad exit status from /var/tmp/rpm-tmp.zcV2dz (%build) | gcc complains about an undeclared identifier. |
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:
[INFO: Buildroot is handled by package management downloaded with a bootstrap image:
rpm-4.19.1.1-2.eln136.x86_64
rpm-sequoia-1.6.0-2.eln134.x86_64
dnf5-5.2.1.0-1.eln136.x86_64
dnf5-plugins-5.2.1.0-1.eln136.x86_64
Start: installing minimal buildroot with dnf
execv(/usr/bin/dnf-3) failed: No such file or directory
WARNING: DNF command failed, retrying, attempt #2, sleeping 10s
execv(/usr/bin/dnf-3) failed: No such file or directory
WARNING: DNF command failed, retrying, attempt #3, sleeping 10s
execv(/usr/bin/dnf-3) failed: No such file or directory
ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-u763d84x/anaconda/anaconda.spec) Config(fedora-eln-x86_64) 0 minutes 27 seconds]: [Includes the line of the failure and the few lines above which make clear that the issue are related to the dnf version.
]
| Issue: packit it trying to use dnf-3, as it's probably hardcoded somewhere. However the environment has dnf5 installed.
Resolution: Replace the hardcoded dnf-3 command with newer dnf version. |
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:
INFO: Buildroot is handled by package management downloaded with a bootstrap image:
rpm-4.19.1.1-2.eln136.x86_64
rpm-sequoia-1.6.0-2.eln134.x86_64
dnf5-5.2.1.0-1.eln136.x86_64
dnf5-plugins-5.2.1.0-1.eln136.x86_64
Start: installing minimal buildroot with dnf
execv(/usr/bin/dnf-3) failed: No such file or directory
WARNING: DNF command failed, retrying, attempt #2, sleeping 10s
execv(/usr/bin/dnf-3) failed: No such file or directory
WARNING: DNF command failed, retrying, attempt #3, sleeping 10s
execv(/usr/bin/dnf-3) failed: No such file or directory
ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-u763d84x/anaconda/anaconda.spec) Config(fedora-eln-x86_64) 0 minutes 27 seconds | Includes the line of the failure and the few lines above which make clear that the issue are related to the dnf version.
|
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 match for argument: bash-completion-devel]: [This snippet lists the unavailable package.]
| Issue: The build BuildRequires a package that doesn't exist.
Resolution: Update the spec file to list the correct and available build requirements. |
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 match for argument: bash-completion-devel | This snippet lists the unavailable package. |
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: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/fr/man5/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pl/man3/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pt_BR/man5/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/sv/man3/*]: [First block of error reports that mention missing translated manual page files.]
=============
[error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man3/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man5/*]: [Second block of error reports that mention missing translated manual page files.]
=============
[File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/fr/man5/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pl/man3/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pt_BR/man5/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/sv/man3/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/sv/man5/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man3/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man5/*]: [Third block of error reports that mention missing translated manual page files.]
| Issue: The new version of package that we're rebasing to doesn't provide several translated manual page files for some languages. The directories that used to contain the translated manpage files are now empty.
Resolution: In %install section of spec file, all the empty directories need to be removed with 'rm' command from buildroot. |
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: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/fr/man5/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pl/man3/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pt_BR/man5/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/sv/man3/* | First block of error reports that mention missing translated manual page files. |
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: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man3/*
error: File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man5/* | Second block of error reports that mention missing translated manual page files. |
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:
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/fr/man5/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pl/man3/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/pt_BR/man5/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/sv/man3/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/sv/man5/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man3/*
File not found: /builddir/build/BUILD/procps-ng-4.0.5-build/BUILDROOT/usr/share/man/zh_CN/man5/* | Third block of error reports that mention missing translated manual page files. |
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:
[fgrep: warning: fgrep is obsolescent; using grep -F
checking for SHA256_Init in -lcrypto... yes
checking for json_loads in -ljansson... no
configure: error: "library jansson not found"
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.8vVNSV (%build)
Bad exit status from /var/tmp/rpm-tmp.8vVNSV (%build)]: [This snippet show where configure script failed. ]
| Issue: The build failed because configure script could not find jansson library.
Resolution: Add jansson-devel as a build dependency. |
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:
fgrep: warning: fgrep is obsolescent; using grep -F
checking for SHA256_Init in -lcrypto... yes
checking for json_loads in -ljansson... no
configure: error: "library jansson not found"
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.8vVNSV (%build)
Bad exit status from /var/tmp/rpm-tmp.8vVNSV (%build) | This snippet show where configure script 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:
[Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/lib/python3.14/site-packages/tox/__main__.py", line 6, in <module>
run()
~~~^^
File "/usr/lib/python3.14/site-packages/tox/run.py", line 20, in run
result = main(sys.argv[1:] if args is None else args)
File "/usr/lib/python3.14/site-packages/tox/run.py", line 42, in main
result = provision(state)
File "/usr/lib/python3.14/site-packages/tox/provision.py", line 87, in provision
MANAGER.tox_add_core_config(state.conf.core, state)
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/tox/plugin/manager.py", line 81, in tox_add_core_config
self.manager.hook.tox_add_core_config(core_conf=core_conf, state=state)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/pluggy/_hooks.py", line 513, in __call__
return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)
~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/pluggy/_manager.py", line 120, in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 139, in _multicall
raise exception.with_traceback(exception.__traceback__)
File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 103, in _multicall
res = hook_impl.function(*args)
File "/usr/lib/python3.14/site-packages/tox_current_env/hooks4.py", line 82, in tox_add_core_config
raise LookupError(
...<4 lines>...
)
LookupError: tox configuration not found. To use tox, please ensure tox configuration is located in current directory (in tox.ini, setup.cfg, pyproject.toml, or tox.toml). See https://tox.wiki/en/latest/config.html for details.]: [The snippet shows LookupError for missing tox configuration.]
| Issue: The specfile contains %pyproject_buildrequires -t, but there is not tox.ini file in the sources.
Resolution: -t option should be used only when tox.ini file is present. Remove it and try to run the tests differently. |
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:
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/lib/python3.14/site-packages/tox/__main__.py", line 6, in <module>
run()
~~~^^
File "/usr/lib/python3.14/site-packages/tox/run.py", line 20, in run
result = main(sys.argv[1:] if args is None else args)
File "/usr/lib/python3.14/site-packages/tox/run.py", line 42, in main
result = provision(state)
File "/usr/lib/python3.14/site-packages/tox/provision.py", line 87, in provision
MANAGER.tox_add_core_config(state.conf.core, state)
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/tox/plugin/manager.py", line 81, in tox_add_core_config
self.manager.hook.tox_add_core_config(core_conf=core_conf, state=state)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/pluggy/_hooks.py", line 513, in __call__
return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)
~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/pluggy/_manager.py", line 120, in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 139, in _multicall
raise exception.with_traceback(exception.__traceback__)
File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 103, in _multicall
res = hook_impl.function(*args)
File "/usr/lib/python3.14/site-packages/tox_current_env/hooks4.py", line 82, in tox_add_core_config
raise LookupError(
...<4 lines>...
)
LookupError: tox configuration not found. To use tox, please ensure tox configuration is located in current directory (in tox.ini, setup.cfg, pyproject.toml, or tox.toml). See https://tox.wiki/en/latest/config.html for details. | The snippet shows LookupError for missing tox configuration. |
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: backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o
gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o -c ../backend/dvi/mdvi-lib/dviread.c
In file included from /usr/include/kpathsea/debug.h:26,
from ../backend/dvi/mdvi-lib/private.h:35,
from ../backend/dvi/mdvi-lib/dviread.c:30:
/usr/include/kpathsea/c-std.h:48:14: error: conflicting types for ‘getenv’; have ‘char *(void)’
48 | extern char *getenv ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/dviread.c:21:
/usr/include/stdlib.h:773:14: note: previous declaration of ‘getenv’ with type ‘char *(const char *)’
773 | extern char *getenv (const char *__name) __THROW __nonnull ((1)) __wur;
| ^~~~~~
In file included from /usr/include/kpathsea/c-std.h:76:
/usr/include/kpathsea/c-memstr.h:57:14: error: conflicting types for ‘strtok’; have ‘char *(void)’
57 | extern char *strtok ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/dviread.c:23:
/usr/include/string.h:356:14: note: previous declaration of ‘strtok’ with type ‘char *(char * restrict, const char * restrict)’
356 | extern char *strtok (char *__restrict __s, const char *__restrict __delim)
| ^~~~~~
/usr/include/kpathsea/c-memstr.h:59:14: error: conflicting types for ‘strstr’; have ‘char *(void)’
59 | extern char *strstr ();
| ^~~~~~
/usr/include/string.h:350:14: note: previous declaration of ‘strstr’ with type ‘char *(const char *, const char *)’
350 | extern char *strstr (const char *__haystack, const char *__needle)
| ^~~~~~
../backend/dvi/mdvi-lib/dviread.c: In function ‘mdvi_init_context’:
../backend/dvi/mdvi-lib/dviread.c:767:9: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
767 | fread(dvi->fileid, 1, n, p);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
[79/378] gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -c ../backend/dvi/mdvi-lib/font.c
FAILED: backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o
gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -c ../backend/dvi/mdvi-lib/font.c
In file included from /usr/include/kpathsea/debug.h:26,
from ../backend/dvi/mdvi-lib/private.h:35,
from ../backend/dvi/mdvi-lib/font.c:23:
/usr/include/kpathsea/c-std.h:48:14: error: conflicting types for ‘getenv’; have ‘char *(void)’
48 | extern char *getenv ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/font.c:20:
/usr/include/stdlib.h:773:14: note: previous declaration of ‘getenv’ with type ‘char *(const char *)’
773 | extern char *getenv (const char *__name) __THROW __nonnull ((1)) __wur;
| ^~~~~~
In file included from /usr/include/kpathsea/c-std.h:76:
/usr/include/kpathsea/c-memstr.h:57:14: error: conflicting types for ‘strtok’; have ‘char *(void)’
57 | extern char *strtok ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/common.h:28,
from ../backend/dvi/mdvi-lib/mdvi.h:27,
from ../backend/dvi/mdvi-lib/font.c:22:
/usr/include/string.h:356:14: note: previous declaration of ‘strtok’ with type ‘char *(char * restrict, const char * restrict)’
356 | extern char *strtok (char *__restrict __s, const char *__restrict __delim)
| ^~~~~~
/usr/include/kpathsea/c-memstr.h:59:14: error: conflicting types for ‘strstr’; have ‘char *(void)’
59 | extern char *strstr ();
| ^~~~~~
/usr/include/string.h:350:14: note: previous declaration of ‘strstr’ with type ‘char *(const char *, const char *)’
350 | extern char *strstr (const char *__haystack, const char *__needle)
| ^~~~~~
[80/378] gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/files.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/files.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/files.c.o -c ../backend/dvi/mdvi-lib/files.c
[81/378] gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/bitmap.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/bitmap.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/bitmap.c.o -c ../backend/dvi/mdvi-lib/bitmap.c
[82/378] env PKG_CONFIG_PATH=/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/meson-uninstalled:/usr/lib/pkgconfig:/usr/share/pkgconfig PKG_CONFIG=/usr/bin/pkg-config CC=gcc /usr/bin/g-ir-scanner --quiet --no-libtool --namespace=EvinceDocument --nsversion=3.0 --warn-all --output libdocument/EvinceDocument-3.0.gir -DEVINCE_COMPILATION -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/libdocument -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/libdocument -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/. -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/. --filelist=/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/libdocument/libevdocument3.so.4.0.0.p/EvinceDocument_3.0_gir_filelist --include=Gdk-3.0 --include=GdkPixbuf-2.0 --include=Gio-2.0 --include=GLib-2.0 --include=Gtk-3.0 --symbol-prefix=ev --identifier-prefix=Ev --pkg-export=evince-document-3.0 --cflags-begin -DHAVE_CONFIG_H -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/. -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/. -I/usr/include/cairo -I/usr/include/libxml2 -I/usr/include/freetype2 -I/usr/include/libpng16 -DWITH_GZFILEOP -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/webp -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cloudproviders -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/lib/pkgconfig/../../include/dbus-1.0 -I/usr/lib/pkgconfig/../../lib/dbus-1.0/include -I/usr/include/fribidi -I/usr/include/gio-unix-2.0 -I/usr/include/synctex -I/usr/include/gobject-introspection-1.0 --cflags-end --add-include-path=/usr/share/gir-1.0 -L/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/libdocument --library evdocument3 --extra-library=cairo --extra-library=gdk_pixbuf-2.0 --extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=gio-2.0 --extra-library=gtk-3 --extra-library=gdk-3 --extra-library=z --extra-library=pangocairo-1.0 --extra-library=pango-1.0 --extra-library=harfbuzz --extra-library=atk-1.0 --extra-library=cairo-gobject --extra-library=gmodule-2.0 --extra-library=xml2 --extra-library=m --extra-library=synctex --extra-library=girepository-1.0 --sources-top-dirs /builddir/build/BUILD/evince-48.0-build/evince-48.0/ --sources-top-dirs /builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/
[83/378] gcc -Ilibview/libevview3.so.3.0.0.p -Ilibview -I../libview -I. -I.. -Ilibdocument -I../libdocument -I/usr/include/gspell-1 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cloudproviders -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/webp -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/lib/pkgconfig/../../include/dbus-1.0 -I/usr/lib/pkgconfig/../../lib/dbus-1.0/include -I/usr/include/fribidi -I/usr/include/libxml2 -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/enchant-2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/gstreamer-1.0 -I/usr/include/orc-0.4 -I/usr/include/gtk-3.0/unix-print -I/usr/include/synctex -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -pthread -DWITH_GZFILEOP '-DG_LOG_DOMAIN="EvinceView"' '-DEVINCEDATADIR="/usr/share/evince"' -DEVINCE_COMPILATION -MD -MQ libview/libevview3.so.3.0.0.p/ev-view.c.o -MF libview/libevview3.so.3.0.0.p/ev-view.c.o.d -o libview/libevview3.so.3.0.0.p/ev-view.c.o -c ../libview/ev-view.c
../libview/ev-view.c: In function ‘ev_view_move_cursor’:
../libview/ev-view.c:7203:22: warning: ‘select_start_offset’ may be used uninitialized [-Wmaybe-uninitialized]
7203 | if (!get_caret_cursor_area (view, select_start_page, select_start_offset, &select_start_rect))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../libview/ev-view.c:7034:25: note: ‘select_start_offset’ was declared here
7034 | gint select_start_offset;
| ^~~~~~~~~~~~~~~~~~~
../libview/ev-view.c:7203:22: warning: ‘select_start_page’ may be used uninitialized [-Wmaybe-uninitialized]
7203 | if (!get_caret_cursor_area (view, select_start_page, select_start_offset, &select_start_rect))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../libview/ev-view.c:7035:25: note: ‘select_start_page’ was declared here
7035 | gint select_start_page;
| ^~~~~~~~~~~~~~~~~]: [The relevant error messages saying that there are conflicting types for ‘getenv’, ‘strtok', ‘strstr’]
| Issue: The build failed because of conflicting type declarations for standard C library functions (getenv, strtok, strstr) during the compilation of mdvi-lib.
Resolution: The cause is that the header file backend/dvi/mdvi-lib/private.h needs to include kpathsea/c-auto.h, which has defines for correct header files.
The patch should look like following:
diff -up evince-46.3.1/backend/dvi/mdvi-lib/private.h.me evince-46.3.1/backend/dvi/mdvi-lib/private.h
--- evince-46.3.1/backend/dvi/mdvi-lib/private.h.me 2025-04-272 12:50:22.625676965 +0100
+++ evince-46.3.1/backend/dvi/mdvi-lib/private.h 2025-04-22 12:51:51.141355752 +0100
@@ -32,6 +32,7 @@
# endif
#endif
+#include <kpathsea/c-auto.h>
#include <kpathsea/debug.h>
#include <kpathsea/tex-file.h>
#include <kpathsea/tex-glyph.h |
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: backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o
gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/dviread.c.o -c ../backend/dvi/mdvi-lib/dviread.c
In file included from /usr/include/kpathsea/debug.h:26,
from ../backend/dvi/mdvi-lib/private.h:35,
from ../backend/dvi/mdvi-lib/dviread.c:30:
/usr/include/kpathsea/c-std.h:48:14: error: conflicting types for ‘getenv’; have ‘char *(void)’
48 | extern char *getenv ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/dviread.c:21:
/usr/include/stdlib.h:773:14: note: previous declaration of ‘getenv’ with type ‘char *(const char *)’
773 | extern char *getenv (const char *__name) __THROW __nonnull ((1)) __wur;
| ^~~~~~
In file included from /usr/include/kpathsea/c-std.h:76:
/usr/include/kpathsea/c-memstr.h:57:14: error: conflicting types for ‘strtok’; have ‘char *(void)’
57 | extern char *strtok ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/dviread.c:23:
/usr/include/string.h:356:14: note: previous declaration of ‘strtok’ with type ‘char *(char * restrict, const char * restrict)’
356 | extern char *strtok (char *__restrict __s, const char *__restrict __delim)
| ^~~~~~
/usr/include/kpathsea/c-memstr.h:59:14: error: conflicting types for ‘strstr’; have ‘char *(void)’
59 | extern char *strstr ();
| ^~~~~~
/usr/include/string.h:350:14: note: previous declaration of ‘strstr’ with type ‘char *(const char *, const char *)’
350 | extern char *strstr (const char *__haystack, const char *__needle)
| ^~~~~~
../backend/dvi/mdvi-lib/dviread.c: In function ‘mdvi_init_context’:
../backend/dvi/mdvi-lib/dviread.c:767:9: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
767 | fread(dvi->fileid, 1, n, p);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
[79/378] gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -c ../backend/dvi/mdvi-lib/font.c
FAILED: backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o
gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/font.c.o -c ../backend/dvi/mdvi-lib/font.c
In file included from /usr/include/kpathsea/debug.h:26,
from ../backend/dvi/mdvi-lib/private.h:35,
from ../backend/dvi/mdvi-lib/font.c:23:
/usr/include/kpathsea/c-std.h:48:14: error: conflicting types for ‘getenv’; have ‘char *(void)’
48 | extern char *getenv ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/font.c:20:
/usr/include/stdlib.h:773:14: note: previous declaration of ‘getenv’ with type ‘char *(const char *)’
773 | extern char *getenv (const char *__name) __THROW __nonnull ((1)) __wur;
| ^~~~~~
In file included from /usr/include/kpathsea/c-std.h:76:
/usr/include/kpathsea/c-memstr.h:57:14: error: conflicting types for ‘strtok’; have ‘char *(void)’
57 | extern char *strtok ();
| ^~~~~~
In file included from ../backend/dvi/mdvi-lib/common.h:28,
from ../backend/dvi/mdvi-lib/mdvi.h:27,
from ../backend/dvi/mdvi-lib/font.c:22:
/usr/include/string.h:356:14: note: previous declaration of ‘strtok’ with type ‘char *(char * restrict, const char * restrict)’
356 | extern char *strtok (char *__restrict __s, const char *__restrict __delim)
| ^~~~~~
/usr/include/kpathsea/c-memstr.h:59:14: error: conflicting types for ‘strstr’; have ‘char *(void)’
59 | extern char *strstr ();
| ^~~~~~
/usr/include/string.h:350:14: note: previous declaration of ‘strstr’ with type ‘char *(const char *, const char *)’
350 | extern char *strstr (const char *__haystack, const char *__needle)
| ^~~~~~
[80/378] gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/files.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/files.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/files.c.o -c ../backend/dvi/mdvi-lib/files.c
[81/378] gcc -Ibackend/dvi/mdvi-lib/libmdvi.a.p -Ibackend/dvi/mdvi-lib -I../backend/dvi/mdvi-lib -I. -I.. -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -MD -MQ backend/dvi/mdvi-lib/libmdvi.a.p/bitmap.c.o -MF backend/dvi/mdvi-lib/libmdvi.a.p/bitmap.c.o.d -o backend/dvi/mdvi-lib/libmdvi.a.p/bitmap.c.o -c ../backend/dvi/mdvi-lib/bitmap.c
[82/378] env PKG_CONFIG_PATH=/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/meson-uninstalled:/usr/lib/pkgconfig:/usr/share/pkgconfig PKG_CONFIG=/usr/bin/pkg-config CC=gcc /usr/bin/g-ir-scanner --quiet --no-libtool --namespace=EvinceDocument --nsversion=3.0 --warn-all --output libdocument/EvinceDocument-3.0.gir -DEVINCE_COMPILATION -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/libdocument -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/libdocument -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/. -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/. --filelist=/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/libdocument/libevdocument3.so.4.0.0.p/EvinceDocument_3.0_gir_filelist --include=Gdk-3.0 --include=GdkPixbuf-2.0 --include=Gio-2.0 --include=GLib-2.0 --include=Gtk-3.0 --symbol-prefix=ev --identifier-prefix=Ev --pkg-export=evince-document-3.0 --cflags-begin -DHAVE_CONFIG_H -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/. -I/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/. -I/usr/include/cairo -I/usr/include/libxml2 -I/usr/include/freetype2 -I/usr/include/libpng16 -DWITH_GZFILEOP -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/webp -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cloudproviders -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/lib/pkgconfig/../../include/dbus-1.0 -I/usr/lib/pkgconfig/../../lib/dbus-1.0/include -I/usr/include/fribidi -I/usr/include/gio-unix-2.0 -I/usr/include/synctex -I/usr/include/gobject-introspection-1.0 --cflags-end --add-include-path=/usr/share/gir-1.0 -L/builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/libdocument --library evdocument3 --extra-library=cairo --extra-library=gdk_pixbuf-2.0 --extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=gio-2.0 --extra-library=gtk-3 --extra-library=gdk-3 --extra-library=z --extra-library=pangocairo-1.0 --extra-library=pango-1.0 --extra-library=harfbuzz --extra-library=atk-1.0 --extra-library=cairo-gobject --extra-library=gmodule-2.0 --extra-library=xml2 --extra-library=m --extra-library=synctex --extra-library=girepository-1.0 --sources-top-dirs /builddir/build/BUILD/evince-48.0-build/evince-48.0/ --sources-top-dirs /builddir/build/BUILD/evince-48.0-build/evince-48.0/redhat-linux-build/
[83/378] gcc -Ilibview/libevview3.so.3.0.0.p -Ilibview -I../libview -I. -I.. -Ilibdocument -I../libdocument -I/usr/include/gspell-1 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cloudproviders -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/webp -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/lib/pkgconfig/../../include/dbus-1.0 -I/usr/lib/pkgconfig/../../lib/dbus-1.0/include -I/usr/include/fribidi -I/usr/include/libxml2 -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/enchant-2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/gstreamer-1.0 -I/usr/include/orc-0.4 -I/usr/include/gtk-3.0/unix-print -I/usr/include/synctex -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -DHAVE_CONFIG_H -Wno-deprecated-declarations -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -m32 -march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -fasynchronous-unwind-tables -fstack-clash-protection -fPIC -pthread -DWITH_GZFILEOP '-DG_LOG_DOMAIN="EvinceView"' '-DEVINCEDATADIR="/usr/share/evince"' -DEVINCE_COMPILATION -MD -MQ libview/libevview3.so.3.0.0.p/ev-view.c.o -MF libview/libevview3.so.3.0.0.p/ev-view.c.o.d -o libview/libevview3.so.3.0.0.p/ev-view.c.o -c ../libview/ev-view.c
../libview/ev-view.c: In function ‘ev_view_move_cursor’:
../libview/ev-view.c:7203:22: warning: ‘select_start_offset’ may be used uninitialized [-Wmaybe-uninitialized]
7203 | if (!get_caret_cursor_area (view, select_start_page, select_start_offset, &select_start_rect))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../libview/ev-view.c:7034:25: note: ‘select_start_offset’ was declared here
7034 | gint select_start_offset;
| ^~~~~~~~~~~~~~~~~~~
../libview/ev-view.c:7203:22: warning: ‘select_start_page’ may be used uninitialized [-Wmaybe-uninitialized]
7203 | if (!get_caret_cursor_area (view, select_start_page, select_start_offset, &select_start_rect))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../libview/ev-view.c:7035:25: note: ‘select_start_page’ was declared here
7035 | gint select_start_page;
| ^~~~~~~~~~~~~~~~~ | The relevant error messages saying that there are conflicting types for ‘getenv’, ‘strtok', ‘strstr’ |
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:
[:: [ 09:37:11 ] :: [ BEGIN ] :: Running 'dnf install -y xapian-core xapian-core-devel g++ --enablerepo=rhel-CRB --enablerepo=rhel-buildroot'
Last metadata expiration check: 0:00:09 ago on Wed 27 Nov 2024 09:37:02 AM UTC.
Package xapian-core-1.4.18-3.el8.x86_64 is already installed.
Package xapian-core-devel-1.4.18-3.el8.x86_64 is already installed.
No match for argument: g++
Error: Unable to find a match: g++
:: [ 09:37:12 ] :: [ FAIL ] :: Command 'dnf install -y xapian-core xapian-core-devel g++ --enablerepo=rhel-CRB --enablerepo=rhel-buildroot' (Expected 0, got 1)]: [Indication that not all dependencies were installed.]
=============
[:: [ 09:37:14 ] :: [ BEGIN ] :: Compiling :: actually running 'g++ -o xapian_test xapian_test.cpp -lxapian'
/usr/share/beakerlib/testing.sh: line 896: g++: command not found
:: [ 09:37:14 ] :: [ FAIL ] :: Compiling (Expected 0, got 127)]: [Compilation failed.]
=============
[:: [ 09:37:14 ] :: [ FAIL ] :: Running test (Expected 0, got 127)
:: [ 09:37:14 ] :: [ FAIL ] :: File test_db should exist
:: [ 09:37:14 ] :: [ FAIL ] :: File 'xapian.log' should contain 'Document added successfully.'
:: [ 09:37:14 ] :: [ FAIL ] :: File 'xapian.log' should contain 'Found 1 matching documents.'
:: [ 09:37:14 ] :: [ FAIL ] :: File 'xapian.log' should contain 'Document ID 1: This is a simple test document'
]: [Failures caused by the failed compilation of xapian-core.]
| Issue: Compilation failed because of the missing g++ command.
Resolution: "gcc-c++" needs to be added as needed into main.fmf file of the test, if the package is installed, g++ command is presented. |
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:
:: [ 09:37:11 ] :: [ BEGIN ] :: Running 'dnf install -y xapian-core xapian-core-devel g++ --enablerepo=rhel-CRB --enablerepo=rhel-buildroot'
Last metadata expiration check: 0:00:09 ago on Wed 27 Nov 2024 09:37:02 AM UTC.
Package xapian-core-1.4.18-3.el8.x86_64 is already installed.
Package xapian-core-devel-1.4.18-3.el8.x86_64 is already installed.
No match for argument: g++
Error: Unable to find a match: g++
:: [ 09:37:12 ] :: [ FAIL ] :: Command 'dnf install -y xapian-core xapian-core-devel g++ --enablerepo=rhel-CRB --enablerepo=rhel-buildroot' (Expected 0, got 1) | Indication that not all dependencies were installed. |
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:
:: [ 09:37:14 ] :: [ BEGIN ] :: Compiling :: actually running 'g++ -o xapian_test xapian_test.cpp -lxapian'
/usr/share/beakerlib/testing.sh: line 896: g++: command not found
:: [ 09:37:14 ] :: [ FAIL ] :: Compiling (Expected 0, got 127) | Compilation 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:
:: [ 09:37:14 ] :: [ FAIL ] :: Running test (Expected 0, got 127)
:: [ 09:37:14 ] :: [ FAIL ] :: File test_db should exist
:: [ 09:37:14 ] :: [ FAIL ] :: File 'xapian.log' should contain 'Document added successfully.'
:: [ 09:37:14 ] :: [ FAIL ] :: File 'xapian.log' should contain 'Found 1 matching documents.'
:: [ 09:37:14 ] :: [ FAIL ] :: File 'xapian.log' should contain 'Document ID 1: This is a simple test document'
| Failures caused by the failed compilation of xapian-core. |
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 failed:
# /usr/bin/systemd-nspawn -q -M 2bcb87b719ec472d967486465205267d -D /var/lib/mock/fedora-39-x86_64-bootstrap-1706184257.512262/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.68g7uaxf:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-39-x86_64-1706184257.512262/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --setenv=SYSTEMD_NSPAWN_TMPFS_TMP=0 --setenv=SYSTEMD_SECCOMP=0 --resolv-conf=off /usr/bin/dnf-3 builddep --installroot /var/lib/mock/fedora-39-x86_64-1706184257.512262/root/ --releasever 39 --setopt=deltarpm=False --setopt=allow_vendor_change=yes --allowerasing --disableplugin=local --disableplugin=spacewalk --disableplugin=versionlock /var/lib/mock/fedora-39-x86_64-1706184257.512262/root//builddir/build/SRPMS/cp2k-2024.1-3.fc39.src.rpm --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 45 kB/s | 1.5 kB 00:00
Additional repo copr_lecris_release 45 kB/s | 1.5 kB 00:00
fedora 765 kB/s | 24 kB 00:00
updates 594 kB/s | 23 kB 00:00
No matching package to install: 'dbcsr-devel >= 2.6.0'
No matching package to install: 'dbcsr-mpich-devel >= 2.6.0'
No matching package to install: 'dbcsr-openmpi-devel >= 2.6.0]: [Mock tried to install BuildRequires (build dependencies) `dbcsr-devel`, `dbcsr-mpich-devel` and `dbcsr-openmp-devel` in specific versions. These dependencies were not available.]
| Issue: Missing BuildRequires in rpm repositories enabled during Mock build.
Resolution: Fix the dependencies so they point to existing packages, or provide the missing packages in the buildroot. |
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 failed:
# /usr/bin/systemd-nspawn -q -M 2bcb87b719ec472d967486465205267d -D /var/lib/mock/fedora-39-x86_64-bootstrap-1706184257.512262/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.68g7uaxf:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-39-x86_64-1706184257.512262/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --setenv=SYSTEMD_NSPAWN_TMPFS_TMP=0 --setenv=SYSTEMD_SECCOMP=0 --resolv-conf=off /usr/bin/dnf-3 builddep --installroot /var/lib/mock/fedora-39-x86_64-1706184257.512262/root/ --releasever 39 --setopt=deltarpm=False --setopt=allow_vendor_change=yes --allowerasing --disableplugin=local --disableplugin=spacewalk --disableplugin=versionlock /var/lib/mock/fedora-39-x86_64-1706184257.512262/root//builddir/build/SRPMS/cp2k-2024.1-3.fc39.src.rpm --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 45 kB/s | 1.5 kB 00:00
Additional repo copr_lecris_release 45 kB/s | 1.5 kB 00:00
fedora 765 kB/s | 24 kB 00:00
updates 594 kB/s | 23 kB 00:00
No matching package to install: 'dbcsr-devel >= 2.6.0'
No matching package to install: 'dbcsr-mpich-devel >= 2.6.0'
No matching package to install: 'dbcsr-openmpi-devel >= 2.6.0 | Mock tried to install BuildRequires (build dependencies) `dbcsr-devel`, `dbcsr-mpich-devel` and `dbcsr-openmp-devel` in specific versions. These dependencies were not available. |
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 match for argument: site-packages]: [Dnf `builddep` command complaints that the `site-packages` package is not available in the build repositories.]
| Issue: Missing BuildRequires in buildroot.
Resolution: Build/provide the`site-packages` package in the Copr repository. |
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 match for argument: site-packages | Dnf `builddep` command complaints that the `site-packages` package is not available in the build repositories. |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 0