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.

Sign up for GitHub

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

Jump to bottom

Compilation Error #11589

Closed
yelinaung opened this issue Jan 16, 2014 · 4 comments
Closed

Compilation Error #11589

yelinaung opened this issue Jan 16, 2014 · 4 comments

Comments

@yelinaung
Copy link

I get the follow compilation error while compiling and can't continue.

llvm[2]: Compiling DiagnosticPrinter.cpp for Release+Asserts build
llvm[2]: Compiling Dominators.cpp for Release+Asserts build
llvm[2]: Compiling Function.cpp for Release+Asserts build
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions.
/bin/rm: cannot remove `/home/vagrant/rust-0.9/x86_64-unknown-linux-gnu/llvm/lib/IR/Release+Asserts/Function.d.tmp': No such file or directory
make[2]: *** [/home/vagrant/rust-0.9/x86_64-unknown-linux-gnu/llvm/lib/IR/Release+Asserts/Function.o] Error 1
make[2]: Leaving directory `/home/vagrant/rust-0.9/x86_64-unknown-linux-gnu/llvm/lib/IR'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/home/vagrant/rust-0.9/x86_64-unknown-linux-gnu/llvm'
make: *** [/home/vagrant/rust-0.9/x86_64-unknown-linux-gnu/llvm/Release+Asserts/bin/llvm-config] Error 2

What kind of logs do I have to provide more to resolve this issue ?

Thanks.
@huonw
Copy link
Member

huonw commented Jan 16, 2014

I sometimes see similar errors, and running just make again "fixes" them; so can you try just running make twice in a row?

@yelinaung
Copy link
Author

Yeah I tried running twice and it's still showing the error. Let me just pull from the master and build again. Will get back to you. Thanks.

@kud1ing
Copy link

kud1ing commented Jan 16, 2014

My first guess, which is supported by googling for this error message, is that you are short of RAM.

@yelinaung
Copy link
Author

@kud1ing I adjusted the memory of my vagrant box and it seems resolve now. Thanks y'all

flip1995 pushed a commit to flip1995/rust that referenced this issue Oct 6, 2023
@bors
Auto merge of rust-lang#11589 - koka831:fix/10198, r=giraffate
81400e2 
std_instead_of_core: avoid lint inside of proc-macro

- fixes rust-lang/rust-clippy#10198

note: The lint for the reported `thiserror::Error` has been suppressed by [Don't lint unstable moves in std_instead_of_core](https://github.com/rust-lang/rust-clippy/pull/9545/files#diff-2cb8a24429cf9d9898de901450d640115503a10454d692dddc6a073a299fbb7eR29) because `thiserror::Error`  internally implements `std::error::Error for (derived struct)`.

changelog: [`std_intead_of_core`]: avoid linting inside proc-macro

I confirmed this change fixes the problem:
<details>
<summary>test result without the change</summary>

```console
error: used import from `std` instead of `core`
  --> tests/ui/std_instead_of_core.rs:65:14
   |
LL |     #[derive(ImplStructWithStdDisplay)]
   |              ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the derive macro `ImplStructWithStdDisplay` (in Nightly builds, run with -Z macro-backtrace for more info)
```
</details>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yelinaung @kud1ing @huonw