Hi
I want to install glib-devel-2.xx on suse 9 linux.
I downloaded from below site,
Index of /pub/gnome/sources/glib/2.24
and installed using normal configure,make,make install.
Am I correct or something else is required?
Thanks.
Usually you'd install using your distro's package manager instead of building from source unless there's an extremely good reason not to. Packages for your distro know where everything belongs, source tarballs are generic things which don't. 'make install' installed both headers and binaries, and may not have put them in the place your distro needs them in order to find them unless you picked your ./configure options carefully. You probably have the necessary header files now, but may have overwritten your glib binaries or installed extra copies somewhere else (check /usr/local/lib)
1 Like
Hello Corona688. thanks for quick reply.
actually I forgot to mention a couple of things. I'd like to keep the old version of glib-devel-1.2.10-586.2 and glib-devel-32bit-9-200501051723
These got installed using RPMS while OS was installed.
Someone requested for glib-devel-2.x version which was not installed. I thought I could install it using source without affecting any part of current system files and as a unique package in /usr/local which that user could make use of when wanted.
First thing I was confused because package on that website or even gnome ftp site is glib and NOT glib-devel. So, I hope the package 'glib' itself is correct. And, secondly now that I have installed glib-2.24.2 using default ./configure options, will it mess up any part of the system or it will still be compatible with old glib-devel?
Also, is there anyway to find using rpm command where glib-devel-1.2.x package files get installed. Meaning what all locations of file system.
Now that you said the installation from source might have overwritten old binaries or libraries, I am really concerned.
Below is make install log
http://pastebin.ca/1939860
Where it installs is controlled by what options you gave ./configure. Try ./configure --help if you're curious.
Most binary distros split packages into base and -dev versions to save space, since the headers, objects, etc. aren't needed to run the libraries and executables, just compile with them. They are needed to compile using the library, so they're optionally available.
Having built glib from source, there is no base and -dev package, just one source tarball. 'make install' installs everything, headers included. Usually, anyway. Not all makefiles are the same.
From the log it looks to have safetly installed everything under /usr/local, even the headers. Hooray for sane defaults. Your users ought to be able to use it there, though they'll need to give these extra header and library search paths the compiler and linker (and maybe point their executables to the right library paths by exporting LD_LIBRARY_PATH before running them).
1 Like
Many thanks. Your input was very informative.
Good day.