public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Sergey Bugaev <bugaevc@gmail.com>
Cc: libc-alpha@sourceware.org, bug-hurd@gnu.org,
	Flavio Cruz <flaviocruz@gmail.com>, Luca <luca@orpolo.org>
Subject: Re: [PATCH v3 4/6] hurd: Add expected abilist files for x86_64
Date: Mon, 1 May 2023 19:43:08 +0200	[thread overview]
Message-ID: <20230501174308.23d43uojxq5z4yk6@begin> (raw)
In-Reply-To: <CAN9u=HeoLbKV9a=-ShWpucgv5cifymj00UeoiX8mTnAxi+SV8g@mail.gmail.com>

Sergey Bugaev, le lun. 01 mai 2023 20:33:36 +0300, a ecrit:
> On Mon, May 1, 2023 at 1:20 PM Samuel Thibault <samuel.thibault@gnu.org> wrote:
> > Applied, thanks!
> 
> I assume the delay means you have built it, and your results matched
> mine,

Yes :)

Though I added libanl which we do want since we haven't moved libpthread
into libc.

> I can hardly believe it no longer only exists on my machine :) Did you
> manage to run it?

I haven't tried that at all.

> How do we proceed? I don't know enough about rump to get it building;

We can easily cross-build debian packages thanks to the rebootstrap
scripts from Helmut:

https://salsa.debian.org/helmutg/rebootstrap.git

> so enabling the in-kernel Linux drivers seems preferable.
> Any tips on how I would do that? Are the Linux drivers ancient enough
> to require their own porting to x86_64, or will they just work?

They will just *not* work with 64bit. The glue code is not ready at all,
and I think it's really not useful to spend time on that when we have
the rump drivers which should be working fine.

Now, that being said, you can also use an initrd, see debian's
50_initrd.patch (which nobody has yet taken the time to clean according
the discussion at the time). That's enough to run a full Hurd system,
you can for instance take the initrd files from the debian installation
CD.

Samuel

  reply	other threads:[~2023-05-01 17:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 20:18 [PATCH v3 0/6] The remaining x86_64-gnu patches Sergey Bugaev
2023-04-29 20:18 ` [PATCH v3 1/6] hurd: Implement sigreturn for x86_64 Sergey Bugaev
2023-04-30 23:06   ` Samuel Thibault
2023-04-29 20:18 ` [PATCH v3 2/6] hurd: Implement longjmp " Sergey Bugaev
2023-04-30 23:16   ` Samuel Thibault
2023-04-29 20:18 ` [RFC PATCH v3 3/6] hurd: Replace reply port with a dead name on failed interruption Sergey Bugaev
2023-05-01  1:20   ` Samuel Thibault
2023-04-29 20:18 ` [PATCH v3 4/6] hurd: Add expected abilist files for x86_64 Sergey Bugaev
2023-04-30 23:18   ` Samuel Thibault
2023-05-01 10:20   ` Samuel Thibault
2023-05-01 17:33     ` Sergey Bugaev
2023-05-01 17:43       ` Samuel Thibault [this message]
2023-04-29 20:18 ` [RFC PATCH v3 5/6] hurd: Make it possible to call memcpy very early Sergey Bugaev
2023-04-30 23:21   ` Samuel Thibault
2023-04-29 20:18 ` [DO NOT PUSH PATCH v3 6/6] TMP hurd: Lower BRK_START Sergey Bugaev
2023-05-02 14:03 ` [PATCH v3 0/6] The remaining x86_64-gnu patches Joseph Myers
2023-05-02 14:16   ` Sergey Bugaev
2023-05-02 18:27     ` Joseph Myers
2023-05-02 15:17   ` Samuel Thibault
2023-05-02 18:24     ` Joseph Myers

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=20230501174308.23d43uojxq5z4yk6@begin \
    --to=samuel.thibault@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=bugaevc@gmail.com \
    --cc=flaviocruz@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=luca@orpolo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).