[rust-dev] Building in Local Git Repo?

2014-12-29 Thread Tom Browder
I have a locally cloned fork of Rust. Is it okay to build in the top-level directory? Or is it better to build in a sub-directory or an out-of-repo directory? Thanks. Best regards, -Tom ___ Rust-dev mailing list Rust-dev@mozilla.org

Re: [rust-dev] Building in Local Git Repo?

2014-12-29 Thread Steve Klabnik
I always build in-tree, and it's fine. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev

Re: [rust-dev] Building in Local Git Repo?

2014-12-29 Thread Tom Browder
On Dec 29, 2014 11:38 AM, Steve Klabnik st...@steveklabnik.com wrote: I always build in-tree, and it's fine. Thanks. Maybe a note to that effect in the docs would be helpful--especially for someone coming from some popular repos that use CMake. Best regards, -Tom

Re: [rust-dev] Rust discourse visibility [Was: Tail call compatibility]

2014-12-29 Thread Paul Nathan
I have no desire to use Discourse, and nearly certainly won't sign up for it (I don't even understand why it came to be). I have never used Rust discourse besides happening once upon it and reading the linked thread. My membership in mailing lists is neatly sorted and segregated, easily readable

Re: [rust-dev] PDF Rust Docs

2014-12-29 Thread Tom Browder
On Dec 29, 2014 12:16 PM, Brian Anderson bander...@mozilla.com wrote: They used to be uploaded. I'm not sure why they stopped. Please file an issue. Will do. Thanks, Brian. -Tom ___ Rust-dev mailing list Rust-dev@mozilla.org

Re: [rust-dev] Rust discourse visibility [Was: Tail call compatibility]

2014-12-29 Thread Dmitry Romanov
I agree on almost every word. I have well sorted and with love configured mail, where I track several Libre projects. Now it is interesting to track rust questions. But dropping maillist most probably means I will not participate any more. I could add, as example, I have very limited Internet

Re: [rust-dev] Problems cross-compiling to ARM9

2014-12-29 Thread Tomi Pieviläinen
In the past when I've seen this error, it's because your C cross toolchain is built for a slightly wrong architecture. Can you verify that C programs cross compiled with your cross-gcc work correctly? Christmas is over, back to work. C works fine just by calling arm-linux-gnueabi-gcc. I hadn't

Re: [rust-dev] Rust discourse visibility [Was: Tail call compatibility]

2014-12-29 Thread Kevin Cantu
It's easy to set up discuss to email you all the time, too: give it a try. It had gotten pretty clear that having a catch-all mailing list wasn't going to scale. Kevin On Dec 29, 2014 10:57 AM, Dmitry Romanov romano...@gmail.com wrote: I agree on almost every word. I have well sorted and with

Re: [rust-dev] Rust discourse visibility [Was: Tail call compatibility]

2014-12-29 Thread Benjamin Herr
On Mon, 2014-12-29 at 13:02 -0800, Kevin Cantu wrote: It's easy to set up discuss to email you all the time, too: give it a try. That still loses you the thread structure of email discussion. I also can't start threads via the mail interface, and the mail interface regularly eats whole replies

Re: [rust-dev] Rust discourse visibility [Was: Tail call compatibility]

2014-12-29 Thread Tony Arcieri
On Mon, Dec 29, 2014 at 1:02 PM, Kevin Cantu m...@kevincantu.org wrote: It's easy to set up discuss to email you all the time, too: give it a try. I've set up Discourse this way. As a Gmail user, this is mostly fine as a mailing list replacement, but I can see (as a former mutt user) how mutt