From: "Russ Cox" <rsc@swtch.com>
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] Modularizing plan9port
Date: Wed, 11 Jun 2008 14:23:26 -0400 [thread overview]
Message-ID: <20080611182132.C91131E8C53@holo.morphisms.net> (raw)
In-Reply-To: <20080611175304.GA23490@nibiru.local>
"I need a way to cross-compile plan9port" would
have been a much more productive opening statement
than "I'm going to modularize plan9port".
I think you should be able to cross-compile it
pretty easily if you already have a cross-compilation
environment set up.
1. Build a local plan9port tree, put it in the chroot
environment, and put it at the end of your chrooted $PATH.
2. Edit that tree's 9 script to override $PLAN9 with
the path to the local tree (1 line change).
3. Extract a fresh tree somewhere else.
4. run SYSNAME=xxx OBJTYPE=xxx INSTALL in the fresh tree.
(assumes
I haven't tried this (I find it much easier just to set up
a dedicated machine of the right OS and architecture
and use its native tools), but having the local copy of
the tools in the path before running INSTALL should
make it use those instead of the ones it builds.
That sounds like a lot less work than your original proposal.
Good luck.
Russ
next prev parent reply other threads:[~2008-06-11 18:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 12:40 Enrico Weigelt
2008-06-11 12:47 ` erik quanstrom
2008-06-11 13:05 ` Jeff Sickel
2008-06-11 13:30 ` Russ Cox
2008-06-11 15:30 ` Enrico Weigelt
2008-06-11 15:43 ` Uriel
2008-06-11 15:46 ` Uriel
2008-06-11 17:53 ` Enrico Weigelt
2008-06-11 18:23 ` Russ Cox [this message]
2008-06-11 20:42 ` Roman Shaposhnik
2008-06-11 20:48 ` Enrico Weigelt
2008-06-11 20:57 ` William Josephson
2008-06-11 21:30 ` Russ Cox
2008-06-12 14:09 ` Enrico Weigelt
2008-06-11 19:28 ` Iruata Souza
2008-06-11 17:33 ` tlaronde
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=20080611182132.C91131E8C53@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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).