SCIENTIFIC-LINUX-USERS Archives

October 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Yasha Karant <[log in to unmask]>
Reply To:
Yasha Karant <[log in to unmask]>
Date:
Tue, 13 Oct 2015 00:41:13 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
I must run a variety of web browser applications.  One of these is 
seamonkey.

Diagnostics:

[root@linux-3iz7 opt]# seamonkey/seamonkey
XPCOMGlueLoad error for file /opt/seamonkey/libxul.so:
libfreetype.so.6: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
[root@linux-3iz7 opt]# yum install libfreetype.so.6
Loaded plugins: langpacks, nvidia
Resolving Dependencies
--> Running transaction check
---> Package freetype.i686 0:2.4.11-10.el7_1.1 will be installed
--> Finished Dependency Resolution
Error:  Multilib version problems found. This often means that the root
        cause is something else and multilib version checking is just
        pointing out that there is a problem. Eg.:

          1. You have an upgrade for freetype which is missing some
             dependency that another package requires. Yum is trying to
             solve this by installing an older version of freetype of the
             different architecture. If you exclude the bad architecture
             yum will tell you what the root cause is (which package
             requires what). You can try redoing the upgrade with
             --exclude freetype.otherarch ... this should give you an error
             message showing the root cause of the problem.

          2. You have multiple architectures of freetype installed, but
             yum can only see an upgrade for one of those architectures.
             If you don't want/need both architectures anymore then you
             can remove the one with the missing update and everything
             will work.

          3. You have duplicate versions of freetype installed already.
             You can use "yum check" to get yum show these errors.

        ...you can also use --setopt=protected_multilib=false to remove
        this checking, however this is almost never the correct thing to
        do as something else is very likely to go wrong (often causing
        much more problems).

        Protected multilib versions: freetype-2.4.11-10.el7_1.1.i686 != 
freetype-2.4.11-9.el7.x86_64
[root@linux-3iz7 opt]#

There does not seem to a X86-64 tar.bz2 runnable binary for Seamonkey, 
only an IA-32 version, but polymorphism for the above
support application (freetype) does not seem to be possible.  Any 
suggestions would be kindly appreciated.  The environment is SL 7.1 not 
yet fully updated to SL 7x.   ElRepo and EPEL repositories also are used 
for applications that are not readily available in
the "stock" repo.

Yasha Karant

ATOM RSS1 RSS2