* [gentoo-user] emerge swt failed: cannot find -lGL
@ 2006-10-18 1:25 Iain Buchanan
2006-10-18 1:53 ` Iain Buchanan
0 siblings, 1 reply; 4+ messages in thread
From: Iain Buchanan @ 2006-10-18 1:25 UTC (permalink / raw
To: gentoo-user
Hi all,
I was just performing a routing update recently, and swt failed with
this error:
* Building OpenGL component
cc -O -Wall -DSWT_VERSION=3232 -DLINUX -DGTK
-I/opt/blackdown-jdk-1.4.2.03/include
-I/opt/blackdown-jdk-1.4.2.03/include/linux -fPIC -c glx.c
cc -O -Wall -DSWT_VERSION=3232 -DLINUX -DGTK
-I/opt/blackdown-jdk-1.4.2.03/include
-I/opt/blackdown-jdk-1.4.2.03/include/linux -fPIC -c glx_structs.c
cc -O -Wall -DSWT_VERSION=3232 -DLINUX -DGTK
-I/opt/blackdown-jdk-1.4.2.03/include
-I/opt/blackdown-jdk-1.4.2.03/include/linux -fPIC -c glx_stats.c
cc -shared -fPIC -shared -fPIC -L/usr/X11R6/lib -lGL -lGLU -lm -o
libswt-glx-gtk-3232.so swt.o glx.o glx_structs.o glx_stats.o
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lGL
collect2: ld returned 1 exit status
make: *** [libswt-glx-gtk-3232.so] Error 1
!!! ERROR: dev-java/swt-3.2-r2 failed.
Call stack:
ebuild.sh, line 1568: Called dyn_compile
ebuild.sh, line 937: Called src_compile
swt-3.2-r2.ebuild, line 141: Called die
!!! Unable to build OpenGL component
!!! If you need support, post the topmost build error, and the call
stack if relevant.
now, I've had "cannot find -l<blah> before, and a revdep-rebuild or
something usually fixes it. In this case however, I couldn't get around
it.
I have been swapping between xorg's x11-drm radeon driver, and ATI's
fglrx driver recently - but I've used eselect correctly - I'm now using
the x11-drm driver.
I don't know what to look at next - any hints?
thanks,
--
Iain Buchanan <iaindb at netspace dot net dot au>
Familiarity breeds contempt -- and children.
-- Mark Twain
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] emerge swt failed: cannot find -lGL
2006-10-18 1:25 [gentoo-user] emerge swt failed: cannot find -lGL Iain Buchanan
@ 2006-10-18 1:53 ` Iain Buchanan
2006-10-18 8:04 ` Bo Ørsted Andresen
0 siblings, 1 reply; 4+ messages in thread
From: Iain Buchanan @ 2006-10-18 1:53 UTC (permalink / raw
To: gentoo-user
On Wed, 2006-10-18 at 10:55 +0930, Iain Buchanan wrote:
> Hi all,
>
> I was just performing a routing update recently, and swt failed with
> this error:
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lGL
I worked around it by doing this:
$ cd /usr/lib
$ sudo ln -s /usr/lib/opengl/ati/lib/libGL.so
but I don't know that this is the right thing to do - how do I tell if
it actually works like this?
thanks,
--
Iain Buchanan <iaindb at netspace dot net dot au>
FLASH!
Intelligence of mankind decreasing.
Details at ... uh, when the little hand is on the ....
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] emerge swt failed: cannot find -lGL
2006-10-18 1:53 ` Iain Buchanan
@ 2006-10-18 8:04 ` Bo Ørsted Andresen
2006-10-18 11:54 ` Iain Buchanan
0 siblings, 1 reply; 4+ messages in thread
From: Bo Ørsted Andresen @ 2006-10-18 8:04 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Wednesday 18 October 2006 03:53, Iain Buchanan wrote:
[SNIP]
> I worked around it by doing this:
> $ cd /usr/lib
> $ sudo ln -s /usr/lib/opengl/ati/lib/libGL.so
>
> but I don't know that this is the right thing to do - how do I tell if
> it actually works like this?
[SNIP]
# eselect opengl set ati
Switching to ati OpenGL interface... done
# readlink /usr/lib/libGL.so
/usr/lib/opengl/ati/lib/libGL.so
# eselect opengl set xorg-x11
Switching to xorg-x11 OpenGL interface... done
# readlink /usr/lib/libGL.so
/usr/lib/opengl/xorg-x11/lib/libGL.so
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] emerge swt failed: cannot find -lGL
2006-10-18 8:04 ` Bo Ørsted Andresen
@ 2006-10-18 11:54 ` Iain Buchanan
0 siblings, 0 replies; 4+ messages in thread
From: Iain Buchanan @ 2006-10-18 11:54 UTC (permalink / raw
To: gentoo-user
On Wed, 2006-10-18 at 10:04 +0200, Bo Ørsted Andresen wrote:
> On Wednesday 18 October 2006 03:53, Iain Buchanan wrote:
> [SNIP]
> > I worked around it by doing this:
> > $ cd /usr/lib
> > $ sudo ln -s /usr/lib/opengl/ati/lib/libGL.so
> >
> > but I don't know that this is the right thing to do - how do I tell if
> > it actually works like this?
> [SNIP]
>
> # eselect opengl set ati
> Switching to ati OpenGL interface... done
>
> # readlink /usr/lib/libGL.so
> /usr/lib/opengl/ati/lib/libGL.so
>
> # eselect opengl set xorg-x11
> Switching to xorg-x11 OpenGL interface... done
>
> # readlink /usr/lib/libGL.so
> /usr/lib/opengl/xorg-x11/lib/libGL.so
$ sudo eselect opengl set ati
Switching to ati OpenGL interface... done
$ readlink /usr/lib/libGL.so
/usr/lib/opengl/ati/lib/libGL.so
looks fine.
$ sudo eselect opengl set xorg-x11
Switching to xorg-x11 OpenGL interface... done
$ readlink /usr/lib/libGL.so
$ <nothing returned>
looks wrong!
I did a bit of snooping, and found that libGL.so comes from mesa, so I
re-merged mesa (media-libs/mesa-6.5.1-r1) and it seems to be working
again:
$ readlink /usr/lib/libGL.so
/usr/lib/opengl/xorg-x11/lib/libGL.so
now, can googleearth work with mesa? it seems to lock-up at the splash
screen...
thanks!
--
Iain Buchanan <iaindb at netspace dot net dot au>
The good oxymoron, to define it by a self-illustration, must be a
planned inadvertency. -Wilson Follett
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-10-18 12:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-18 1:25 [gentoo-user] emerge swt failed: cannot find -lGL Iain Buchanan
2006-10-18 1:53 ` Iain Buchanan
2006-10-18 8:04 ` Bo Ørsted Andresen
2006-10-18 11:54 ` Iain Buchanan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox