Re: [gentoo-dev] ncurses and sandbox

[Geert Bevin]

Hi,

I checked this and it's almost 100% sure that this is due to your bash
being the default portage bash. In fact for the sandbox to work fully,
bash should be linked dynamically instead of of statically. Then you get
these errors instead :

------------------------ ACCESS VIOLATION SUMMARY-----------------------
LOG FILE = "/tmp/sandbox19055.log"

open_wr:   /usr/tmp/conftest9012345
open_wr:   /usr/tmp/conftest9012346
-------------------------------------------------------------------------

and it never arrives at the unlink stage.

The package should be checked though why this is happening.

Geert.

On Wed, 2001-12-05 at 20:27, Grant Goodyear wrote:
> I started to build a new system, and I decided to sandbox the
> entire build.  I emerged sys-apps/sandbox _before_ even the bootstrap
> step, I commented out the portage build in scripts/bootstrap.sh, and
> I started the bootstrap.  Surprisingly, it seems that the ncurses
> configure script creates files outside of ${D}:
>
> --------------------------- ACCESS VIOLATION SUMMARY ---------------------------LOG FILE = "/tmp/sandbox14465.log"
>
> unlink:    /usr/tmp/conftest9012345
> unlink:    /usr/tmp/conftest9012346
> unlink:    /usr/lib/conftest9012345
> unlink:    /usr/lib/conftest9012346
> --------------------------------------------------------------------------------
>
> I took a look at the configure script, and it seems that the
> ac_sys_long_file_names test writes (and then afterwards unlinks)
> files in /usr/tmp and /usr/lib.  Any suggestions?  (Also, it appears
> that the sandbox allows those conftest* files to be installed, but
> not unlinked.  Is that what was wanted?)
>
> -g2boojum-
-- 
Geert Bevin
the Leaf sprl/bvba
"Use what you need"           Pierre Theunisstraat 1/47
http://www.theleaf.be         1030 Brussels
gbevin@×××××××.be             Tel & Fax [phone]