Re: pkg/53671 (lang/rust build breaks on read-only source tree)

[triaxx <triaxx%triaxx.org@localhost>]

Le 2019-02-21 07:00, triaxx a écrit :
> The following reply was made to PR pkg/53671; it has been noted by 
> GNATS.
>
> From: triaxx <triaxx%triaxx.org@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc: he%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
>  hauke%netbsd.org@localhost, Hauke Fath <hf%spg.tu-darmstadt.de@localhost>
> Subject: Re: pkg/53671 (lang/rust build breaks on read-only source 
> tree)
> Date: Thu, 21 Feb 2019 06:52:28 +0100
>
>  Le 2019-02-19 16:48, hauke%NetBSD.org@localhost a écrit :
>  > Synopsis: lang/rust build breaks on read-only source tree
>  >
>  > State-Changed-From-To: feedback->closed
>  > State-Changed-By: hauke%NetBSD.org@localhost
>  > State-Changed-When: Tue, 19 Feb 2019 15:48:41 +0000
>  > State-Changed-Why:
>  > rust 1.32 builds fine -- even without mounted /proc.
>
>  I have just tried to build lang/rust 1.32 into a fresh sandbox without
>  mounted /proc and it failed.
>
>  [*** build log ***]
>
>  --- stderr
>  thread 'main' panicked at 'failed to get current_exe: 
> /proc/curproc/exe
>  doesn't point to regular file.'

I just notice that in my chrooted sandbox:
# ls -l /proc/curproc/exe
lr-xr-xr-x  1 root  wheel  1 Feb 21 07:14 /proc/curproc/exe -> /
# file /proc/curproc/exe
/proc/curproc/exe: symbolic link to /
# file /proc/curproc/exe/
/proc/curproc/exe/: directory

and out of my chrooted sandbox:
# ls -l /mnt/ccd0/sandbox/rust/proc/curproc/exe
lr-xr-xr-x  1 root  wheel  7 Feb 21 08:14 
/mnt/ccd0/sandbox/rust/proc/curproc/exe -> /bin/ls

So yes, /proc/curproc/exe is not a regular file into a chrooted 
environment. But I don't know if it is a problem from rust or from 
NetBSD...