David A. Bandel babbled on about: > run locate glib.h. If it's on your system, then the build software can't > find it. You may need to modify your make file, find the line with the > other -I/path/to/includes and put another -I/path/to/glib.h in. If glib.h > is not on your system, you need the glib-devel-* and gtk-devel-* RPMs (at > least, possibly even the gnome-devel-* RPMs).
you might also check that glib-config has the correct path info. sometimes you can have more than one copy of this file lying around and whichever is "found" first in the path wins.. -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 Admin: Linux StepByStep - http://linux.nf printk("CPU[|d]: Sending penguins to jail...",smp_processor_id()); 2.4.8 arch/sparc64/kernel/smp.c _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
