From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Where to find 32 bit emul libs?
Date: Fri, 5 Jun 2009 21:42:30 +0200 [thread overview]
Message-ID: <200906052142.30284.alan.mckinnon@gmail.com> (raw)
Hi,
I want to give Google's new Chrome browser for Linux a try. It's shipped as 32
and 64 bit .debs only. That's the easy part. Chrome itself is a 32bit app, and
it's complains about these missing libs:
$ ldd chrome | grep 'not found'
libnss3.so.1d => not found
libnssutil3.so.1d => not found
libsmime3.so.1d => not found
libssl3.so.1d => not found
libplds4.so.0d => not found
libplc4.so.0d => not found
libnspr4.so.0d => not found
libgconf-2.so.4 => not found
I have all emul-linux packages installed anyway (except -qtlibs), but now I'm
stumped. How would I find which packages provide these 32 bit libs?
--
alan dot mckinnon at gmail dot com
next reply other threads:[~2009-06-05 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 19:42 Alan McKinnon [this message]
2009-06-05 20:09 ` [gentoo-user] Where to find 32 bit emul libs? Arttu V.
2009-06-05 20:28 ` Alan McKinnon
2009-06-05 20:26 ` Paul Hartman
2009-06-05 20:54 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906052142.30284.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox