Summary: | www-client/ungoogled-chromium-88.0.4324.192-r1::PF4Public - three packages fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcus V Salvador <marcus.v.salvador92> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | ionen, jstein, marcus.v.salvador92 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | www-client/ungoogled-chromium-88.0.4324.192-r1 |
Description
Marcus V Salvador
2021-03-04 22:43:59 UTC
Created attachment 689385 [details]
www-client/ungoogled-chromium-88.0.4324.192-r1
Archives:
emerge_info_command.txt
ungoogled_chromium_emerge_problem.txt
openh264_build.log
re2_build.log
xdg-utils_build.log
fPIC_compilation.conf
package.env
make.conf
Given the fact, that my overlay does have neither of the failing packages and given that ungoogled-chromium ebuild (which indeed is in my overlay) wasn't even attempted to be compiled, I don't to see how this issue is related to my overlay at all. It's preferable to file bugs against the packages you are having issues with and not the end-goal package (which led to confusion like this). However, in a situation where it's multiple packages, there's good odds there's a specific reason for it rather than a bug, and so support venues are preferable first: https://www.gentoo.org/support/ That aside, the failures are happening because you have -fPIE in C(XX)FLAGS, note that pie is already default-enforced on gentoo (by gcc) but can lead to issues if specified. Also, please don't use tar for logs in the future, and don't CC arches (amd64@) like that -- these serve a different purpose. (In reply to PF4Public from comment #2) > Given the fact, that my overlay does have neither of the failing packages > and given that ungoogled-chromium ebuild (which indeed is in my overlay) > wasn't even attempted to be compiled, I don't to see how this issue is > related to my overlay at all. Hello! It's just how I look properly to reference well my problem. For me, as user, seems related, because I'd tried to compile www-client/ungoogled-chromium and these three packages failed to compile. So, I feel better reference these packages with the ungoogled-chromium just to relate better my problem and receive an awesome help overall. Thanks so much for your comment. Best regards, Marcus V. (In reply to Ionen Wolkens from comment #3) > It's preferable to file bugs against the packages you are having issues with > and not the end-goal package (which led to confusion like this). > > However, in a situation where it's multiple packages, there's good odds > there's a specific reason for it rather than a bug, and so support venues > are preferable first: > https://www.gentoo.org/support/ > > That aside, the failures are happening because you have -fPIE in C(XX)FLAGS, > note that pie is already default-enforced on gentoo (by gcc) but can lead to > issues if specified. > > Also, please don't use tar for logs in the future, and don't CC arches > (amd64@) like that -- these serve a different purpose. Hello! Definetely, I like it! I agree with you. I'll look forward to these tips in compilation in order to avoid problems. Also, I'll save this support link which I didn't know before. Sorry. Anyway, I've tried my best to reference well my problem. Sorry if I did confusion in this bug. And, I'll not do that about tar for logs and CC arches. Really appreciated it these tips too. Best regards, Marcus V. |