||12-23-2012 04:06 AM
Error in Installing bluefish 2.2.3 on Slackware 14.0 (kernel 3.2.29)
I have issue when I am trying to install bluefish 2.2.3 on the latest Slackware 14.0 (with custom kernel 3.2.29). Basically I downloaded the Bluefish 2.2.3 tar file and after untar it I did ./configure and make, however the make failed with the following error:
make: Entering directory `/root/bluefish-2.2.3/src/plugin_about'
/bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/local/share/locale\" -DPKGDATADIR=\"/usr/local/share/bluefish\" -I. -I../../src -g -O2 -Wall -pipe -I/usr/include/python2.7 -MT about.lo -MD -MP -MF .deps/about.Tpo -c -o about.lo about.c
libtool: compile: gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/local/share/locale\" -DPKGDATADIR=\"/usr/local/share/bluefish\" -I. -I../../src -g -O2 -Wall -pipe -I/usr/include/python2.7 -MT about.lo -MD -MP -MF .deps/about.Tpo -c about.c -fPIC -DPIC -o .libs/about.o
about.c:22:21: fatal error: gmodule.h: No such file or directory
I have installed both glib-1.2.10 and glib2-2.32-4 so the gmodule.h exist in both /usr/include/glib-1.2 and /usr/include/glib-2.0 but somehow the compile command cannot find them. If I manually copy one of the gmodule.h to /usr/include, it seemed that the compiler could find it but it again stuck at some other missing header ( I think it was glib.h) So I don't think keep copying header files into /usr/include is the right solution here. So what am I missing here ? Is it the problem on my slackware system configuration ? or is it something wrong with the directive on the make file ? This is the first time I try to compile anything on this brand new slackware 14.0.