Re: [9fans] Modularizing plan9port

[Enrico Weigelt <weigelt@metux.de>]

* Russ Cox <rsc@swtch.com> wrote:

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

Note: sysroot != chroot.
(sysroot *only* applies to the toolchain's search pathes)

> 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

Okay, how can I make sure the right toolchain is used, *all*
imports come from within sysroot and *only* code from the
(building) HOST system is executed - *never* from TARGET ?

> 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

No, I can't have one dedicated machine per target right here.
And most of my targets aren't even capable of compiling.

> That sounds like a lot less work than your original proposal.

Even if I could go this way, it would require *much* more
manual works. Simply too expensive.


cu
--
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 cellphone: +49 174 7066481   email: info@metux.de   skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------