On Mon, Nov 28, 2016 at 12:01:45PM -0800, Gerald Squelart wrote:
> On Tuesday, November 29, 2016 at 5:03:17 AM UTC+11, Gregory Szorc wrote:
> > > On Nov 27, 2016, at 14:46, Gerald Squelart <sque...@gmail.com> wrote:
> > >
> > >> On Saturday, November 26, 2016 at 3:59:05 AM UTC+11, Ralph Giles wrote:
> > >> On Fri, Nov 25, 2016 at 7:48 AM, Andrew Halberstadt
> > >> <ahalbe...@mozilla.com> wrote:
> > >>
> > >>> For anyone confused by this, the binaries are downloaded to ~/.cargo/bin
> > >>> and adding this directory to your $PATH should fix the issue. The
> > >>> bootstrapper explains this if you run it a second time, but makes no
> > >>> mention of it the first time through for some reason.
> > >>
> > >> Thanks. I've tried to address this in
> > >> https://bugzilla.mozilla.org/show_bug.cgi?id=1319860
> > >>
> > >> -r
> > >
> > > Hi Ralph,
> > >
> > > Following your instructions, rustc and friends are in ~/.cargo/bin, and 
> > > I've added that path in my $PATH.
> > >
> > > But now, `./mach build` gives me:
> > >  force-cargo-build
> > >  env: /usr/local/bin/cargo: No such file or directory
> > >  /mozilla-central/config/rules.mk:951: recipe for target 
> > > 'force-cargo-build' failed
> > >  gmake[2]: *** [force-cargo-build] Error 127
> > >  /mozilla-central/config/recurse.mk:71: recipe for target 
> > > 'toolkit/library/rust/target' failed
> > >  gmake[1]: *** [toolkit/library/rust/target] Error 2
> > >  gmake[1]: *** Waiting for unfinished jobs....
> > >
> > > Sym-linking rustc from /usr/local/bin worked, but it feels wrong!
> > 
> > This is a longstanding problem with the build system w.r.t. detected
> > programs changing out from under the build system: the build system
> > makes a lot of assumptions that the system doesn't change between
> > builds. If you do things like change the toolchain or where binaries
> > are installed, you'll need to perform a clobber build.
> 
> Ah yes, it worked after a clobber. Sorry, I should have tried that before.

Note, you probably didn't /actually/ need a clobber. It would probably
have fixed itself after re-running mach configure.

Mike
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to