Post New Topic  Post A Reply
my profile | register | search | faq | forum home
  next oldest topic   next newest topic
» MacOSX - forked.net   » Compile Problems   » glib 1.2.10

UBBFriend: Email this page to someone!    
Author Topic: glib 1.2.10
psyba
Junior Member
Member # 193

posted October 26, 2001 04:54 PM      Profile for psyba   Email psyba   Send New Private Message      Edit/Delete Post  Reply With Quote 
While trying to compile GAIM, I needed to get GTK and Glib, but the ones here aren't really working for me... So i am trying to compile the latest builds myself. I get GTK to compile fine if I skip the glib test with the glib binary here, but I get some error about -ldl that installs with glib? when trying to compile GAIM and with GTK with the glib test? Anyways, i get this error when I 'make' glib:

code:
 /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=g_log_domain_glib     -g -O2 -Wall  -c giounix.c
gcc -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=g_log_domain_glib -g -O2 -Wall -c giounix.c -o giounix.o
giounix.c:1317: bad macro argument list
cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode
make[2]: *** [giounix.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 2

what the hell is this I've been trying to get tons of help with this, someone said it might have somethign to do with m4.... I don't know, but plz help, thanks


Posts: 14 | From: Lewiston, Maine | Registered: Oct 2001  |  IP: Logged
psyba
Junior Member
Member # 193

posted October 26, 2001 05:01 PM      Profile for psyba   Email psyba   Send New Private Message      Edit/Delete Post  Reply With Quote 
gah, damn back button, sorry, i just saw the 1.2.10 glib here, but still... how did you get it to compile, or what is up with that error?
Posts: 14 | From: Lewiston, Maine | Registered: Oct 2001  |  IP: Logged
JCPowers21
Junior Member
Member # 208

posted November 03, 2001 02:17 PM      Profile for JCPowers21   Email JCPowers21   Send New Private Message      Edit/Delete Post  Reply With Quote 
Delete config.cache then whenever you configure it use this:

setenv CFLAGS -no-cpp-precomp ; ./configure

If you use that it will configure, make, then install fine. I like using the setenv better than editing each makefile and changing the cflags. Sometimes makefiles don't even have the spot for cflags so you have to configure it the way I showed above.

Justin


Posts: 2 | From: Indiana | Registered: Nov 2001  |  IP: Logged

All times are Pacific Time  

Post New Topic  Post A Reply Close Topic    Move Topic    Delete Topic next oldest topic   next newest topic
Hop To:

Contact Us | macosx.forked.net

Powered by Infopop Corporation
Ultimate Bulletin BoardTM 6.1.0.2