Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Sergey Bugaev
On Wed, May 10, 2023 at 9:05 PM Sergey Bugaev wrote: > _hurd_startup crashes on accessing 'args' it has just received from > the exec server in the __exec_startup_get_info. The data arrives > out-of-line, and... broken: > > > > argvType is { msgt_inline = 0, msgt_longform = 1, msgt_deallocate = 1

Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Sergey Bugaev
On Wed, May 10, 2023 at 7:39 PM Samuel Thibault wrote: > Sergey Bugaev, le mer. 10 mai 2023 19:30:20 +0300, a ecrit: > > Dynamic linking also adds its share of complexity, > > You can always create static builds of the various translators, by > running e.g. make proc.static in proc/ Thank you! --

Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Samuel Thibault
Sergey Bugaev, le mer. 10 mai 2023 19:30:20 +0300, a ecrit: > Dynamic linking also adds its share of complexity, You can always create static builds of the various translators, by running e.g. make proc.static in proc/ Samuel

Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Sergey Bugaev
An update from me: /hurd/startup starts up (which means that exec is now working -- how cool is that!) and then spawns auth and proc. But then proc task_terminate's itself (= exists with some error, likely), seemingly somewhere early, maybe even during ld.so startup -- before it gets a chance to o

Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Samuel Thibault
Sergey Bugaev, le mer. 10 mai 2023 14:51:55 +0300, a ecrit: > On Wed, May 10, 2023 at 1:43 PM Samuel Thibault > wrote: > > For now you'll just be faced with library dependencies, so I'd say just > > unpack all lib*.deb (+zlib1g*.deb) and you'll be done. > > I see, thanks. > > By the way, I'm no

Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Sergey Bugaev
On Wed, May 10, 2023 at 1:43 PM Samuel Thibault wrote: > For now you'll just be faced with library dependencies, so I'd say just > unpack all lib*.deb (+zlib1g*.deb) and you'll be done. I see, thanks. By the way, I'm now getting ../../isofs/lookup.c:224:1: error: conflicting types for ‘diskfs_g

Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Samuel Thibault
Sergey Bugaev, le mer. 10 mai 2023 13:25:25 +0300, a ecrit: > On Wed, May 10, 2023 at 3:55 AM Samuel Thibault > wrote: > > With the available .debs you should now be able to enable these. > > I'm afraid I'm going to need more guidance here. Your little tutorial > in readme [0] is helpful (thank

Re: [PATCH 00/41] The x86_64 port

2023-05-10 Thread Sergey Bugaev
Hello, On Wed, May 10, 2023 at 3:55 AM Samuel Thibault wrote: > With the available .debs you should now be able to enable these. I'm afraid I'm going to need more guidance here. Your little tutorial in readme [0] is helpful (thank you!), but I still have questions. [0]: https://people.debian.or

Re: [PATCH 00/41] The x86_64 port

2023-05-09 Thread Samuel Thibault
Hello, Pushed! Sergey Bugaev, le mar. 09 mai 2023 00:30:55 +0300, a ecrit: > One annoying warning that I get a lot of when building the Hurd with > GCC 13 is -Wenum-int-mismatch; here's one example: > > ../../trans/streamio.c:694:1: warning: conflicting types for > ‘trivfs_S_file_sync’ due to e

[PATCH 00/41] The x86_64 port

2023-05-08 Thread Sergey Bugaev
Hello! This is it -- my work on porting the Hurd proper to x86_64, and assorted fixes that came up. I've split into separate patches by components for ease of review. Most of the changes amount to being more strict about integer types: we can no longer use unsigned int, integer_t, size_t, vm_size