On Mon, Jul 13, 2009 at 9:55 PM, Russ Cox<r...@swtch.com> wrote: > +plan9port-dev > bcc: 9fans > > I have just created a mailing list for these questions. > It is not documented anywhere yet - yours is the first. > I would have called the mailing list plan9port-help > but apparently -help is not a valid mailing list suffix. > plan9port-...@googlegroups.com
Should we put patches here, too? > > There is also an issue tracker at > http://bitbucket.org/rsc/plan9port/issues. > There may be a nicer URL in a few days. > > Russ > > On Mon, Jul 13, 2009 at 6:43 PM, Ethan Grammatikidis<eeke...@fastmail.fm> > wrote: >> Building plan9port on an arm box I get this message several times: >> >> sh: cd: 4: can't cd to armv5tel >> >> >> At the end of the build the only binary in plan9/bin is mk: >> >> $ file bin/* | grep ELF >> bin/mk: ELF 32-bit LSB executable, ARM, version 1 (SYSV), for >> GNU/Linux 2.6.14, dynamically linked (uses shared libs), not stripped >> >> >> In src/lib9 I symlinked getcallerpc-arm.c to getcallerpc-armv5tel.c; this >> made lib9 build but it's not enough to build the executables. How do I >> specify the architecture to the build system? I guess the setarch command >> may work, but I'd need to compile it too and I'd ideally like to work >> without that particular hack. >> > >
