Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"make check" error on Arch Linux "make[1]: *** [libharfbuzz.dummy] Error 101" #88

Closed
RunningDroid opened this issue Sep 27, 2012 · 2 comments

Comments

@RunningDroid
Copy link

@RunningDroid RunningDroid commented Sep 27, 2012

make check

make[1]: Entering directory `/home/runningdroid/testing/servo/build/src/rust-harfbuzz'
rustc -O  /home/runningdroid/testing/servo/src/rust-harfbuzz/harfbuzz.rc -o libharfbuzz.dummy
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=0,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
make[1]: *** [libharfbuzz.dummy] Error 101
make[1]: Leaving directory `/home/runningdroid/testing/servo/build/src/rust-harfbuzz'
make: *** [/home/runningdroid/testing/servo/build/src/rust-harfbuzz/rust-harfbuzz.dummy] Error 2

make check-servo RUST_LOG=rustc=0,::rt::backtrace

make[1]: Entering directory `/home/runningdroid/testing/servo/build/src/rust-harfbuzz'
rustc -O  /home/runningdroid/testing/servo/src/rust-harfbuzz/harfbuzz.rc -o libharfbuzz.dummy
rust: task failed at 'can't determine value for sysroot', /var/aurget/src/rust-git/src/rust-build/src/rustc/metadata/filesearch.rs:104
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(_ZN9rust_task13begin_failureEPKcS1_m+0x5d)[0x7f45d87a3f8d]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(+0x34dbd)[0x7f45d87bddbd]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(upcall_fail+0x1a8)[0x7f45d87a6898]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustc-c84825241471686d-0.4.so(+0x69c285)[0x7f45d908c285]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustc-c84825241471686d-0.4.so(_ZN8metadata10filesearch13mk_filesearch16_2f4813d5be6e9063_04E+0x8d)[0x7f45d908b09d]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustc-c84825241471686d-0.4.so(_ZN6driver6driver14build_session_17_fd91e7d0f2aafe413_04E+0xa2)[0x7f45d909dc42]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustc-c84825241471686d-0.4.so(_ZN6driver6driver13build_session16_8e30be84d12dc363_04E+0xb1)[0x7f45d909da01]
rustc[0x407c0f]
rustc[0x411e34]
rustc[0x40ed63]
rustc[0x40d9e8]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0x76687)[0x7f45d9e0f687]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0xb7154)[0x7f45d9e50154]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(_Z18task_start_wrapperP10spawn_args+0x24)[0x7f45d87a4734]
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=0,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: task failed at 'explicit failure', /var/aurget/src/rust-git/src/rust-build/src/rustc/driver/rustc.rs:283
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(_ZN9rust_task13begin_failureEPKcS1_m+0x5d)[0x7f45d87a3f8d]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(+0x34dbd)[0x7f45d87bddbd]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(upcall_fail+0x1a8)[0x7f45d87a6898]
rustc[0x40cf0b]
rustc[0x411e34]
rustc[0x4119e8]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(_Z18task_start_wrapperP10spawn_args+0x24)[0x7f45d87a4734]
rust: domain main @0x20041c0 root task failed
rust: task failed at 'killed', /var/aurget/src/rust-git/src/rust-build/src/libcore/task.rs:781
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(_ZN9rust_task13begin_failureEPKcS1_m+0x5d)[0x7f45d87a3f8d]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(+0x34dbd)[0x7f45d87bddbd]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(upcall_fail+0x1a8)[0x7f45d87a6898]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(_ZN4task5yield16_9531951b4f79f8b3_04E+0xc4)[0x7f45d9df8af4]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0x9200e)[0x7f45d9e2b00e]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(_ZN7private11weaken_task17_d15522f384beb8853_04E+0xc4)[0x7f45d9e2ae84]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0x91db5)[0x7f45d9e2adb5]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0xb7154)[0x7f45d9e50154]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0x91151)[0x7f45d9e2a151]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0x901b6)[0x7f45d9e291b6]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0x76687)[0x7f45d9e0f687]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/libcore-c3ca5d77d81b46c1-0.4.so(+0xb7154)[0x7f45d9e50154]
/usr/lib/rustc/x86_64-unknown-linux-gnu/lib/librustrt.so(_Z18task_start_wrapperP10spawn_args+0x24)[0x7f45d87a4734]
make[1]: *** [libharfbuzz.dummy] Error 101
make[1]: Leaving directory `/home/runningdroid/testing/servo/build/src/rust-harfbuzz'
make: *** [/home/runningdroid/testing/servo/build/src/rust-harfbuzz/rust-harfbuzz.dummy] Error 2
@burg
Copy link

@burg burg commented Sep 28, 2012

This seems to be distinct from Rust Issue #3592 (rust-lang/rust#3592)

@burg
Copy link

@burg burg commented Sep 28, 2012

@RunningDroid, this is an upstream bug in Rust. Can you look at rust-lang/rust#1711 and try performing the diagnostic that was suggested?

@burg burg closed this Nov 7, 2012
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
Coverage tool: Add spec status and UI to sort specs by status.
glennw added a commit to glennw/servo that referenced this issue Jan 16, 2017
Don't use a uniform to store the texture size in the filter shader.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.