Oh, ok, so this will be fixed? Any idea when? :-)
On Thu, Aug 22, 2013 at 2:44 PM, Brian Anderson <bander...@mozilla.com>wrote: > On 08/22/2013 02:04 PM, Vadim wrote: > >> When I try to use an extern function defined in another crate, >> (specifically, std::libc::funcs::extra::**kernel32::OpenProcess in my >> case), Rust seems to generate a direct call to that function, and then >> linking fails because of unresolved symbols. My expectation is that the >> call would go first to the wrapper inside std crate, which then calls the >> real OpenProces(). >> >> Am I getting this right? >> > > This is fallout from the new model for externs that I at least did not > anticipate. > ______________________________**_________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/**listinfo/rust-dev<https://mail.mozilla.org/listinfo/rust-dev> >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
