-
Notifications
You must be signed in to change notification settings - Fork 227
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
Not able to compile #5
Comments
What version of rust are you using? |
sagar.sakre@sagar-vm ~/rust-bin/bin $ ./rustc -v i couldn't clone binutils so i manually downloaded and compiled from |
I get the same error.
|
This fixes it zero.rs |
ryanra
referenced
this issue
in ryanra/RustOS
Jul 26, 2014
Good morning, It's taken a long time, but I finally am almost done freeing libsyntax of `vecs_implicitly_copyable` in this pull request, but I'm running into some issues. I've confirmed that all but the last commit (which only disables `vecs_implicitly_copyable` pass the `check` tests. The last commit errors with this message, which makes no sense to me: ``` /Users/erickt/rust/rust/src/libcore/num/f32.rs:35:37: 35:43 error: expected `,` but found `=` /Users/erickt/rust/rust/src/libcore/num/f32.rs:35 pub pure fn $name($( $arg : $arg_ty ),*) -> $rv { ^~~~~~ ``` and this stack trace: ``` #1 0x00000001000b059b in sys::begin_unwind_::_a923ca4ae164c::_06 () #2 0x00000001000b0542 in sys::begin_unwind::anon::anon::expr_fn_13876 () #3 0x00000001000048a1 in sys::begin_unwind::_8ec273289fc0adc0::_06 () #4 0x00000001005df999 in diagnostic::__extensions__::meth_7941::span_fatal::_efdf2d14612d79ec::_06 () #5 0x0000000100682d48 in parse::parser::__extensions__::meth_16938::fatal::_8aa3239426747a3::_06 () #6 0x00000001006850b8 in parse::common::__extensions__::meth_17005::expect::_d3604ec6c7698d5f::_06 () #7 0x00000001006b59f1 in parse::common::__extensions__::parse_seq_to_before_end_17860::_48c79835f9eb1011::_06 () #8 0x00000001006a50f7 in parse::parser::__extensions__::meth_17606::parse_fn_decl::_14f3785fe78967d::_06 () haileys#9 0x00000001006b6f59 in parse::parser::__extensions__::meth_17987::parse_item_fn::_8a6be529cf7b2ca5::_06 () haileys#10 0x00000001006ac839 in parse::parser::__extensions__::meth_17761::parse_item_or_view_item::_bfead947d6dd7d25::_06 () haileys#11 0x00000001006c8b8f in parse::parser::__extensions__::meth_18364::parse_item::_96b54e33f65abe76::_06 () haileys#12 0x000000010076179f in ext::tt::macro_rules::add_new_extension::generic_extension::anon::anon::expr_fn_23365 () haileys#13 0x000000010072e793 in ext::expand::expand_item_mac::_a4f486c4465cfb1b::_06 () haileys#14 0x00000001007b5ad3 in __morestack () ``` There also a bunch of new warnings that I haven't cleaned up yet: https://gist.github.com/erickt/5048251. @nikomatsakis thought there might be some scary bug in the parser caused by moving a vector in the parser instead of copying it, which is why I'm filing this pull request before it's ready. Thanks for any help!
ryanra
referenced
this issue
in ryanra/RustOS
Jul 26, 2014
terminfo parameterized strings supports a limited subset of printf-style formatting operations, such as %#5.3d.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I followed the steps given on README.md
After all the prerequisites I cloned the rustboot
exported all the PATH
$~ echo $PATH
/home/sagar.sakre/binutils/i386-elf/bin/:/home/sagar.sakre/binutils/bin/:/home/sagar.sakre/rust-bin/bin/:/opt/qemu/bin/4.4.3/bin/:/opt/qemu/bin/:/home/nithin/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
I got error while make..
sagar.sakre@sagar-vm ~ $ cd rustboot/
sagar.sakre@sagar-vm ~/rustboot $ ls
LICENSE.txt linker.ld loader.asm main.rs Makefile README.md runtime.asm zero.rs
sagar.sakre@sagar-vm ~/rustboot $ make
nasm -o loader.bin -f bin loader.asm
nasm -f elf32 -o runtime.o runtime.asm
rustc -O --target i386-intel-linux --lib -o main.o -c main.rs
error: no item found for
sized
error: aborting due to previous error
make: *** [main.o] Error 101
can you please tel me where I am goin wrong?
The text was updated successfully, but these errors were encountered: