From: Alexander Sychev <santucco@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p on 64 bit Linux
Date: Tue, 4 Mar 2014 12:55:48 +0400 [thread overview]
Message-ID: <CAPavXpBPJ4WNgros=C_fLXuL8p9yzsVGWOgtJQoR3HPyb8UQHw@mail.gmail.com> (raw)
In-Reply-To: <CABwHSOvGOaQQr5=86twzZ25OfkvDUFpkXZAa6AcN-cfHs1rkgw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi,
I think, you should check the ld cache:
ldconfig -p | grep libX11.so
Also you can run
ldd $PLAN9/bin/devdraw
and check some other dependencies from X world
On Tue, Mar 4, 2014 at 6:58 AM, Blake McBride <blake@mcbride.name> wrote:
> Greetings,
>
> I am trying to build p9p with the latest LinuxMint on a 64 bit machine.
> In addition to the normal stuff, I think I had to install packages:
>
> libxt-dev
> libxext-dev
>
> It built fine, but what I run it I get:
>
> blake@sony-linux-laptop ~ $ acme
> acme: error while loading shared libraries: libX11.so.6: cannot open
> shared object file: No such file or directory
> blake@sony-linux-laptop ~ $
>
>
> I have:
>
> blake@sony-linux-laptop /usr/lib $ find . -name 'libX11*'
> ./x86_64-linux-gnu/libX11-xcb.so.1.0.0
> ./x86_64-linux-gnu/libX11.a
> ./x86_64-linux-gnu/libX11.so.6.3.0
> ./x86_64-linux-gnu/libX11-xcb.so.1
> ./x86_64-linux-gnu/libX11.so.6
> ./x86_64-linux-gnu/libX11.so
>
>
> I think it may be looking for 32 bit shared libraries. I am not sure how
> things are getting built on a 64 bit environment. Your help is greatly
> appreciated.
>
> Thanks.
>
> Blake McBride
>
>
--
Best regards,
santucco
[-- Attachment #2: Type: text/html, Size: 2075 bytes --]
next prev parent reply other threads:[~2014-03-04 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 2:58 Blake McBride
2014-03-04 8:55 ` Alexander Sychev [this message]
2014-03-04 9:11 ` Charles Forsyth
2014-03-04 9:18 ` tuchalia
2014-03-04 9:48 ` David du Colombier
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='CAPavXpBPJ4WNgros=C_fLXuL8p9yzsVGWOgtJQoR3HPyb8UQHw@mail.gmail.com' \
--to=santucco@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).