Stoian Ivanov wrote: > On Monday 06 June 2005 18:24, Hans Hvelplund Odborg wrote: > >>I think this may happen if you're emerging in parallel (e.g. emerge started >>on >>two consoles) > > > Nope this is not the case: > [EMAIL PROTECTED] ~ # grep MAKEOPTS /etc/make.conf > MAKEOPTS="-j1" > [EMAIL PROTECTED] ~ # > > Besides, a colegue of mine has the same problem
while wondering why it's trying to access the floppy disk, you can try #FEATURES="-sandbox" emerge foo/bar This will disable the cage into which run emerge permitting access to the whole filesystem while emerging (long story too short). Please fill a bug explaining it, if this is the ebuild behaviour it need to be modified. [snip] >>>foomatic-printermap-to-gimp-print-xml mkinstalldirs >>>--------------------------- ACCESS VIOLATION SUMMARY >>>--------------------------- LOG FILE = >>>"/tmp/sandbox-net-print_-_foomatic-db-engine-3.0.2-13846.log" >>> >>>open_wr: /dev/fd/3 (symlink to /proc/14225/fd/3) >>> >> >>-------------------------------------------------------------------------------- >> >>>[EMAIL PROTECTED] ~ # >>> >>> -- .................................................................... . These pages are best viewed by coming to my house and looking at . . my monitor. [S. Lucas Bergman (on his website)] . .................................................................... -- gentoo-user@gentoo.org mailing list
