Date: Thu, 7 Jun 2018 10:21:59 -0700 From: Matthew Macy <mat.macy@gmail.com> To: Alan Somers <asomers@freebsd.org> Cc: Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: rust broken? Message-ID: <CAPrugNpTN9mLK1chca6ovGojM_9iJBmRcYbSiFRivpr=2vKbVg@mail.gmail.com> In-Reply-To: <CAOtMX2hG2CDj0OZYG-VY6N-zcqkkZA9tQdB-D%2BvAaATAUwqZjQ@mail.gmail.com> References: <f7f4d873-5bf3-6dfa-fdf0-6922219b14e3@protected-networks.net> <CAOtMX2hG2CDj0OZYG-VY6N-zcqkkZA9tQdB-D%2BvAaATAUwqZjQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Rustup uses the 11 ABI. On Thu, Jun 7, 2018 at 10:11 Alan Somers <asomers@freebsd.org> wrote: > Can you reproduce the problem using rust installed from rustup instead of > from Ports? If so, you should file a bug report with the Rust developers. > Hint: when using Rustup, you'll have to use vresion 1.26.1 instead of > 1.26.0. > -Alan > > On Thu, Jun 7, 2018 at 9:44 AM, Michael Butler <imb@protected-networks.net > > > wrote: > > > In response to a Firefox update, I tried to build the new version. > > However, rust now fails with a core-dump in the build process. > > > > checking for libffi > 3.0.9... yes > > checking MOZ_FFI_CFLAGS... -I/usr/local/lib/libffi-3.2.1/include > > checking MOZ_FFI_LIBS... -L/usr/local/lib -lffi > > checking for rustc... /usr/local/bin/rustc > > checking for cargo... /usr/local/bin/cargo > > checking rustc version... > > DEBUG: Executing: `/usr/local/bin/rustc --version --verbose` > > DEBUG: The command returned non-zero exit status -12. > > DEBUG: Its output was: > > DEBUG: | rustc 1.26.0 > > DEBUG: | binary: rustc > > DEBUG: | commit-hash: unknown > > DEBUG: | commit-date: unknown > > DEBUG: | host: x86_64-unknown-freebsd > > DEBUG: | release: 1.26.0 > > ERROR: Command `/usr/local/bin/rustc --version --verbose` failed with > > exit status -12. > > > > Attempts to rebuild rust (and cargo) from the bootstrap files fail in > > similar fashion. > > > > On a machine running a SVN r334538 kernel but more recent user-land, it > > builds successfully. With (the only difference being) a kernel at SVN > > r334748, it does not. > > > > Any hints/thoughts? > > > > imb > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPrugNpTN9mLK1chca6ovGojM_9iJBmRcYbSiFRivpr=2vKbVg>