Re: rust broken?

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_at_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_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>