• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't install glib 1.2.10 on Fedora Core 3

S

Sureshot324

Diamond Member
I'm trying to install glib 1.2.10 on my machine so i can install xmms. I seem to remember that xmms need glib/gtk 1.2 instead of the newest version 2.5 (is this correct). Anyway, ./configure works fine, but make fails. Here are the last few lines:

g_log_domain_glib -g -O2 -Wall -D_REENTRANT -c gstrfuncs.c
rm -f .libs/gstrfuncs.lo
gcc -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=g_log_domain_glib -g -O2 -Wall -D_REENTRANT -c gstrfuncs.c -fPIC -DPIC -o .libs/gstrfuncs.lo
gstrfuncs.c: In function `g_printf_string_upper_bound':
gstrfuncs.c:870: error: syntax error before string constant
gstrfuncs.c:1037: error: syntax error before string constant
gstrfuncs.c:1080: error: syntax error before string constant
gstrfuncs.c:1111: error: syntax error before string constant
make[2]: *** [gstrfuncs.lo] Error 1
make[2]: Leaving directory `/home/louis/glib-1.2.10'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/louis/glib-1.2.10'
make: *** [all-recursive-am] Error 2
[root@localhost glib-1.2.10]#

Can anyone help?
 
The rpm worked, didn't try it before because it said it was for Fedora Core 1. Why does the source need glib and gtk but the rpm doesn't?
 
Originally posted by: Sureshot324
The rpm worked, didn't try it before because it said it was for Fedora Core 1. Why does the source need glib and gtk but the rpm doesn't?
Click to expand...

Maybe you have glib and gtk installed already. rpm -qa | grep glib might tell you (not positive, I hate RPMs 😛).

Or it's staticly compiled.
 
The rpm worked, didn't try it before because it said it was for Fedora Core 1.
Click to expand...

It does, but to compile it you also need the -dev packages that have the headers in them which you probably didn't have.
 
That's not a big deal then. Just add a third-party repository to your sources, they'd probably have a XMMS with the legally questionable codecs. (which btw is the LAME codec, so i don't know if you just need to have the codec aviable, or it mp3 support has to be compiled in.)

There are several to choose from..
at rpms http://atrpms.net/
fresh rpms http://freshrpms.net/
dags rpms http://dag.wieers.com/home-made/apt/


pick one or two to update against and you should be able to get xmms support with MP3s. Thats one of the reasons these guys exist is to supply extra packages that Redhat/Fedora wish to avoid because of legal issues. Now that Fedore Core 3 is just out, they probably aren't going to have a whole lot, but they will.

And that way you can get access to lots of other programs that Fedora doesn't offer by default, too.

Otherwise what your going to have to do is install all those *-dev packages for all the different libraries that xmms needs to be compiled against, then make sure that you have everything.
 
I did get xmms working with the rpm from the xmms.org site, but thanks for the info anyway. The default yum repository didn't seem to even have firefox.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top