Re: Error building Hurd on an existing Hurd

Guys thank you for your patience. I realize the problem is my MIG was not up to date. A few days ago I compiled an old version MIG from source and used it. So I removed the old one and installed the latest MIG from apt. The following instructions suggested by jbranso works fine: $ apt get build

Re: [PATCH gnumach] ioapic: Initially mask all IRQs individually

Applied, thanks! Damien Zammit, le lun. 21 oct. 2024 03:22:22 +, a ecrit: > This fixes a spurious intnull(9) from occurring on real hardware > during ACPI startup when compiled with --enable-apic > > --- > i386/i386at/ioapic.c | 9 + > 1 file changed, 9 insertions(+) > > diff --git

Re: [PATCH 2/2 hurd] acpi: Link to libirqhelp

Applied, thanks! Damien Zammit, le lun. 21 oct. 2024 03:21:46 +, a ecrit: > This change is required when the libacpica library is updated > to link with hurd library irqhelp. > --- > acpi/Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/acpi/Makefile b/acpi/M

Re: [PATCH 1/2 libacpica] irqhelp: Add interrupt handler registration support

Applied, thanks! Damien Zammit, le lun. 21 oct. 2024 03:21:41 +, a ecrit: > --- > debian/patches/acgnu.diff | 34 ++--- > debian/patches/acpi-init-files.diff | 8 ++- > debian/patches/add-makefile.diff| 2 +- > 3 files changed, 39 insertions(+), 5 d

Re: [PATCH hurd] irqhelp: Dont bail when cannot connect to acpi

Hello, Damien Zammit, le lun. 21 oct. 2024 03:21:24 +, a ecrit: > acpi translator will only call the irqhelp api with fixed gsi during startup, > so won't require itself to be started yet. Ok, but we want to make irqhelp_install_interrupt_handler emit a different error message when acpidev ==

Re: Error building Hurd on an existing Hurd

On Mon, Oct 21, 2024 at 9:53 PM Samuel Thibault wrote: > Ah ok. > > Yes :) Good :) > He said we was using > > https://mail.gnu.org/archive/html/bug-hurd/2023-01/msg00132.html I admit I didn't follow the link in the original message... Those are my notes about bootstrapping a toolchain & cross-c

Re: Error building Hurd on an existing Hurd

Sergey Bugaev, le lun. 21 oct. 2024 21:49:59 +0300, a ecrit: > On Mon, Oct 21, 2024 at 9:38 PM Samuel Thibault > wrote: > > Sergey Bugaev, le lun. 21 oct. 2024 14:47:10 +0300, a ecrit: > > > You must > > > have a fresh enough MIG build (that already generates references to > > > mach_port_name_in

Re: Error building Hurd on an existing Hurd

On Mon, Oct 21, 2024 at 9:38 PM Samuel Thibault wrote: > Sergey Bugaev, le lun. 21 oct. 2024 14:47:10 +0300, a ecrit: > > You must > > have a fresh enough MIG build (that already generates references to > > mach_port_name_inlined_t), but older gnumach headers (that don't yet > > define mach_port_n

Re: Error building Hurd on an existing Hurd

Sergey Bugaev, le lun. 21 oct. 2024 14:47:10 +0300, a ecrit: > On Mon, Oct 21, 2024 at 9:21 AM Zhaoming Luo wrote: > > I am trying to build Hurd (76419b67...) from source on an existing Hurd. I > > found this post. However, when I tried ./configure && make, I got the > > following error: > > > >

Re: Error building Hurd on an existing Hurd

October 21, 2024 at 7:47 AM, "Sergey Bugaev" mailto:buga...@gmail.com?to=%22Sergey%20Bugaev%22%20%3Cbugaevc%40gmail.com%3E > wrote: > > On Mon, Oct 21, 2024 at 9:21 AM Zhaoming Luo wrote: > > > > > Hi, > > > Hi, > > > > > I am trying to build Hurd (76419b67...) from source on an existing

Re: [PATCH hurd]: adding /dev/rtc device

Zhaoming Luo, le lun. 21 oct. 2024 20:51:21 +0800, a ecrit: > On 10/21/24 8:12 PM, Samuel Thibault wrote: > > I mean that it probably doesn't have to be in kernelland, and rather be > > a userland translator. > > Do you mean we can implement an userland translator (it is also a rtc device > driver

Re: [PATCH hurd]: adding /dev/rtc device

On 10/21/24 8:12 PM, Samuel Thibault wrote: Thank you for your patience, but there are still a few things I don't understand. I mean that it probably doesn't have to be in kernelland, and rather be a userland translator. Do you mean we can implement an userland translator (it is also a rtc de

Re: [PATCH hurd]: adding /dev/rtc device

Zhaoming Luo, le lun. 21 oct. 2024 20:04:23 +0800, a ecrit: > Then perhaps 'adding /dev/rtc device' should be removed from 'small hack > entries', or this entry includes implementing a rtc mach device? For me implementing the device driver was implied :) > In addition to that, I'm quite confused

Re: [PATCH hurd]: adding /dev/rtc device

On 10/21/24 7:37 PM, Samuel Thibault wrote: Zhaoming Luo, le lun. 21 oct. 2024 19:31:19 +0800, a ecrit: Adding /dev/rtc device in the Hurd as described on [1]contributing website. /dev/rtc is useless until rtc and the functions for accessing it are added in dev_name_list in GNU mach. So there

Re: Error building Hurd on an existing Hurd

On Mon, Oct 21, 2024 at 9:21 AM Zhaoming Luo wrote: > Hi, Hi, > I am trying to build Hurd (76419b67...) from source on an existing Hurd. I > found this post. However, when I tried ./configure && make, I got the > following error: > > default_pagerUser.c: In function 'default_pager_object_creat

Re: [PATCH hurd]: adding /dev/rtc device

Zhaoming Luo, le lun. 21 oct. 2024 19:31:19 +0800, a ecrit: > Adding /dev/rtc device in the Hurd as described on [1]contributing website. > > /dev/rtc is useless until rtc and the functions for accessing it are added in > dev_name_list in GNU mach. So there is no real reason to commit this for no

[PATCH hurd]: adding /dev/rtc device

Adding /dev/rtc device in the Hurd as described on contributing website . /dev/rtc is useless until rtc and the functions for accessing it are added in dev_name_list in GNU mach. ---  sutils/MAKEDEV.sh | 4 +++-  1 file changed, 3 i