From: Danny Milosavljevic <dannym@scratchpost.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>,
guix-devel@gnu.org, bug-mes@gnu.org
Subject: Re: Update on wip-arm-bootstrap
Date: Fri, 19 Feb 2021 05:23:41 +0100 [thread overview]
Message-ID: <20210219052341.5f10e637@scratchpost.org> (raw)
In-Reply-To: <874ki9cabq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
Hi Janneke,
On Thu, 18 Feb 2021 22:52:57 +0100
Jan Nieuwenhuizen <janneke@gnu.org> wrote:
> # 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!
OABI is older than year 2000, and the kernel docs say not to enable it.
It also breaks seccomp.
I doubt that people have it enabled, and thus would have trouble reproducing
our stuff. Since this only affects the syscall interface and since also our
ELF headers specify EABI, I would just change the syscalls to EABI:
Just put the syscall number into r7 and use svc 0.
I'd do it myself but I don't see what libc the gcc 2.95 we built has been
using.
Is it ours?
If so, how come it then uses svc 90000... in the first place?
We don't do that.
Or is it using glibc ?
How do I build that gcc on novena? Where would the syscall headers that
I could change be?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-02-19 4:24 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
2021-02-19 4:23 ` Danny Milosavljevic [this message]
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=20210219052341.5f10e637@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=bug-mes@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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.