From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] ape under arm
Date: Tue, 7 Feb 2012 10:27:00 -0600 [thread overview]
Message-ID: <D6900507-9372-4D13-98E8-E1790B22E188@corpus-callosum.com> (raw)
Just a quick question for other users of ARM based machines:
Should the ape/lib/openssl be ignored for ARM, or is there a decent alternative for objtype=arm when trying to
build it? The current build fails as /sys/include/ape/openssl/opensslconf.h errors out with 'unknown objtype'.
Otherwise, I can get ape/lib/openssl to build (though not necessarily be viable) by the subtle change below:
term% cd /sys/include/ape/openssl
term% diffy opensslconf.h
85c85,86
< #if defined(PLAN9) && defined(T386)
---
> #if defined(PLAN9)
> #if defined(T386)
86a88,89
> #elif defined(Tarm)
> #define ARM_ONLY
89a93,94
> #endif
>
This small change has made it a lot easier to populate my arm tree.
next reply other threads:[~2012-02-07 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 16:27 Jeff Sickel [this message]
2012-02-07 21:40 ` [9fans] new zlib (1.2.6) support &| build Jeff Sickel
2012-02-07 21:50 ` Jeff Sickel
2012-02-08 0:18 ` Jeff Sickel
2012-02-08 0:21 ` erik quanstrom
2012-02-08 2:48 ` Jeff Sickel
2012-02-08 2:52 ` Jeff Sickel
2012-02-08 3:50 ` Jeff Sickel
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=D6900507-9372-4D13-98E8-E1790B22E188@corpus-callosum.com \
--to=jas@corpus-callosum.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).