From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 12 Jul 2011 20:08:06 +0100 From: Ethan Grammatikidis To: 9fans@9fans.net Message-ID: <20110712200806.07ff5a7d@lahti.ethans.dre.am> In-Reply-To: <5eeb67c747b34515a3a2c065ae853eed@hamnavoe.com> References: <5eeb67c747b34515a3a2c065ae853eed@hamnavoe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [9fans] GNU/Linux/Plan 9 disto Topicbox-Message-UUID: 00a7aa32-ead7-11e9-9d60-3106f5b1d025 On Tue, 12 Jul 2011 19:09:44 +0100 Richard Miller <9fans@hamnavoe.com> wrote: > > On > > plan9 of course I don't pull from sources over my mobile phone, > > instead pull and compile on the CPU server. > > Compiling on a phone is no longer so far-fetched. Compiling all > of plan9port from scratch on a Nokia n900 takes about 1.5 hours. > It seems to be less hassle just to install gcc on the n900 than to > set up Nokia's weird cross-compiling environment on another host. This is exactly what I found on my Zaurus a few years ago... and then I found that the available basesystems were broken for compilation and putting a sane basesystem together was impossible. Glibc was installed, and recompiling that was... well, I never succeeded despite trying very hard and having plenty of time to put into it. Deitlibc didn't even have an arm port when I first wanted one, and ucLibc again wanted to do everything in a confusing alternate environment. It wasn't exactly cross-compilation, it was an environment which ran in QEmu, but anything I built in that QEmu VM wouldn't run on the real hardware, despite static linking. Horrible mess. I never did get to use that Zaurus properly. Hm, I never finished getting p9p to compile, either. I submitted one small patch but it wasn't all that was needed and I lost interest in the Zaurus altogether about a year before p9p was fixed for arm/Linux.