Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 115014 - et-etpro fails to load libGL.so.1
Summary: et-etpro fails to load libGL.so.1
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Games (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Gentoo Games
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-09 12:05 UTC by Mats Liljegren
Modified: 2005-12-09 12:42 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mats Liljegren 2005-12-09 12:05:54 UTC
I cannot start Enemy Territory, et-etpro. I'm using etpro version 3.2.4.


Reproducible: Always
Steps to Reproduce:
1.Issue command 'et-etpro'

Actual Results:  
$ et-etpro 
ET 2.60 linux-i386 Mar 10 2005
----- FS_Startup -----
Current search path:
/home/mats/.etwolf/etpro
/opt/enemy-territory/etpro/etpro-3_2_4.pk3 (101 files)
/opt/enemy-territory/etpro
/home/mats/.etwolf/etmain
/opt/enemy-territory/etmain/pak2.pk3 (22 files)
/opt/enemy-territory/etmain/pak1.pk3 (10 files)
/opt/enemy-territory/etmain/pak0.pk3 (3725 files)
/opt/enemy-territory/etmain/mp_bin.pk3 (6 files)
/opt/enemy-territory/etmain

----------------------
3864 files in pk3 files
execing default.cfg
couldn't exec language.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok

------- Input Initialization -------
Joystick is not active.
------------------------------------
Bypassing CD checks
----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
...loading libGL.so.1: QGL_Init: dlopen libGL.so.1 failed: libGL.so.1: cannot
open shared object file: No such file or directory
failed
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
----- CL_Shutdown -----
-----------------------
Sys_Error: GLimp_Init() - could not load OpenGL subsystem



Expected Results:  
Being able to shoot lots of soldiers...


I checked if I had the library:

$ whereis libGL.so.1          
libGL.so: /usr/lib/libGL.so.1
$ ls -l /usr/lib/libGL.so.1
lrwxrwxrwx  1 root root 27 Oct 26 20:43 /usr/lib/libGL.so.1 ->
/usr/X11R6/lib/libGL.so.1.2
$ ls -l /usr/X11R6/lib/libGL.so.1.2
-rw-r--r--  1 root root 1005257 Oct 26 20:43 /usr/X11R6/lib/libGL.so.1.2

Looks fine to me!

I tried "opengl-update xorg", no difference.

I have a fairly new install of Gentoo.
Comment 1 SpanKY gentoo-dev 2005-12-09 12:08:24 UTC
you neglected to post `emerge info` like the bug report page told you to

also, what does this show:
$ ls /var/db/pkg/app-emulation/
Comment 2 Chris Gianelloni (RETIRED) gentoo-dev 2005-12-09 12:24:13 UTC
Enemy Territory is not a 64-bit application, so files in /usr/lib won't be the
ones it needs/uses.  It sounds like you either are missing viable 32-bit
versions if your video drivers, such as what you would get with the ATI or
Nvidia binary drivers, or you haven't run opengl-update to setup your opengl
libraries.

What kind of video card do you have?  If it isn't one supported by the
Nvidia/ATI binary drivers, then it is not likely to ever work with any 32-bit
applications.  It will not work with any of the X-provided drivers.
Comment 3 Mats Liljegren 2005-12-09 12:29:18 UTC
First, here comes the "emerge info", sorry for not providing it before:

# emerge info
Portage 2.0.51.22-r3 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6
.12-rc3-vidalinux x86_64)
=================================================================
System uname: 2.6.12-rc3-vidalinux x86_64 AMD Athlon(tm) 64 X2 Dual Core Process
or 3800+
Gentoo Base System version 1.12.0_pre10
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X1
1/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/
distributions/gentoo"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/overlays/vlos"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X alsa audiofile avi berkdb bitmap-fonts bzip2 cdr crypt cups curl ed
s emboss encode esd exif expat fam foomaticdb fortran gif glut gnome gpm gstream
er gtk gtk2 hal howl imlib ipv6 java jpeg junit kde lcms lzw lzw-tiff mng mp3 mp
eg ncurses nls nptl nptlonly ogg opengl pam pdflib perl png python qt quicktime 
readline samba sdl slang spell ssl tcpd tiff truetype truetype-fonts type1-fonts
 udev usb userlocales vorbis xine xml2 xpm xv zlib userland_GNU kernel_linux eli
bc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

Here's the requested extra info:

# ls /var/db/pkg/app-emulation/
emul-linux-x86-baselibs-2.1.1  emul-linux-x86-glibc-1000   emul-linux-x86-xlibs-2.1
emul-linux-x86-compat-1.0      emul-linux-x86-gtklibs-2.1

As for driver, I use ATI 64-bit driver downloaded from ATI website. Do I have to
throw away this driver and use a 32-bit version?
Comment 4 SpanKY gentoo-dev 2005-12-09 12:31:31 UTC
since you installed the ati driver yourself, it's up to you to also take care
of installing a 32bit libGL

--> INVALID
Comment 5 Chris Gianelloni (RETIRED) gentoo-dev 2005-12-09 12:41:44 UTC
OK... This isn't a "bug" so much as a configuration issue on your part.

For one, dump the driver you got form ATI's site and use "emerge ati-drivers"
instead, as it installs botht he 64-bit and the 32-bit portions and sets up your
OpenGL properly.
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2005-12-09 12:42:41 UTC
Right.  This is INVALID in the sense that it is not a bug.  If you still need
help configuring your drivers after using the ebuild, try the forums.