Hi,

    I met some problem when install gnomemeeting.My PC is under RedHat Linux 
9.0(kernel 

version is 2.4.22). 

    I download:
        gnomemeeting-1.2.1-1.FC3.i386.rpm
        openh323-1.15.3-1.i386.rpm
        pwlib-1.8.4-1.i386.rpm

    First I install pwlib and openh323,no problem!
    Then I run:
        [EMAIL PROTECTED] gnomemeeting]# rpm -ivh 
gnomemeeting-1.2.1-1.FC3.i386.rpm
        warning: gnomemeeting-1.2.1-1.FC3.i386.rpm: V3 DSA signature: NOKEY, 
key ID de95bc1f
        error: Failed dependencies:
        evolution-data-server is needed by gnomemeeting-1.2.1-1.FC3
                libc.so.6(GLIBC_2.3.4) is needed by gnomemeeting-1.2.1-1.FC3
                libebook.so.8 is needed by gnomemeeting-1.2.1-1.FC3
                libedataserver.so.3 is needed by gnomemeeting-1.2.1-1.FC3
                liblber-2.2.so.7 is needed by gnomemeeting-1.2.1-1.FC3
                libldap-2.2.so.7 is needed by gnomemeeting-1.2.1-1.FC3
                libstdc++.so.6 is needed by gnomemeeting-1.2.1-1.FC3
                libstdc++.so.6(CXXABI_1.3) is needed by gnomemeeting-1.2.1-1.FC3
                libstdc++.so.6(GLIBCXX_3.4) is needed by 
gnomemeeting-1.2.1-1.FC3

    The glibc version is glibc-2.3.2-11.9,so I download 
glibc-2.3.4-2.i386.rpm,then I run:
        [EMAIL PROTECTED] others]# rpm -Uvh glibc-2.3.4-2.i386.rpm
        warning: glibc-2.3.4-2.i386.rpm: V3 DSA signature: NOKEY, key ID 
443e1821
        error: Failed dependencies:
                glibc-common = 2.3.4-2 is needed by glibc-2.3.4-2
                shadow-utils < 2:4.0.3-20 conflicts with glibc-2.3.4-2
                nscd < 2.3.3-52 conflicts with glibc-2.3.4-2
                glibc = 2.3.2 is needed by (installed) glibc-devel-2.3.2-11.9

    I don't know how to solve the dependencies.Hope someone can help me!

    Thank you in advance for any help!

    Have a nice day!

John



_______________________________________________
GnomeMeeting-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnomemeeting-list

Reply via email to