From: David S. <dsc...@vy...> - 2001-04-13 21:02:07
|
> It's hard for this bystander to comprehend how Linux users put up > with this! The problem isn't really the OS, but our pathetic packages. On Windows, the (fairly complex) job of installing shared libraries, registry entries, etc for Python, OpenGL, Tcl/Tk, cvisual, etc is handled by the Python 2.0 installer and our own. On Linux distributions, it should be handled by the package manager, based on dependency information in the packages. Unfortuantely, Ari is trying to build rpm packages without access to a Red Hat-like distribution, which is impossible. Everyone else is therefore trying to do things like compile from source, which is about as painful as you would expect. The only thing hard to understand is that anyone likes VPython enough to put up with this ;) > These dialogs sound like bad jokes. That's just because you aren't used to the particular jargon being used, so that /usr/lib/libgtkgl.so.4 sounds slightly "worse" to your ears than, say, c:\windows\system\opengl32.dll. These problems don't seem a lot worse than the installation headaches that forced us to build our own Python distribution for 1.5.2. What is desperately needed to fix this is someone with a Red Hat system, and the time and minimal expertise required to build packages. I would also advocate static linking against a few things like libstdc++ if possible, even though that goes against normal practice on Linux. Dave > --On Thursday, April 12, 2001 20:13 -0400 Ari Heitner > <ahe...@an...> wrote: > > > On Thu, Apr 12, 2001 at 04:26:14PM -0700, Gary Huber wrote: > >> Yeah, mine also has glXUseXFont, according to the nm command. It also > >> works fine in my C++ code. I have Mesa 3.4-1. In addition to being in > >> /usr/X11R6/lib, I've copied libGL.so to /usr/lib and /usr/local/lib, to > >> no avail. > >> > > Ok. Then do an > > ldd /usr/lib/libgtkgl.so.4 > > (or whatever version of libgtkgl you have cvisualmodule.so linked > > against). are all the dependencies resolved? your libGL.so must be in a > > dir that's in /etc/ld.so.conf ... |