Hi,
Which is current state of once functions?
In the doc https://github.com/mozilla/rust/wiki/Doc-under-construction-FAQit
mentioned as experimental feature, which might not be enabled in 1.0.
But it is
Compiler shows a warning
___
Rust-dev mailing
;once functions are experimental and likely to
be removed", which raises question "how likely" considering wiki page was
last edited 9 months ago.
Is better to avoid them at all or it's still safe use them as
experimental feature?
--
Valerii
On Thu, May 1, 2014 at 11:1
Hi Christophe,
> i can not use :
> let ppDb : **mut () = RawPtr::null();
> unsafe { res=sqlite3_open(filename.as_ptr(), ppDb);
> because as_ptr() returns an *u8 and c_char is a i8, so i have to use
> extern { fn sqlite3_open(filename: *c_uchar, ppDb : **mut ()) ->
> c_int; }
as_ptr() is a bad i
I'm trying to run rustc on an arm board, but obviously there's no
precompiled stage0 to build the compiler.
Is there a procedure to cross-compile stage0 on other host machine where
I do have rustc?
Disclaimer: haven't tried anything like this, but just a couple of
hints:
- configure scr
Hi,
Being a big fan of offline documentation I've prepared a fresh docset
for Dash (zeal, helm-dash, any other compatible software).
Here is the link for subscription:
dash-feed://https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fnet.vhbit.rust-doc%2FRustNightly.xml
It's a beta and has a cou
Hi Vladimir,
> It removes the left side navigation panel from docs and adds TOC generation.
Looks nice, I've added TOC generation too (so far I'm not using
dash-rust and plan to publish the code after cleaning up a bit).
One of the reason is that dash-rust actually shows much more
informatio
Hi,
So finally Rust can cross-compile for iOS (armv7 only for now). BTW,
it also means that Rust now can be used both for iOS and Android
low-level development.
Short instructions are available here:
https://github.com/mozilla/rust/wiki/Doc-building-for-ios
Unfortunately LLVM patch for s
Hi Alex,
> The source also supports a number of other platforms such as Android and
> iOS now.
Unfortunately iOS build is failing now because of LLVM bug and as
patch for it hasn't yet landed, I believe it shouldn't be mentioned in
release notes.
--
Valerii
signature.asc
Description: O
Hi Rob,
> make: *** No rule to make target
> `powerpc64-bgq-linux/rt/arch/powerpc64/morestack.o', needed by
> `powerpc64-bgq-linux/rt/libsmorestack.a'. Stop.
>
> I don't know how to go about debugging this. Any ideas?
There is no way to "debug" this - you have to implement a couple of
func
Hi,
> Also when using the --target approach, I always had to wait for hours
> until it finished the Linux (host) build before it started to build
> the target.
Yep, `--target` approach can be extremely exhausting. One pretty
useful dirty trick in this case is to build it once for host and play
Hi Kashyap,
> I've used it here -
> https://github.com/ckkashyap/unix/blob/master/kernel/Makefile and it
> appears that the compiler does honor the contents of the json file
> that is passed.
Corey Richardson can help you with that.
--
Valerii
signature.asc
Description: OpenPGP digital
Hi Tomi,
> Anyone have any idea if that's a larger problem, or simply something
> nobody has written the small handcoded ASMs needed for ARMv5 or v4?
> If latter, I might be able to wrap my head around this.
The problem you've got is related to segmented stack support. It need
fix on 2 levels:
Hi Tom,
> Is anyone aware of work on a tool to automatically generate an FFI
> for C libraries?
https://github.com/crabtw/rust-bindgen
--
Valerii
signature.asc
Description: OpenPGP digital signature
___
Rust-dev mailing list
Rust-dev@mozilla.o
Hi Tomi,
> The prologue problem was fixed by adding "morestack: false," to the
> linux ARM target specification, similar to how it is in the iOS
> target.
Right, my bad, that should be enough.
> My device does not really benefit from the segmented stack, since it
> has only 64MB RAM
Segm
14 matches
Mail list logo
