| View previous topic :: View next topic |
| Author |
Message |
tckosvic
Tux's lil' helper
Joined: 18 Apr 2023
Posts: 128
|
 Posted: Thu Oct 31, 2024 3:22 pm Post subject: |
 |
|
@genome,
I understand what you are saying but the actual errors that are listed by emerge were included in my first post. The errors listed in the build.log file look to me to be a repetition of the errors listed by emerge.
But perhaps there is more info in build.log that I am not conversant with.
See below from my first post.
| Code: |
ERROR: dev-python/pyside6-6.7.3::gentoo failed (configure phase):
* cmake failed
*
* Call stack:
* ebuild.sh, line 136: Called src_configure
* environment, line 3458: Called python_foreach_impl 'pyside6_configure'
* environment, line 3066: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'pyside6_configure'
* environment, line 2613: Called _multibuild_run '_python_multibuild_wrapper' 'pyside6_configure'
* environment, line 2611: Called _python_multibuild_wrapper 'pyside6_configure'
* environment, line 811: Called pyside6_configure
* environment, line 3456: Called cmake_src_configure
* environment, line 1558: Called die
* The specific snippet of code:
* "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
|
|
|
| Back to top |
|
 |
eschwartz
Developer
Joined: 29 Oct 2023
Posts: 213
|
| Posted: Thu Oct 31, 2024 3:32 pm Post subject: |
|
|
| tckosvic wrote: | @genome,
I understand what you are saying but the actual errors that are listed by emerge were included in my first post. The errors listed in the build.log file look to me to be a repetition of the errors listed by emerge.
But perhaps there is more info in build.log that I am not conversant with.
See below from my first post.
|
You have already been informed in no uncertain terms and without any ambiguosity whatsoever that those are NOT the actual errors and that portage itself says the actual errors are in the build.log
So yes, there is more info in build.log that you are not conversant with -- which is the entire point of this discussion.
| Nowa wrote: | "cmake failed" is not the real error, some job that cmake was running failed and we need to know which job and why.
|
| eschwartz wrote: | I routinely look through far, far longer pastebins than a mere tiny 18k lines worth, in order to debug the problems users report.
It is exceedingly easy to grep for specific bug keywords or manually inspect only the last couple hundred lines -- you just need to have a lot of familiarity with debugging user problems, know how to recognize and analyze compiler errors, make/ninja error statuses, etc. It is domain-specific knowledge, that's why users ask experts for help, but the experts absolutely do know how to find the real issue in *seconds*.
The reason we ask for the full 18k lines of text is because long experience has proven that when people try to shorten the text in order to be "helpful" they accidentally remove the 5 lines that were actually needed and which we could have found immediately, if only they were actually there to be found...
... and instead we end up spending multiple *days* arguing back and forth about the correct way to report a bug.
In summary, please stop overthinking this. We ask for certain information for a reason. It's because the best way to ensure a FAST response is to provide ALL the information that you have available, so that we are able to look at the information *we* know matters. |
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
