Re: installing
- From: John Cupitt <john cupitt ng-london org uk>
- To: "Witt, Richard" <Richard Witt TTMC TTUHSC EDU>
- Cc: "'gtk-list gnome org'" <gtk-list gnome org>
- Subject: Re: installing
- Date: Thu, 15 Jun 2000 11:06:09 +0100
"Witt, Richard" wrote:
> I have unzipped it and
> ran then ./configure then make then make install. Then i tried doing the
> same with the gtk+ and when i run the configure i run into an error that
> says:
>
> Could not run GLIB test program, checking why.....
> The test program compiled, but did not run. This usually means that the
> run-time linker is not finding GLIB or finding the wrong version GLIB. If
> it is not finding GLIB, you'll need to set your LD_LIBRARY_PATH environment
> variable, or edit/etc/ld.so.conf to point to installed location. Also make
> sure you have run ldonfig if that is required on your system.
Hi Richard,
The problem is probably that the gtk+ you removed was installed in
/usr/lib, and by default configure puts gtk+ into /usr/local/lib. You
system is not set up to look in /usr/local/lib, so it can't find the
library.
There are several ways to fix this, the easiest is to change your system
to that it knows to look in /usr/local/lib for libraries. Take a look at
/etc/ld.so.conf ... this file lists all the directories that will be
searched for libraries by default. Add "/usr/local/lib" to the bottom,
and run the command "ldconfig" to rebuild the library cache. You'll need
to do this as root.
If you don't want to mess with your system set up (probably sensible),
as an alternative, you can add /usr/local/lib to your personal
LD_LIBRARY_PATH environment variable. This environment variable lists
directories which will be searched in addition to the directories listed
in /etc/ld.so.conf when looking for libraries.
Edit the file ".bashrc" in your home directory, and search for
LD_LIBRARY_PATH. It may well not be there at all, it depends on your
linux. Whether it's there to start with or not, after editing you need a
line like:
export LD_LIBRARY_PATH=old-stuff:/usr/local/lib
So append /usr/local/lib to it. Separate directories with ":"
characters. Don't use any whitespace, and don't break into several
lines.
Second, you need to add /usr/local/bin to your path (if it's not there).
Look at the file ".bashrc" in your home directory (this is as you now,
not as root). You should see a line something like:
export PATH= ... lots of stuff
Append /usr/local/bin to this. Directories in PATH are separated with
":" characters, so aim for something along these lines:
export PATH=/bin:/usr/bin:/usr/local/bin
Now quit and restart your shells to make them reread the ".bashrc" files
(or type "source ~/.bashrc"), and try configure again. Congratulations!
You are now a linux hacker.
Hope this helps,
John
--
John Cupitt, john.cupitt@ng-london.org.uk, +44 (0)20 7747 2570
VASARI Lab, The National Gallery, Trafalgar Square, London, WC2N 5DN
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]