From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org, bug-mes@gnu.org
Subject: Re: Update on wip-arm-bootstrap
Date: Thu, 18 Feb 2021 22:52:57 +0100 [thread overview]
Message-ID: <874ki9cabq.fsf@gnu.org> (raw)
In-Reply-To: <87h7m91d3j.fsf@yucca> (Vagrant Cascadian's message of "Thu, 18 Feb 2021 09:48:32 -0800")
Vagrant Cascadian writes:
Hi!
> On 2021-02-13, Jan Nieuwenhuizen wrote:
[..]
>> ...pretty familiar. So, what's going on here? Do the "woody"
>> binaries not run on novena?
>
> My guess would be OABI (debian "arm" architecture) vs. EABI (debian
> "armel" or "armhf" architectures). The hardware may likly support OABI,
> but the kernel may need a compatibility layer enabled.
>
> https://wiki.debian.org/ArmPorts
Ah, interesting. The kernel config has
# CONFIG_OABI_COMPAT is not set
...certainly a lot easier to find when you know what you're looking
for.
@Danny: I'm wondering if we could (should?) try a kernel with OABI
compatibility? I suppose it would be better to somehow target
EABI...but I'm not sure that's possible with glibc-2.2.5 / gcc-2.95.3.
Interesting choices here!
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2021-02-18 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 9:25 Update on wip-arm-bootstrap Jan Nieuwenhuizen
2021-02-18 17:26 ` Ludovic Courtès
2021-02-21 18:17 ` Jan Nieuwenhuizen
2021-02-22 1:03 ` Danny Milosavljevic
2021-02-18 17:48 ` Vagrant Cascadian
2021-02-18 21:52 ` Jan Nieuwenhuizen [this message]
2021-02-19 4:23 ` Danny Milosavljevic
2021-02-19 6:17 ` Jan Nieuwenhuizen
2021-02-21 18:28 ` Jan Nieuwenhuizen
2021-02-22 1:03 ` Danny Milosavljevic
2021-02-22 1:50 ` Danny Milosavljevic
2021-02-22 6:01 ` Jan Nieuwenhuizen
2021-02-22 17:09 ` Danny Milosavljevic
2021-02-22 17:34 ` Danny Milosavljevic
2021-02-22 6:14 ` Jan Nieuwenhuizen
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=874ki9cabq.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=bug-mes@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.