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

main.rs is unable to compile #7

Open
coder543 opened this issue Jul 5, 2013 · 4 comments · Fixed by #8
Open

main.rs is unable to compile #7

coder543 opened this issue Jul 5, 2013 · 4 comments · Fixed by #8

Comments

@coder543
Copy link

coder543 commented Jul 5, 2013

When running make, it spits out this error message.

rustc -O --target i386-intel-linux --lib -o main.o -c main.rs
error: no item found for `ty_desc`
error: no item found for `opaque`
error: no item found for `ty_visitor`
error: no item found for `freeze`
error: no item found for `send`
error: no item found for `closure_exchange_malloc`
error: aborting due to 6 previous errors
make: *** [main.o] Error 101

It seems dependent on some part of the rust runtime? maybe?

I'm running rustc version 0.7

rustc 0.7
host: x86_64-apple-darwin

any tips you can give?
@pczarn
Copy link
Contributor

pczarn commented Jul 7, 2013

It seems that new lang items were added and some were renamed. For example:
https://github.com/thestinger/rust/commit/4a29d6eb3f20c2b7a05bb9c9c2f964da606e39ca
rust-lang/rust#6962

Here's a quick fix. Some parts may be excessive.

@haileys
Copy link
Owner

haileys commented Jul 7, 2013

@pczarn if you open a PR for that commit I'll merge it

@pczarn pczarn mentioned this issue Jul 7, 2013
Merged
@coder543
Copy link
Author

coder543 commented Jul 7, 2013

Thanks! with these changes, it now compiles and runs!

But I'm curious, do these feature implementation stubs negatively impact Rust in any way? closure_exchange_malloc in particular seems important to not be stubbed out... but I'm new to this whole Rust thing, so I'm not an expert by any means.

@pczarn
Copy link
Contributor

pczarn commented Jul 9, 2013

I'm not an expert either. To begin with, malloc is unimplemented anyway. I think we don't use features that may require dynamic allocation.

ryanra referenced this issue in ryanra/RustOS Jul 26, 2014
@bors
auto merge of #5143 : erickt/rust/incoming, r=pcwalton
afdd0b8 
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!
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

Successfully merging a pull request may close this issue.

Add implementation of new lang items pczarn/rustboot
3 participants
@haileys @coder543 @pczarn