09-13-2010
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)
Last edited by Corona688; 09-13-2010 at 02:06 PM..
This User Gave Thanks to Corona688 For This Post:
6 More Discussions You Might Find Interesting
1. Programming
I have a question on how to make an rpm out of the source package distribution. just looking for a general procedure. Like say I have the MIT kerberos source, would I "make -C libs" or something like that? (2 Replies)
Discussion started by: thmnetwork
2 Replies
2. Solaris
I am trying to install Postfix on a Sun SPARC Solaris 9 server. I am not sure whether it is essential or not but still installed MySQL on that server and it is running fine.Now when I am trying to run the make command as a part of installation of Postfix, it reports the following error.
# make ... (1 Reply)
Discussion started by: chrs0302
1 Replies
3. Red Hat
Hi there,
I am using redhat 7.3 and I am trying to install openssl-devel-0.9.6b-18.i386.rpm but I get the following error message when I try to install:
error: failed dependencies:
openssl = 0.9.6b-18 is needed by openssl-devel-0.9.6b-18
The thing that confuses me most is that when I... (0 Replies)
Discussion started by: redhat_newb101
0 Replies
4. Solaris
Hi,
I have downloaded the glib 2.14.1 package from sunfreeware.com and installed it with pkgadd. However, glib-config --version shows the old version which is 1.2.10. I tried using crle but it just blew stuff up. I also tried glib-config --prefix=/usr/local but it doesn't seem to stick. I need... (2 Replies)
Discussion started by: cshore
2 Replies
5. Red Hat
my os is
# cat /etc/redhat-release
CentOS release 6.4 (Final)
from Pinoyden Blog: configure: error: mcrypt.h not found. Please reinstall libmcrypt.
# rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
Retrieving... (1 Reply)
Discussion started by: jediwannabe
1 Replies
6. Programming
hi all,
i use yum install qt-devel qt-doc qt-creator to install qt4 on fedora 20
what command line used to install qt5 (1 Reply)
Discussion started by: cetu
1 Replies
LEARN ABOUT CENTOS
glib-compile-schemas
GLIB-COMPILE-SCHEM(1) User Commands GLIB-COMPILE-SCHEM(1)
NAME
glib-compile-schemas - GSettings schema compiler
SYNOPSIS
glib-compile-schemas [OPTION...] {DIRECTORY}
DESCRIPTION
glib-compile-schemas compiles all the GSettings XML schema files in DIRECTORY into a binary file with the name gschemas.compiled that can
be used by GSettings. The XML schema files must have the filename extension .gschema.xml. For a detailed description of the XML file
format, see the GSettings documentation.
At runtime, GSettings looks for schemas in the glib-2.0/schemas subdirectories of all directories specified in the XDG_DATA_DIRS
environment variable. The usual location to install schema files is /usr/share/glib-2.0/schemas.
In addition to schema files, glib-compile-schemas reads 'vendor override' files, which are key files that can override default values for
keys in the schemas. The group names in the key files are the schema id, and the values are written in serialized GVariant form. Vendor
override files must have the filename extension .gschema.override.
By convention, vendor override files begin with nn_ where nn is a number from 00 to 99. Higher numbered files have higher priority (eg: if
the same override is made in a file numbered 10 and then again in a file numbered 20, the override from 20 will take precedence).
OPTIONS
-h, --help
Print help and exit
--targetdir=TARGET
Store gschemas.compiled in the TARGET directory instead of DIRECTORY.
--dry-run
Don't write gschemas.compiled. This option can be used to check .gschema.xml sources for errors.
--allow-any-name
Do not enforce restrictions on key names. Note that this option is purely to facility the transition from GConf, and will be removed at
some time in the future.
GIO
GLIB-COMPILE-SCHEM(1)