-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Linking fails attempting to run cc (fork returns -1) #5772
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
Comments
I just deleted everything and compiled it again. Now it makes it to stage2, and then fails with the same error. |
I can't compile to. I'm on debian squeeze. |
It would probably help diagnosis if you followed the error's advice |
More helpful would be running rustc under gdb and breaking on rust_task_fail. The backtrace from there is must more useful. |
@crazymykl That's what I did. See the first line of the block. @jdm How? |
Run make with VERBOSE=1 to see the actual command that's failing. Run |
@progval mea culpa. At least some attention was drawn to the bug by my mistake. |
("Aucun fichier ou dossier de ce type" means "No such file or directory") |
What about the full backtrace output from |
Oops, sorry.
|
You apparently lack a |
What do you mean? I have And stages 0 and 1 worked once. (I tried to run "make clean" and then "make", but stage 0 fails again) |
What's the output of running make with |
RUST_LOG=rustc::back::link make >journal.txt 2>&1 cfg: build triple x86_64-unknown-linux-gnu |
|
I've updated the title to reflect the error your logs show. I'm mystified why run::program_output would report that |
Although, reading the source of rust_run_program.cpp, apparently the |
Could that be because it cannot allocate enough memory to the fork? The process uses about 35% of my RAM when it crashes (I have no SWAP). EDIT: That would explain why stages 0 and 1 worked once. |
I closed Firefox (ie. what consumes the more memory ;) ) and stage0 |
and... it worked! I'm not closing this issue as requiring so much memory (more than 2GB) is still a problem, isn't it? |
Alas, rustc does use a lot of memory. I think there's no other bug here; reopen if I'm confused. |
Don't lint `multiple_inherent_impl` with generic arguments fixes: rust-lang#5772 changelog: Treat different generic arguments as different types in `multiple_inherent_impl`
Hi,
I am getting this when trying to compile Rust 0.6 (tarball downloaded via the website):
I use Debian Sid (amd64).
Regards,
Valentin
The text was updated successfully, but these errors were encountered: