* Russ Cox [EMAIL PROTECTED] wrote:
Hi,
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 would have expected your host system to refuse
to run binaries
So I intent do write some script which creates Makefile's from
mkfile's and maybe even does some build-time configuration
(sort of ./configure ;-)). That script(s) could be packet along
with some other fundamental p9p build utils, and this package
then would be the very first in depedency
On Jun 11, 2008, at 7:40 AM, Enrico Weigelt wrote:
I'm going to modularize plan9port a bit.
I'd recommend just leaving it as it is--you can easily pull out and
use the pieces you want based off of the current build tree.
...
What do you think about this approach ?
Way to much like
If you want to cross-compile why don't you use Plan 9? or at least the
port of the plan9 compilers to lunix[1], where cross compiling is the
only way to compile.
Cross-compiling in Gnu/land is a nightmare not worth going into.
uriel
[1] http://gsoc.cat-v.org/projects/kencc/
On Wed, Jun 11,
By the way, silly question, but what would it take to have the kencc
port accepted as part of p9p?
And a port of of plan9's awk (trivial to do)? It would be nice to be
able to rely on a decent utf-8 enabled awk when writing scripts for
p9p without worrying about what broken awk does this or that
Hello,
On Wed, Jun 11, 2008 at 02:40:38PM +0200, Enrico Weigelt wrote:
[...]
So I intent do write some script which creates Makefile's from
mkfile's and maybe even does some build-time configuration
(sort of ./configure ;-)). That script(s) could be packet along
with some other
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
On Wed, Jun 11, 2008 at 2:53 PM, Enrico Weigelt [EMAIL PROTECTED] wrote:
* Uriel [EMAIL PROTECTED] wrote:
Cross-compiling in Gnu/land is a nightmare not worth going into.
No, it isn't - as long as you've got a proper toolchain and
get around autoshit. (eg. I've got my own libtool
On Wed, 2008-06-11 at 14:23 -0400, Russ Cox wrote:
I find it much easier just to set up
a dedicated machine of the right OS and architecture
and use its native tools
Speaking of which: am I the only one betraying the true
cross-compiling in favor of virtualized copies of the
OS/platform? I
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 would have expected your host system to refuse
to run binaries for the target architecture.
You are clearly
10 matches
Mail list logo
