From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] trying to populate arm tree
Date: Mon, 28 Jan 2013 15:10:55 -0500 [thread overview]
Message-ID: <ffbc3c5ce3862bbe0f2b49ee43b8f24c@ladd.quanstro.net> (raw)
In-Reply-To: <ED875943-57F2-42F8-8DBC-C0704AAA0D32@gmail.com>
On Mon Jan 28 13:27:19 EST 2013, benavento@gmail.com wrote:
>
> On Jan 28, 2013, at 3:21 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> > or anything that's not x86.
>
> I have openssl-1.0.1c it builds on arm too...
(have you tested it?)
i don't think anyone said there are no contrib packages
that compile for arm, just that there are a number of
packages—especially ape ports—that either don't compile
or don't run correctly except on x86.
also, there are contrib packages that break other parts
of the system. and contrib packages that can't be rebuilt.
contrib is supposed to be the wild wild west. but it would
be nice to have a list of packages known to comple & run
on all the common arches, and also not break anything else.
- erik
next prev parent reply other threads:[~2013-01-28 20:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 12:46 James Chapman
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 [this message]
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=ffbc3c5ce3862bbe0f2b49ee43b8f24c@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).