| View previous topic :: View next topic |
| Author |
Message |
mDup
Apprentice
Joined: 14 Apr 2006
Posts: 212
|
 Posted: Wed Nov 29, 2017 1:37 pm Post subject: arm64 gentoo firefox 57.0 |
 |
|
Did anyone manage to emerge firefox 57.0 ?
Using kindly provided previous hints (using which previously I could emerge versions up to 56.0), in 57.0 build.log I find several
'fatal error's plhash.h or prthread.h 'not found'.
I incrementally replaced some "plhash.h" by <nspr/plhash.h> (same for prthread) but new similar fatal errors keep coming.
Any patch or trick to succeed is welcome.
Have a nice day. |
|
| Back to top |
|
 |
Sakaki
Guru
Joined: 21 May 2014
Posts: 409
|
| Posted: Wed Nov 29, 2017 2:27 pm Post subject: |
|
|
Seeing similar things this end - have currently masked firefox-57.0 in the rpi3 overlay used by the gentoo-on-rpi3-64bit image.
_________________
Regards,
sakaki |
|
| Back to top |
|
|
mDup
Apprentice
Joined: 14 Apr 2006
Posts: 212
|
| Posted: Wed Nov 29, 2017 4:50 pm Post subject: |
|
|
| Sakaki wrote: | | Seeing similar things this end - have currently masked firefox-57.0 in the rpi3 overlay used by the gentoo-on-rpi3-64bit image. |
OK good to know I am not alone  |
|
| Back to top |
|
|
mDup
Apprentice
Joined: 14 Apr 2006
Posts: 212
|
| Posted: Tue Dec 12, 2017 4:47 pm Post subject: |
|
|
fwiw
for firefox-57.0.1 I encounter other issue (seems with rust)
| Code: | stack backtrace:
0: 0xaaaae64a47bf - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::h1fbcb51845b49e4c
1: 0xaaaae64a1b5b - std::sys_common::backtrace::_print::he788aead51a7e16b
2: 0xaaaae64a9ec3 - std::panicking::default_hook::{{closure}}::h252468129423eef2
3: 0xaaaae64a99ef - std::panicking::default_hook::h24e4458f9a7ca614
4: 0xaaaae64aa2fb - std::panicking::rust_panic_with_hook::h44eb20c82230662b
5: 0xaaaae64aa193 - std::panicking::begin_panic::h0edbe9007a581e1a
6: 0xaaaae64aa123 - std::panicking::begin_panic_fmt::h789e2018894996b6
7: 0xaaaae6241e9f - build_script_build::build_gecko::bindings::write_binding_file::h8a4aef1b33f13149
8: 0xaaaae62453bb - build_script_build::build_gecko::bindings::generate_structs::h969795347ad5fcd3
9: 0xaaaae64b0a0f - __rust_maybe_catch_panic
10: 0xaaaae623b83f - <F as alloc::boxed::FnBox<A>>::call_box::hb27a421196d5af9e
11: 0xaaaae64a91af - std::sys::imp::thread::Thread::new::thread_start::h7547893739a4d7c8
12: 0xffffbb8b5853 - <unknown>
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Any', src/libcore/result.rs:860
stack backtrace:
0: 0xaaaae64a47bf - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::h1fbcb51845b49e4c
1: 0xaaaae64a1b5b - std::sys_common::backtrace::_print::he788aead51a7e16b
2: 0xaaaae64a9ec3 - std::panicking::default_hook::{{closure}}::h252468129423eef2
3: 0xaaaae64a99ef - std::panicking::default_hook::h24e4458f9a7ca614
4: 0xaaaae64aa2fb - std::panicking::rust_panic_with_hook::h44eb20c82230662b
5: 0xaaaae64aa193 - std::panicking::begin_panic::h0edbe9007a581e1a
6: 0xaaaae64aa123 - std::panicking::begin_panic_fmt::h789e2018894996b6
7: 0xaaaae64aa0c7 - rust_begin_unwind
8: 0xaaaae64b70af - core::panicking::panic_fmt::hd9c3fa5e8be4b364
9: 0xaaaae623b29f - core::result::unwrap_failed::he518f7b348085c7a
10: 0xaaaae624aaa3 - build_script_build::main::hf3a676181ab4a602
11: 0xaaaae64b0a0f - __rust_maybe_catch_panic
12: 0xaaaae64aa87f - std::rt::lang_start::h615ea895ccae507e
13: 0xffffbb72d163 - <unknown>
|
|
|
| Back to top |
|
|
psychedup
n00b
Joined: 02 Oct 2012
Posts: 19
Location: Bremerton, WA, US
|
| Posted: Mon Jan 08, 2018 6:33 pm Post subject: |
|
|
| mDup wrote: | fwiw
for firefox-57.0.1 I encounter other issue (seems with rust)
| Code: | stack backtrace:
0: 0xaaaae64a47bf - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::h1fbcb51845b49e4c
1: 0xaaaae64a1b5b - std::sys_common::backtrace::_print::he788aead51a7e16b
2: 0xaaaae64a9ec3 - std::panicking::default_hook::{{closure}}::h252468129423eef2
3: 0xaaaae64a99ef - std::panicking::default_hook::h24e4458f9a7ca614
4: 0xaaaae64aa2fb - std::panicking::rust_panic_with_hook::h44eb20c82230662b
5: 0xaaaae64aa193 - std::panicking::begin_panic::h0edbe9007a581e1a
6: 0xaaaae64aa123 - std::panicking::begin_panic_fmt::h789e2018894996b6
7: 0xaaaae6241e9f - build_script_build::build_gecko::bindings::write_binding_file::h8a4aef1b33f13149
8: 0xaaaae62453bb - build_script_build::build_gecko::bindings::generate_structs::h969795347ad5fcd3
9: 0xaaaae64b0a0f - __rust_maybe_catch_panic
10: 0xaaaae623b83f - <F as alloc::boxed::FnBox<A>>::call_box::hb27a421196d5af9e
11: 0xaaaae64a91af - std::sys::imp::thread::Thread::new::thread_start::h7547893739a4d7c8
12: 0xffffbb8b5853 - <unknown>
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Any', src/libcore/result.rs:860
stack backtrace:
0: 0xaaaae64a47bf - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::h1fbcb51845b49e4c
1: 0xaaaae64a1b5b - std::sys_common::backtrace::_print::he788aead51a7e16b
2: 0xaaaae64a9ec3 - std::panicking::default_hook::{{closure}}::h252468129423eef2
3: 0xaaaae64a99ef - std::panicking::default_hook::h24e4458f9a7ca614
4: 0xaaaae64aa2fb - std::panicking::rust_panic_with_hook::h44eb20c82230662b
5: 0xaaaae64aa193 - std::panicking::begin_panic::h0edbe9007a581e1a
6: 0xaaaae64aa123 - std::panicking::begin_panic_fmt::h789e2018894996b6
7: 0xaaaae64aa0c7 - rust_begin_unwind
8: 0xaaaae64b70af - core::panicking::panic_fmt::hd9c3fa5e8be4b364
9: 0xaaaae623b29f - core::result::unwrap_failed::he518f7b348085c7a
10: 0xaaaae624aaa3 - build_script_build::main::hf3a676181ab4a602
11: 0xaaaae64b0a0f - __rust_maybe_catch_panic
12: 0xaaaae64aa87f - std::rt::lang_start::h615ea895ccae507e
13: 0xffffbb72d163 - <unknown>
|
|
Have you had any luck resolving this? I'm getting the same error trying to build firefox-57.0.4 on a pine64 (arm64).
I found this bug which looks like the same error on a previous version but for FreeBSD. |
|
| Back to top |
|
|
mDup
Apprentice
Joined: 14 Apr 2006
Posts: 212
|
| Posted: Mon Jan 08, 2018 11:59 pm Post subject: |
|
|
| psychedup wrote: |
Have you had any luck resolving this? I'm getting the same error trying to build firefox-57.0.4 on a pine64 (arm64).
I found this bug which looks like the same error on a previous version but for FreeBSD. |
I have not investigated but will try again. Keep you informed.
update
I tried firefox-57.0.4 running into same issue.
update
same issue using udated dev-lang/rust-1.23.0-r1 . |
|
| Back to top |
|
|
mDup
Apprentice
Joined: 14 Apr 2006
Posts: 212
|
| Posted: Fri Feb 16, 2018 4:31 pm Post subject: |
|
|
| fwiw: I have been able to build firefox-58.0.1 |
|
| Back to top |
|
|
Khumarahn
Apprentice
Joined: 17 Apr 2009
Posts: 199
|
| Posted: Mon Mar 19, 2018 9:29 pm Post subject: |
|
|
Is anyone still able to compile 58.0.1? There is a strange no-message compilation error, though it seems not arm specific
https://bugs.gentoo.org/650846 |
|
| Back to top |
|
|
mDup
Apprentice
Joined: 14 Apr 2006
Posts: 212
|
| Posted: Mon Mar 19, 2018 9:51 pm Post subject: |
|
|
| Khumarahn wrote: | Is anyone still able to compile 58.0.1? There is a strange no-message compilation error, though it seems not arm specific
https://bugs.gentoo.org/650846 |
fwiw: the USE differences with my (passed) build are
| Code: | system-harfbuzz
system-icu
system-jpeg
system-libevent
system-libvpx
system-sqlite
-wifi |
|
|
| Back to top |
|
|
Sakaki
Guru
Joined: 21 May 2014
Posts: 409
|
| Posted: Sat Mar 31, 2018 6:31 pm Post subject: |
|
|
I too have been having quite a frustrating time with this.
However, having (eventually) built rust-1.23.0-1 (the vanilla Gentoo tree ebuild will do ~arm64 OK now, but doesn't default to building a single-target LLVM as NeddySeagoon's original ebuild did - so if you use it, be prepared for quite a long wait!) and cargo-0.24.0, I finally managed to get firefox-58.0.1 to build on my RPi3 (with distcc backing). It needed a 3GiB swap file, and failed a couple of times through the compile with seemingly random rust errors (similar to bug 650846).
(Tip) When the emerge failed, I just restarted the make from where it left off with: | Code: | | pi64 ~ # ebuild /usr/portage/www-client/firefox/firefox-58.0.1.ebuild merge |
I had to do this twice, but it did complete in the end. The USE flags, following mDup, were: | Code: | | bindist dbus screenshot startup-notification system-harfbuzz system-icu system-jpeg system-libevent system-libvpx system-sqlite -custom-cflags -custom-optimization -debug -eme-free -gmp-autoupdate -hardened -hwaccel -jack -neon -pulseaudio -selinux -test -wifi |
However, I'm going to try building it again now without the "system-..." flags, for the forthcoming gentoo-on-rpi3-64bit release, as these can end up requiring frequent rebuilds of the browser on the build server.
Perhaps I should just get myself a 96-core ARM box ^-^
_________________
Regards,
sakaki |
|
| Back to top |
|
|
Khumarahn
Apprentice
Joined: 17 Apr 2009
Posts: 199
|
| Posted: Sat Mar 31, 2018 6:36 pm Post subject: |
|
|
It seems to fail at the strange
| Code: | | thread 'rustc' panicked at 'other was less than the current instant', src/libstd/sys/unix/time.rs:284:16 |
Some problem with timers (?), seems intermittent. Maybe, indeed, restarting the compilation is the way to go? I should retry. |
|
| Back to top |
|
|
Sakaki
Guru
Joined: 21 May 2014
Posts: 409
|
| Posted: Sat Mar 31, 2018 7:06 pm Post subject: |
|
|
@Khumarahn,
Yes, that "other was less than the current instant" error was exactly the issue I was seeing too (twice in the course of one emerge).
As such, most likely if you restart the build (and have sufficient swap) it should work for you also.
_________________
Regards,
sakaki |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54615
Location: 56N 3W
|
| Posted: Sat Mar 31, 2018 8:42 pm Post subject: |
|
|
If it helps, use my ~arm64 BINHOST
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Gentoo on ARM
