> That is: stageN/bin contains everything needed-to-run stageN/bin, whereas > stageN/<arch>/lib contains everything needed-by-programs-produced-by stageN.
So far, so good. What I'm objecting to is using the libstd.so *distributed in the snapshot* to link with stage1/rustc. If we do a little creative directory shuffling, couldn't we make stage0/rustc link against a libstd.so other than stage0/lib/libstd.so, and have the make cycle start by building that lib from the current sources? That would already be enough to make extending the standard lib non-painful. The subject of this thread suggests I care about the actual paths, which is actually not what I was trying to get at. I just care about not being stuck depending on the stdlib from the last snapshot. _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
