55859 – amd64 emerge openoffice-bin-1.1.2 fails without -sandbox

Bug 55859 - amd64 emerge openoffice-bin-1.1.2 fails without -sandbox

Summary: amd64 emerge openoffice-bin-1.1.2 fails without -sandbox

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Unspecified (show other bugs)
Hardware:	AMD64 Linux

Importance:	High normal (vote)
Assignee:	Gentoo Office Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-07-02 01:36 UTC by Steve Herber
Modified:	2004-07-02 06:12 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Steve Herber 2004-07-02 01:36:39 UTC

Trying to emerge openoffice-bin-1.1.2 fails with an error about unable to load /lib/libsandbox.so.  This reminded me that I had installed openoffice-bin-1.1.1 using the amd64 tech notes about.  The current version of the tech notes no longer have the suggestion.  A cached google page, http://www.gentoo.org/proj/en/base/amd64/technotes.xml?part=2&chap=3, included the hint.

Reproducible: Always
Steps to Reproduce:
1.ACCEPT_KEYWORDS=~amd64 /usr/bin/emerge openoffice-bin - fails
2.ACCEPT_KEYWORDS=~amd64 FEATURES="-sandbox" /usr/bin/emerge openoffice-bin - works
3.

Actual Results:  
The normal install fails each time with the error unable to load /lib/libsandbox.so


Expected Results:  
Either the amd64 tech notes should be restored to use FEATURES="-sandbox"
or
the ebuild should do it automatically.

 emerge info
Portage 2.0.50-r8 (default-amd64-2004.0, gcc-3.3.3, glibc-2.3.4.20040605-r0,
2.6.7-gentoo-r6)
=================================================================
System uname: 2.6.7-gentoo-r6 x86_64 4
Gentoo Base System version 1.5.1
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2"
CHOST="x86_64-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://mirror.tucdemonic.org/gentoo
ftp://ftp.mirrors.ussg.iu.edu/pub/linux/gentoo/  http://mirror.datapipe.net/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa amd64 apache2 apm avi berkdb cdr crypt cscope cups dvd dvdr encode
esd flac foomaticdb gdbm gif gnome gpm gtk gtk2 imlib joystick jpeg kde libg++
libwww lirc mad matroska mikmod motif mozilla mpeg mysql ncurses net nogcj
nvidia oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime
readline sdl slang spell ssl tcltk tcpd tiff transcode truetype usb xinerama
xml2 xmms xv zlib"

Comment 1 Travis Tilley (RETIRED) gentoo-dev

2004-07-02 06:12:26 UTC

it's a known limitation... either fix your system by doing 'FEATURES="-sandbox" USE="-gcj multilib" emerge gcc portage' to get a 32bit sandbox, or disable sandbox.

as for documentation, this limitation is mentioned in our errata last i knew and has been since i started using gentoo on amd64. i'll check again once www.gentoo.org is back up, but i'm pretty sure it's still there.