Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	 "babel-users@lists.alioth.debian.org"
	<babel-users@lists.alioth.debian.org>
Subject: Re: [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...]
Date: Wed, 22 Jun 2016 09:38:58 -0700	[thread overview]
Message-ID: <CAA93jw4kSz71gUBSPtZb-ggwVYJPq2uiC8LvrjNA7HORj36arg@mail.gmail.com> (raw)
In-Reply-To: <87lh1xihnv.wl-jch@pps.univ-paris-diderot.fr>

On Wed, Jun 22, 2016 at 4:31 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> The preinstalled OS has sufficient compiler and onboard flash space to
>> build a current babeld from git, and I'm happy to report IPV6_SUBTREES
>> is compiled in by default.
>
> Dave,
>
> It's not the first time that I notice with wonder that you're compiling on
> the devel boards.  Are you aware that cross-compiling babeld to armhf is
> so easy it's not even funny?
>
>   sudo apt-get install gcc-arm-linux-gnueabihf
>   make CC=arm-linux-gnueabihf-gcc


I ended up writing a long rant about this that I will blog one day...
but my short answer to both your suggestions that I cross compile or
install a docker: "You kids, get off my lawn!" :)

I have a tendency to need to compile things vastly more complex than
babel, often more bleeding edge than what is supplied in a repo, and
*knowing* that an apt-get build-dep something; then checking it out
from git head, will actually work with minimal effort, is a joy. The
latest generation of hackerboards are actually "real computers",
because they have a working, on-board compiler and full debian (and
android) support. They would be even more real if the Xwindow drivers
worked worth a damn and I could hook up a keyboard, or a variety of
more obscure languages (:cough: "go", "rust") actually worked, also.

I would love to one day soon be back on a world where I only had to
compile stuff for one architecture, and could spend more time writing
code rather than dealing with ABI differences. I am impressed with the
java port... Although I don't care for java much, it would be nice to
carry these new protocols into android somehow.

> Shncpd is a little bit trickier, since it depends on libbsd.  I think I'll
> remove the dependency before relase, but in the meantime you may either
> build yourself an armhf libbsd, or install libbsd0:armhf on your system
> (which requires setting up a multiarch environment), or set up
> a cross-compilation chroot, or simply copy libbsd.so from the target system.

Compiling natively, I don't have to think about that.

(does a working cross compiler exist for the aarch64 in the c2?)


-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

  parent reply	other threads:[~2016-06-22 16:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 23:54 [Cerowrt-devel] beaglebone green wireless boards now available Dave Taht
2016-06-22 11:31 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Juliusz Chroboczek
2016-06-22 12:08   ` [Cerowrt-devel] [Babel-users] " Benjamin Henrion
2016-06-22 13:10     ` [Cerowrt-devel] Cross-compiling to armhf Juliusz Chroboczek
2016-06-22 13:15       ` Benjamin Henrion
2016-06-22 20:38         ` Juliusz Chroboczek
2016-06-22 16:38   ` Dave Taht [this message]
2016-06-23 22:10     ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Juliusz Chroboczek
2016-06-23 22:45       ` Dave Taht
2016-06-23 22:57         ` Juliusz Chroboczek
2016-06-23 23:13           ` Dave Taht
2016-06-24  0:02             ` [Cerowrt-devel] Why we are discussing ARM [was: Cross-compiling to armhf] Juliusz Chroboczek
2016-06-24  2:37               ` Jonathan Morton
2016-06-24 11:04                 ` Juliusz Chroboczek
2016-06-24 16:36                   ` Eric Johansson
2016-06-24 20:27                     ` David Lang
     [not found]               ` <E1bH8oe-0000Wv-EO@stardust.g4.wien.funkfeuer.at>
2016-06-26 17:59                 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-06-26 19:02                   ` Baptiste Jonglez
2016-06-26 19:58                     ` Jonathan Morton
2016-06-26 20:03                     ` Juliusz Chroboczek
2016-06-23 23:20           ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Jonathan Morton
2016-06-23 23:27             ` Dave Taht
2016-06-23 23:42               ` Dave Taht
2016-06-24 16:25                 ` Eric Johansson

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw4kSz71gUBSPtZb-ggwVYJPq2uiC8LvrjNA7HORj36arg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jch@pps.univ-paris-diderot.fr \
    /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