9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Building 9vx on a modern Linux?
Date: Thu, 29 Jun 2023 23:46:00 -0700	[thread overview]
Message-ID: <CAJSxfmJWnX6BZ3jMK_XMs3Jpb5PKQ_FnwYF0xt4YV1z-gOdbaQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_X0tC3R-nmoz1KHL=neTMopOgLYKxJen2Luz=WHpEyQpBA-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]

i did this a couple of days ago on Ubuntu 22.04; i had to install these to
successfully build/link:
apt install build-essential gcc-multilib libx11-dev libx11-dev:i386

On Thu, Jun 29, 2023, 9:48 PM Don Bailey <don.bailey@gmail.com> wrote:

> Hi Pals,
> I'm trying to build 9vx using the current vx32 repo. I have (as I
> understand it) installed multiarch in my Ubuntu environment (22). But I
> can't compile 9vx. It fails to find the 32bit libx11, which is installed
> under /usr/lib/i386..../ and instead insists on looking under
> /usr/lib/x86_64..../
> Any tips? I've never had to use multiarch for anything and don't want to
> waste a lot of time trying to get 9vx working just to work with a demo
> RISC-V plan9 kernel.
> Thanks all,
> D
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Tcc9412f74455bd96-M5d67cb164f3cb6843fb5d76b>

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tcc9412f74455bd96-M451db97da68320a33832f013
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1914 bytes --]

  reply	other threads:[~2023-06-30  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  4:47 Don Bailey
2023-06-30  6:46 ` Skip Tavakkolian [this message]
2023-06-30 15:13   ` Don Bailey

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJSxfmJWnX6BZ3jMK_XMs3Jpb5PKQ_FnwYF0xt4YV1z-gOdbaQ@mail.gmail.com \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \


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