From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] building plan9port: arch spec, arm vs armv5tel
Date: Tue, 14 Jul 2009 18:12:02 -0400 [thread overview]
Message-ID: <3aaafc130907141512u50dca03cga34e5a5332d1a8b1@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0907131855q40412081qdaa52f88852a57eb@mail.gmail.com>
On Mon, Jul 13, 2009 at 9:55 PM, Russ Cox<rsc@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-dev@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<eekee57@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.
>>
>
>
next prev parent reply other threads:[~2009-07-14 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 1:43 Ethan Grammatikidis
2009-07-14 1:55 ` Russ Cox
2009-07-14 22:12 ` J.R. Mauro [this message]
2009-07-15 0:06 ` Russ Cox
2009-07-15 1:03 ` J.R. Mauro
2009-07-15 15:31 ` Uriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3aaafc130907141512u50dca03cga34e5a5332d1a8b1@mail.gmail.com \
--to=jrm8005@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).