www-client/firefox-102.4.0 fails to build with libevent-2.1.8, worked with libevent-2.1.12. Takes me 12h to build on my amd64 system. Couldn't attach build.log or test if libevent-2.1.11 worked. This bug requires only a simple ebuild update on libevent, I think. Reproducible: Always Actual Results: Build fails with undeclared EVENT__SIZEOF_TIME_T (not the exact message)
Please include the full build.log and emerge --info. I've built with system-libevent fine, and that libevent has been out for ages.
wait, why are you building with such an old libevent? 2.1.8 isn't in tree anymore?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e4d915e30d3765d9551440fdb54c4ddfff86b9ce commit e4d915e30d3765d9551440fdb54c4ddfff86b9ce Author: Sam James <sam@gentoo.org> AuthorDate: 2022-11-03 23:08:20 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-03 23:08:20 +0000 www-client/firefox: crank up system-libevent dependency The bundled version of libevent is 2.1.12: >firefox-102.4.0/ipc/chromium/src/third_party/libevent/configure.ac:8:AC_INIT(libevent,2.1.12-stable) Closes: https://bugs.gentoo.org/879341 Signed-off-by: Sam James <sam@gentoo.org> www-client/firefox/firefox-102.4.0.ebuild | 2 +- www-client/firefox/firefox-106.0.2.ebuild | 2 +- www-client/firefox/firefox-106.0.4.ebuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
(In reply to Sam James from comment #2) > wait, why are you building with such an old libevent? I'm updating my system :) > 2.1.8 isn't in tree anymore? Yes, isn't in the tree. Maybe I'm not very clear, sorry. As Larry noted, I'm requesting an ebuild dependency update. Thanks all for replies.
(In reply to Enrique Domínguez from comment #4) > > > 2.1.8 isn't in tree anymore? > Yes, isn't in the tree. Maybe I'm not very clear, sorry. As Larry noted, I'm > requesting an ebuild dependency update. > Thanks all for replies. I don't agree the ebuild needs an update. The problem goes away once you update your system. (but the ebuild was updated already by nicer people than me so have it!) I'd understand if we were talking about a dependency that was dropped like few weeks - few months ago, but 2.1.8 was dropped _over_ 2 years ago, nearly 2½. Since it's a runtime dependency I can't imagine how you managed to stay that much behind with updates - unless you deliberately _chose_ to. Then it's your problem, not ours.
