notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
All times are UTC
non port: lang/rust-nightly/files/

Number of commits found: 2

Sun, 31 Oct 2021
[ 18:20 Tobias Kortkamp (tobik) search for other commits by this committer ]    commit hash:d5f09dc31fcfdb77b69c86b9093bf67ec67653d9  commit hash:d5f09dc31fcfdb77b69c86b9093bf67ec67653d9  commit hash:d5f09dc31fcfdb77b69c86b9093bf67ec67653d9  d5f09dc 
lang/rust-nightly: Update to

Make the no-hardlinks-patches conditional and move them to

Newer kernels should return sane kern.proc.pathname values for
hardlinks which will hopefully help avoid the intermittent "can't
find crate for `std`" build failures we had on the package

Thanks to kib@ for fixing kernel behavior. Now let's see if it
makes a difference for lang/rust-nightly.

PR:		248184
Fri, 24 Jul 2020
[ 15:50 tobik search for other commits by this committer ] Original commit   Revision:543251
lang/rust-nightly: Attempt to fix intermittent "can't find crate for `std`"
build failures

The location of rustc (found via env::current_exe()) is used to
find the right libstd.  However it might have been "copied" by
creating a hard link to the new location instead.  Like /proc/curproc/file,
KERN_PROC_PATHNAME (used internally by current_exe()) can return
any of the file's multiple paths.  Most of the time it returns the
right rustc path and the build will succeed but occasionally it
will return the "wrong" path and the build fails with:

    error[E0463]: can't find crate for `std`

If this is right a viable workaround should be to never create hard
links during the build, so let's try that.

Also drop the related llvm-config-wrapper workaround.

PR:		248184

Number of commits found: 2