From: James Chapman <james@cs.ioc.ee>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] trying to populate arm tree
Date: Mon, 28 Jan 2013 14:46:38 +0200 [thread overview]
Message-ID: <006549EF-F9F0-4DE1-A4EC-2B7F6E7FBCBA@cs.ioc.ee> (raw)
Hi,
I would like to boot my 9pi using an fs from a 386 based cpu/auth/fossil server.
I have previously installed:
fgb/z
fgb/bz2
fgb/openssl
bichued/python
stallion/mercurial
and go from the development repo, and I was planning on putting kertex on there too.
I tried cpuing into the server and running
cpu% cd /sys/src
cpu% objtype=arm mk install
The build fails with a lot of cpp errors about /sys/include/ape/openssl/*.h
about unknown object type.
How can i exclude openssl from the build?
I'm assuming I won't be able to build it. I can put up with cpuing in to run the extra stuff I have installed.
I tried adding openssl to BUGGERED in /sys/src/cmd/mkfile but this didn't help.
James
next reply other threads:[~2013-01-28 12:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 12:46 James Chapman [this message]
2013-01-28 14:32 ` Jens Staal
2013-01-28 14:53 ` Federico G. Benavento
2013-01-28 15:07 ` Federico G. Benavento
2013-01-28 15:38 ` James Chapman
2013-01-28 15:30 ` James Chapman
2013-01-28 16:47 ` Federico G. Benavento
2013-01-28 17:20 ` James Chapman
2013-01-28 17:40 ` Jeff Sickel
2013-01-28 18:21 ` erik quanstrom
2013-01-28 18:26 ` Federico G. Benavento
2013-01-28 20:10 ` erik quanstrom
2013-01-28 20:14 ` Federico G. Benavento
2013-01-29 22:07 ` Richard Miller
2013-01-29 22:02 ` Richard Miller
2013-01-28 15:32 ` erik quanstrom
2013-01-28 15:53 ` Federico G. Benavento
2013-01-28 16:25 ` Jacob Todd
2013-01-28 16:40 ` Matthew Veety
2013-01-28 16:40 ` Federico G. Benavento
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=006549EF-F9F0-4DE1-A4EC-2B7F6E7FBCBA@cs.ioc.ee \
--to=james@cs.ioc.ee \
--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).