On Sat, 11 May 2013 18:23:47 -0400
Steve Blackwell <zephod@xxxxxxxxxx> wrote:
> On Sat, 11 May 2013 16:05:35 -0400
> Stephen Harris <lists@xxxxxxxxxx> wrote:
>
> > > # ./lexmark-inkjet-08-driver-1.0-1.i386.rpm.sh
> >
> > > CPU Arch: x86_64
> > > Warning: No installer for "x86_64" found, defaulting to x86...
> >
> > > ./startupinstaller.sh:
> > > bin/linux/x86/libc.so.6/lzma-decode: /lib/ld-linux.so.2: bad ELF
> > > interpreter: No such file or directory
> >
> > Your system is pure 64bit; no 32bit routines installed. You're
> > trying to install a 32bit piece of software.
> >
> > You probably need to install glibc.i686 or determine if there's a
> > x86_64 version of the package you're trying to install.
> >
> I installed the glibc.i686 rpm which fixed some of the errors.
> Now I get this:
>
> # ./lexmark-inkjet-08-driver-1.0-1.i386.rpm.sh
> Verifying archive integrity... All good.
> Uncompressing
> nixstaller...............................................................
> Collecting info for this system... Operating system: linux CPU Arch:
> x86_64 Warning: No installer for "x86_64" found, defaulting to x86...
> Error: Couldn't find any suitable frontend for your system
>
> >From looking at the installer script, a suitable frontend appears to
> >be
> gtk, fltk or ncurs.
>
> Is it OK to have both the x86_64 and i686 versions of any of these
> installed?
I have installed some more i686 rpms and now I get the Lexmark
installer to run. It still fails however and I get a message about not
being able to load module "canberra-gtk-module". So...
# yum search canberra | grep i686
libcanberra-devel.i686 : Development Files for libcanberra Client
Development libcanberra-gtk2.i686 : Gtk+ Bindings for libcanberra
libcanberra.i686 : Portable Sound Event Library
# yum install libcanberra.i686
...lots of dependent packages to install
--> 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 tcp_wrappers-libs which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of tcp_wrappers-libs 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 tcp_wrappers-libs.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of tcp_wrappers-libs installed, but
yum can only see an upgrade for one of those arcitectures.
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 tcp_wrappers-libs 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: tcp_wrappers-libs-7.6-57.el6.i686 != tcp_wrappers-libs-7.6-57.el6.test.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I can't remove tcp_wrappers-libs-7.6-57.el6.test.x86_64 because too much depends on it.
Steve
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
