seamonkey

2015-10-13 Thread Yasha Karant
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


Re: seamonkey

2015-10-13 Thread Denice

On Tue, 13 Oct 2015, Yasha Karant wrote:


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

...
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.


seamonkey is in the Fedora everything tree.

I built it earlier this year from one of the Fedora versions.   I had
to hack the spec file and the comm-release/mozilla/configure file
to force it to use an older version of nss in order to get it to
build on stock SL 7.  That is presumably why it has not shown up in epel
so far, if it ever will.

But it works for me, so whatever is hardwired into the build process
for build requirements for the nss library versions does not seem to
affect my experience with it.

cheers, etc.
--
deatrich @ triumf.ca, Science/ATLAS PH: +1 604-222-7665
<*> This moment's fortune cookie:
Next to being shot at and missed, nothing is really quite as satisfying
as an income tax refund.
-- F. J. Raymond