public inbox for sig-arm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: Interested in making an odroid-u2 image of ipFire
Date: Tue, 09 Sep 2014 15:56:12 +0200	[thread overview]
Message-ID: <910dc18a85243ce7c681487f41bfceb0@mail01.ipfire.org> (raw)
In-Reply-To: <fe8529100361478188c9f7630a261a5d@APLEX04.dom1.jhuapl.edu>

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

On 2014-09-08 18:45, Levine, Daniel J. wrote:
> Hi,
> 
> I see some Arm development regarding ipFire going on. I was wondering
> how difficult it might be to make one on an odroid-u2.
> 
> Suppose I already have a bootable Ubuntu 14.04 and I am able to build
> a kernel package with the desired kernel .config parameters (if that's
> necessary). Would I simply go over to the ipFire github site and get
> the ipFire-2.x with git and build the arm version?

The IPFire buildsystem should work with ubuntu on the odroid. (I use an 
Odroid-X to build IPFire.)
If you clone the git and check the master or next out and run
./make.sh gettoolchain
./make.sh downloadsrc
./make.sh build

It will build the current master or next devel-branch for arm.

There are two problems at odroid-x/u support. You need to build a 
working uboot from source (Exynos need a signed bootloader which is very 
bad)
and a 3.10.x kernel with grsecurity, imq, layer7 and some other 
patchsets.

Both we have not got to work.

Arne


           reply	other threads:[~2014-09-09 13:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <fe8529100361478188c9f7630a261a5d@APLEX04.dom1.jhuapl.edu>]

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=910dc18a85243ce7c681487f41bfceb0@mail01.ipfire.org \
    --to=arne.fitzenreiter@ipfire.org \
    --cc=sig-arm@lists.ipfire.org \
    /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