I'm on a Solaris Sun 10 box and I'm trying to install syslog-ng-2.0.9
and I keep getting this error whenever I run ./configure:

configure: error: Glib headers inconsistent with current compiler
setting. You might be using 32 bit Glib with a 64 bit compiler, check
PKG_CONFIG_PATH

I just installed Glib-2.18.0 as well as pkg-config-0.20. I'm not sure
how to tell what bit program I am using, though, and/or how to change
it. I'm still fairly new to the Unix world, so please forgive the
ignorance....

Jamen McGranahan

Jamen <jmcgranahan@gmail.com> wrote:
> I'm on a Solaris Sun 10 box and I'm trying to install syslog-ng-2.0.9
> and I keep getting this error whenever I run ./configure:

> configure: error: Glib headers inconsistent with current compiler
> setting. You might be using 32 bit Glib with a 64 bit compiler, check
> PKG_CONFIG_PATH

> I just installed Glib-2.18.0 as well as pkg-config-0.20. I'm not sure
> how to tell what bit program I am using, though, and/or how to change
> it. I'm still fairly new to the Unix world, so please forgive the
> ignorance....

Yeah, something is a bit screwy with the configure on it, easiest way to
build it is...

# PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ; export PKG_CONFIG_PATH
# ./configure --enable-dynamic-linking
# make

Although that glib stuff should be found after declaring the pkg path,
something just doesn't see it. Using that --enable-dynamic-linking gets rid
of the error, builds and runs fine.

Also after it's built and before doing "make install", type this:

# ldd src/syslog-ng

and make sure nothing is pointing to "not found".

This is just another of the "Solaris doesn't use /usr/local" nonsense
defects. It seems to build fine on every other platform without voodoo.

Good luck if you ever have to add in perl modules via cpan, heh.

-bruce
bje@ripco.com

> # PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ; export PKG_CONFIG_PATH
> # ./configure --enable-dynamic-linking

I tried this, but got the same error - configure: error: Glib headers
inconsistent with current compiler setting. You might be using 32 bit
Glib with a 64 bit compiler, check PKG_CONFIG_PATH

> # make

This just gives me the following message:
make: *** No targets specified and no makefile found. Stop.

I did check my environment variable to make sure I set it correctly:
CC=gcc
CPPFLAGS=-I/usr/local/BerkeleyDB.4.2/include -I/usr/local/ssl/include
ENV=~/.kshrc
HOME=/
HZ=
LANG=C
LDFLAGS=-L/usr/local/lib -L/usr/local/BerkeleyDB.4.2/lib -R/usr/local/
BerkeleyDB.4.2/lib
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/lib:/sirsi/oracle/product/
102/lib32:/usr/local/BerkeleyDB.4.2/lib:/usr/local/ssl/lib
LOGNAME=root
MAIL=/var/mail/root
MANPATH=/usr/opt/SUNWmd/man:/usr/kerberos/man:/usr/man:/usr/dt/man:/
usr/openwin/man:/usr/local/man
OPENWINHOME=/usr/openwin
PATH=/usr/local/ssl/bin:/usr/local/bin:/usr/bin/nsr:/usr/opt/SUNWmd/
sbin:/usr/kerberos/bin:/opt/SUNWspro/bin:/usr/bin:/usr/sbin:/usr/ccs/
bin:/usr/dt/bin:/usr/openwin/bin:/usr/ucb:/usr/local/bin:.:/opt/ssl/
bin:/usr/sfw/bin:/opt/hpnp/bin:/opt/hpnp/admin:/opt/hpnpl/bin:/opt/
hpnpl/admin
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
SHELL=/sbin/sh
TERM=vt100
TZ=US/Central
VISUAL=vi

What else can I check?

Jamen

Jamen <jmcgranahan@gmail.com> wrote:

>> # PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ; export PKG_CONFIG_PATH
>> # ./configure --enable-dynamic-linking

> I tried this, but got the same error - configure: error: Glib headers
> inconsistent with current compiler setting. You might be using 32 bit
> Glib with a 64 bit compiler, check PKG_CONFIG_PATH

>> # make

> This just gives me the following message:
> make: *** No targets specified and no makefile found. Stop.

Well yeah, if configure didn't finish without errors, there is no Makefile
yet.

Honestly, some of your environment is a little scary, but one thing before
re-inventing the wheel, there is a package for syslog-ng v2.0.9 on
sunfreeware.com, you just download it and run pkgadd. You didn't say if you
were trying to build it on sparc or x86, but both are there.

Unless you needed to do something special with it, I'm sure the
drop-in-and-run copy from there will get you going.

But really, some things in your environment are wrong and in some cases
dangerous (so to speak). I don't know if you can start clean or if some of
those things like the PATH are being loaded from a profile somewhere, but
it's not syslog-ng that is the problem in this case.

Maybe you need all that stuff defined and in that order for some reason but
with things like this, you really have a hair-pulling session.

-bruce
bje@ripco.com