From: 6o205zd02@sneakemail.com
To: 9fans@cse.psu.edu
Subject: [9fans] Building P9P for multiple architectures from the same source tree?
Date: Fri, 21 Dec 2007 05:29:18 +0000 [thread overview]
Message-ID: <4664-67673@sneakemail.com> (raw)
Is it possible to build P9P for multiple architectures (e.g. linux i386 and amd64) in the same tree? I looked at the documentation but didn't see anything.
In my work environment I can't install in /usr/local/plan9 because I don't control the machines, so I install in my (NFS mounted) home directory. This has worked fine up until now because all the machines are running i386 linux. Unfortunately, we are now starting to have some machines running amd64 linux, so I need to build an amd64 version of P9P. I would like to avoid having two complete copies of the tree if possible.
Does anybody have any suggestions.
thanks,
Peter Canning
PS: I imagine I could solve this nicely with namespaces if I was running real plan9.
next reply other threads:[~2007-12-21 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 5:29 6o205zd02 [this message]
2007-12-27 16:09 ` Russ Cox
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=4664-67673@sneakemail.com \
--to=6o205zd02@sneakemail.com \
--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).