From: David Morris <lists@morris-clan.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9port build failure on Linux (debian)
Date: Mon, 3 Mar 2008 09:25:11 -0700 [thread overview]
Message-ID: <20080303162511.GC28226@morris-clan.net> (raw)
In-Reply-To: <140e7ec30803030709g23c81b57jab711b7eaf121a04@mail.gmail.com>
On Tue, Mar 04, 2008 at 12:09:27AM +0900, sqweek wrote:
> On Mon, Mar 3, 2008 at 5:46 PM, David Morris <lists@morris-clan.net> wrote:
> > This time the build worked, so looks like some lenny/sid
> > packages don't work well together. Hmm, or another
> > possibility occurs to me. I use the AMD64 kernel
> > (2.6.22-3-amd64) on my desktop, but i686 on the laptop
> > (2.6.22-3-i686). Any chance that could cause a problem?
>
> I run p9p on x86_64 at work (CentOS), so no. There are some problems
> with 9pfuse under x86_64 (which look like fuse's fault to me), but the
> only problem I had at build was missing dependencies (some X11
> development packages).
> I'll try and remember to cvs update and see if it still builds.
Good to know. I was thinking more along the lines of a
problem because I'm using a 64-bit kernel in a 32-bit
userspace, a setup I've had other applications have problems
with, though it was a binary distribution I simply had to
recompile.
--David
next prev parent reply other threads:[~2008-03-03 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 4:20 David Morris
2008-03-03 5:23 ` Hongzheng Wang
[not found] ` <20080303084557.GA24732@morris-clan.net>
2008-03-03 8:46 ` David Morris
2008-03-03 15:09 ` sqweek
2008-03-03 16:25 ` David Morris [this message]
2008-03-03 16:17 ` Russ Cox
2008-03-03 17:27 ` David Morris
2008-03-03 19:02 ` erik quanstrom
[not found] ` <20080303195459.GE28226@morris-clan.net>
2008-03-03 19:56 ` David Morris
2008-03-04 4:42 ` Russ Cox
2008-03-05 16:21 ` Douglas A. Gwyn
2008-03-03 14:10 erik quanstrom
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=20080303162511.GC28226@morris-clan.net \
--to=lists@morris-clan.net \
--cc=9fans@cse.psu.edu \
/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).