Date: Fri, 24 Jul 2020 15:51:03 +0000
From: bugzilla-noreply@freebsd.org
To: bugs@FreeBSD.org
Subject: [Bug 248184] readlink("/proc/curproc/file") returns arbitrary correct name for programs with more than one link (name)
Message-ID: <bug-248184-227-pVrFEFmJ6I@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-248184-227@https.bugs.freebsd.org/bugzilla/>
References: <bug-248184-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248184 --- Comment #5 from commit-hook@FreeBSD.org --- A commit references this bug: Author: tobik Date: Fri Jul 24 15:50:57 UTC 2020 New revision: 543251 URL: https://svnweb.freebsd.org/changeset/ports/543251 Log: 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/fil= e, 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 Changes: head/lang/rust-nightly/files/patch-src_bootstrap_lib.rs head/lang/rust-nightly/files/patch-src_bootstrap_native.rs --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248184-227-pVrFEFmJ6I>