Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] erlang: enable compilation on mipsel
Date: Wed, 22 Jun 2016 09:01:25 +0200	[thread overview]
Message-ID: <20160622090125.727d9c7b@free-electrons.com> (raw)
In-Reply-To: <1466527613-31459-1-git-send-email-fhunleth@troodon-software.com>

Hello,

On Tue, 21 Jun 2016 12:46:53 -0400, Frank Hunleth wrote:
> Erlang works fine on mipsel platforms so add it to the supported list.
> 
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
> ---
> 
> As a side note, one would hope that Erlang would work fine on mips, mips64
> and mipsel64, but I haven't found documentation of this yet and I can't
> verify it myself on real hw.

We have very good Qemu defconfigs in Buildroot, for all of mips,
mipsel, mips64el and mips64:

$ ls -1 configs/qemu_mips*
configs/qemu_mips64el_malta_defconfig
configs/qemu_mips64_malta_defconfig
configs/qemu_mipsel_malta_defconfig
configs/qemu_mips_malta_defconfig

These allow to very easily test things on those architectures even when
hardware is not available.

Note that I'm not saying that you *have* to test Erlang on all those
architectures, I'm perfectly fine with enabling it on mipsel today, and
enabling it later on other architectures when people need that. I just
wanted to take this opportunity to mention the Qemu defconfigs, that
are very regularly maintained and updated by Gustavo.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-06-22  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 16:46 [Buildroot] [PATCH] erlang: enable compilation on mipsel Frank Hunleth
2016-06-22  7:01 ` Thomas Petazzoni [this message]
2016-06-22 15:27   ` Frank Hunleth
2016-06-30 22:44 ` Thomas Petazzoni

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=20160622090125.727d9c7b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.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