From mboxrd@z Thu Jan  1 00:00:00 1970
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] Modularizing plan9port
From: "Russ Cox" <rsc@swtch.com>
Date: Wed, 11 Jun 2008 14:23:26 -0400
In-Reply-To: <20080611175304.GA23490@nibiru.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20080611182132.C91131E8C53@holo.morphisms.net>
Topicbox-Message-UUID: badf5688-ead3-11e9-9d60-3106f5b1d025

"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