From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about 64Bit kernel and 32Bit applications
Date: Tue, 2 Oct 2012 16:02:54 +0200 [thread overview]
Message-ID: <20121002160254.3b94fe25@skate> (raw)
In-Reply-To: <CAMJ=MEd+eR2Z1yUKu541TQzQJOhu-fpa6HDLD0e-0+n-Jt-6WA@mail.gmail.com>
Ronny,
On Tue, 2 Oct 2012 15:57:43 +0200, Ronny Meeus wrote:
> I'm using buildroot to build an environment for MIPS (Cavium).
> For this I use a 64 bit toolchain provided by Cavium.
Just curious, is this toolchain publicly available? I would really like
to have the opportunity to test it and integrate it as an external
toolchain in Buildroot.
> Building and deploying the kernel / busybox in this configuration
> works without issues.
>
> I want to deploy on this configuration "legacy" applications that need
> to run in 32 bit mode.
> So in fact I want to have a mixture of 32 and 64 bit
> (busybox,dropbear,...) applications to be present on the board.
>
> Is this supported in buildroot? If it is, how can this be configured?
No, generating a userland with a mix of libraries with different ABIs
is not supported.
And my opinion is that we should not try to support this. Unless I'm
missing something, it is a really bizarre use case, and adding support
for it would create an horrible additional complexity in Buildroot.
The change you did for libfuse cannot be integrated: it is MIPS
specific, and we also have no way of specifying on a per-package basis
whether it should be built for 32 bits or 64 bits.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-02 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 13:57 [Buildroot] Question about 64Bit kernel and 32Bit applications Ronny Meeus
2012-10-02 14:02 ` Thomas Petazzoni [this message]
[not found] ` <CAMJ=MEe-AfvoQ9tx5z3Wo2=w3tTbsorqCmcSp6trkxMmwpusZg@mail.gmail.com>
2012-10-02 17:49 ` Thomas Petazzoni
2012-10-02 18:39 ` Thomas De Schampheleire
2012-10-02 19:21 ` Ronny Meeus
2012-10-02 20:46 ` Ronny Meeus
2012-10-03 15:18 ` Ronny Meeus
2012-10-04 9:08 ` Arnout Vandecappelle
2012-10-04 10:56 ` Thomas De Schampheleire
2012-10-04 11:44 ` Arnout Vandecappelle
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=20121002160254.3b94fe25@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.