Created attachment 913149 [details] build.log Hello, I have problem with firefox compilation, it compiles for some times and at the end it just ends with error. 1075:10.95 ld.lld: error: undefined symbol: mozilla::a11y::DocAccessible::FireDelayedEvent(unsigned int, mozilla::a11y::LocalAccessible*) 1075:10.96 >>> referenced by CssAltContent.cpp 1075:10.96 >>> ../../../accessible/base/CssAltContent.o:(mozilla::a11y::CssAltContent::HandleAttributeChange(int, nsAtom*)) 1075:12.01 x86_64-pc-linux-gnu-clang++-18: error: linker command failed with exit code 1 (use -v to see invocation) I guess it might have something to do with clang18, but not sure. Thanks, Regards, Petr Sourek
Created attachment 913150 [details] environment
Created attachment 913151 [details] emerge -pvq
Created attachment 913155 [details] emerge --info
First of all always try without ccache if it fails using that. 2nd +pgo is very sensitive to python stuff, so I'd suggest removing whatever custom python you're using (or polluting the environment with) when compiling firefox.
(In reply to Joonas Niilola from comment #4) > First of all always try without ccache if it fails using that. 2nd +pgo is > very sensitive to python stuff, so I'd suggest removing whatever custom > python you're using (or polluting the environment with) when compiling > firefox. Ok, thanks. I had compiled without ccache (previous atempt, having this error for 3 versions), but when it failed the same I had enabled it again. So now I am disabling ccache and -pgo and will let you know (it compiles for some time). Thanks
Disabled ccache, removed pgo and it compiled, thanks.
Same issue here but I would wonder how would this be fixed if I wanted to use pgo -jumbo-build and how would I go about fixing this so it can not fail the build I have already tried without ccache and failed with pgo still enabled but when pgo is disabled it works as stated above, how can I fix it so it works with pgo regardless of ccache/etc. Finally Joonas how do I un-pollute python and stuff so that the build works. Thanks again
(In reply to Kyle Rabago from comment #7) > how do I > un-pollute python and stuff so that the build works. That may not apply to you at all. But indeed, this seems like a "-jumbo-build" problem. I've never tested "-jumbo-build +pgo" combination but it wouldn't surprise me if it didn't work at all. I run into all kinds of random problems with -jumbo-build but they're mostly related to compiling with gcc.
(In reply to Joonas Niilola from comment #8) > (In reply to Kyle Rabago from comment #7) > > how do I > > un-pollute python and stuff so that the build works. > > That may not apply to you at all. > > But indeed, this seems like a "-jumbo-build" problem. I've never tested > "-jumbo-build +pgo" combination but it wouldn't surprise me if it didn't > work at all. I run into all kinds of random problems with -jumbo-build but > they're mostly related to compiling with gcc. So then how can we fix it so that it will work with clang, pgo and -jumbo-build I know that it has worked before with those flags im not sure what version but I do remeber it fully building with those use flags specifically set
(In reply to Kyle Rabago from comment #9) > > So then how can we fix it so that it will work with clang, pgo and > -jumbo-build I know that it has worked before with those flags im not sure > what version but I do remeber it fully building with those use flags > specifically set It should be reported upstream, especially if it used to work. "-jumbo-build" is "non-unified build" in their terms. But as I said, -jumbo-build is kind of random. It may start working between releases even without a bug through other updates. You'd still be best taking it upstream.
(In reply to Joonas Niilola from comment #10) > (In reply to Kyle Rabago from comment #9) > > > > So then how can we fix it so that it will work with clang, pgo and > > -jumbo-build I know that it has worked before with those flags im not sure > > what version but I do remeber it fully building with those use flags > > specifically set > > It should be reported upstream, especially if it used to work. > "-jumbo-build" is "non-unified build" in their terms. > > But as I said, -jumbo-build is kind of random. It may start working between > releases even without a bug through other updates. You'd still be best > taking it upstream. How would I go about reporting that upstream so it can be pushed to next release other than of course the official repo/bug reporter anything in particular I need to include specifically in my bug report that relates to gentoo?
(In reply to Kyle Rabago from comment #11) > > How would I go about reporting that upstream so it can be pushed to next > release other than of course the official repo/bug reporter anything in > particular I need to include specifically in my bug report that relates to > gentoo? Just summarize the issue is when trying to build with pgo, but without unified-build (+MOZ_PGO, --disable-unified-build). And post build.log - it can be compressed with "xz -9" for example if it's too large. I'd also mention that it used to work, however you're most likely asked to bisect the issue then between two releases so be prepared to do that. And be aware non-unified builds aren't really their priority but it's the best place to try and get it fixed. If you can find out the commit that broke non-unified pgo for you, usually the person responsible for the commit will fix the regression.
*** Bug 946604 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4d69f169b9b980067436aa33b84398ee19ca4d2 commit b4d69f169b9b980067436aa33b84398ee19ca4d2 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2024-12-18 17:12:21 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2024-12-18 17:12:21 +0000 www-client/firefox: require 'jumbo-build' when +pgo is specified - I'm honestly surprised if it ever worked otherwise. See bugs for discussion. Bug: https://bugs.gentoo.org/946604 Bug: https://bugs.gentoo.org/945801 Signed-off-by: Joonas Niilola <juippis@gentoo.org> www-client/firefox/firefox-128.5.0.ebuild | 1 + www-client/firefox/firefox-128.5.1.ebuild | 1 + www-client/firefox/firefox-133.0.3.ebuild | 1 + 3 files changed, 3 insertions(+)
