From: Sergey Bugaev <bugaevc@gmail.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
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 20:33:36 +0300 [thread overview]
Message-ID: <CAN9u=HeoLbKV9a=-ShWpucgv5cifymj00UeoiX8mTnAxi+SV8g@mail.gmail.com> (raw)
In-Reply-To: <20230501102030.ja2llkf36x3wcvjp@begin>
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, in which case, \o/
I can hardly believe it no longer only exists on my machine :) Did you
manage to run it?
Thank you for changing pthread_t to be pointer-sized, I was going to
do that next.
Here's some of my own news: I've got enough of Hurd ported and built
to get this:
$ file ext2fs/ext2fs ext2fs/ext2fs.static exec/exec proc/proc
ext2fs/ext2fs: ELF 64-bit LSB executable, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib/ld-x86-64.so.1, for
GNU/Hurd 0.0.0, with debug_info, not stripped
ext2fs/ext2fs.static: ELF 64-bit LSB executable, x86-64, version 1
(GNU/Linux), statically linked, for GNU/Hurd 0.0.0, with debug_info,
not stripped
exec/exec: ELF 64-bit LSB executable, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib/ld-x86-64.so.1, for
GNU/Hurd 0.0.0, with debug_info, not stripped
proc/proc: ELF 64-bit LSB executable, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib/ld-x86-64.so.1, for
GNU/Hurd 0.0.0, with debug_info, not stripped
Trying to run it, it of course does not work:
ext2fs: part:1:device:hd0: Invalid argument
This is because:
- I'm building --without-parted
- gnumach gets built without the Linux disk drivers
- I'm not even attaching a hard drive to the VM...
How do we proceed? I don't know enough about rump to get it building;
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?
Sergey
next prev parent reply other threads:[~2023-05-01 17:33 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 [this message]
2023-05-01 17:43 ` Samuel Thibault
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='CAN9u=HeoLbKV9a=-ShWpucgv5cifymj00UeoiX8mTnAxi+SV8g@mail.gmail.com' \
--to=bugaevc@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=flaviocruz@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=luca@orpolo.org \
--cc=samuel.thibault@gnu.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).