Bugzilla Bug 25366

erlang seems to run its own shell (eshell) during the build process,
but then fails when trying to allocate a terminal outside the sandbox.

Is there a workaround for that ?
I saw similar sandbox problems with apache long directory path and others,
but this one is more unique I think.
I'm running 2.4.20-gentoo-r5, portage-2.0.48-r7 and coreutils-5.0.

I get the following output:
...
ACCESS DENIED  open_wr:   /dev/pty/s1
Eshell V5.2.3.3  (abort with ^G)
1> erlc boot_linker.erl
erlc -W  -bbeam -W -I
/var/tmp/portage/erlang-9c-r1/work/otp_src_R9B-1/lib/stdlib/include -o./ ecc.erl
erlc -W  -bbeam -W -I
/var/tmp/portage/erlang-9c-r1/work/otp_src_R9B-1/lib/stdlib/include -o./ elink.erl
echo "compile:file(fake_demand_epp), halt()." | erl
ACCESS DENIED  open_wr:   /dev/pty/s1
Eshell V5.2.3.3  (abort with ^G)
1> echo "compile:file(fake_error_handler), halt()." | erl
ACCESS DENIED  open_wr:   /dev/pty/s1
Eshell V5.2.3.3  (abort with ^G)
1> echo "compile:file(fake_demand_init), halt()." | erl
ACCESS DENIED  open_wr:   /dev/pty/s1
Eshell V5.2.3.3  (abort with ^G)
1> echo "boot_tools:make_tools(), halt()." | erl -env ERL_BEAM_EVM
/var/tmp/portage/erlang-9c-r1/work/otp_src_R9B-1/bin/i686-pc-linux-gnu/beam_evm
ACCESS DENIED  open_wr:   /dev/pty/s1
Eshell V5.2.3.3  (abort with ^G)
1> done
done
...
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-erlang-9c-r1-1433.log"
                                                                               
                                                         
 open_wr:   /dev/pty/s1
 open_wr:   /dev/pty/s1
 open_wr:   /dev/pty/s1
 open_wr:   /dev/pty/s1
 open_wr:   /dev/pty/s1
 --------------------------------------------------------------------------------

`emerge info` please and tell me how you are connecting to the box ... 
are you running a terminal in X ?  ssh session ?  console ? 

I did emerge erlang from within a gnome terminal (XFree).
According to your hint, I tried compile on a console,
and IT WORKED ! Thx !

Maybe just add a comment to the ebuild ?

nah, i added a `addpredict` so that the ebuild will lie to erlang and tell
it that it wrote to the terminal when it really didnt ;)

thanks for the report