Hello,

Thanks for the email.
The thing is I am not cross compiling. I am instead compiling from inside
Hurd (in Qemu).
Yet cannot seem to get it quite right (even though it compiles
successfully inside Hurd, when I copy it to /boot it panics on the next
reboot).

Is a cross compiling route recommended instead?


On Mon, Jun 16, 2025 at 2:41 AM Almudena Garcia <liberamenso10...@gmail.com>
wrote:

> Hi:
>
> To cross-compile gnumach from Linux you have to specify some flags in
> configure, to indicate the hurd architecture.
>
> You can find the flag list here:
> https://www.gnu.org/software/hurd/microkernel/mach/gnumach/building.html
>
> Read the instructions for non-Debian systems and 64-bit, and try again
>
> P.S.: I redirect this mail to bug-hurd, which is the main maillist now
>
> El lunes 16 de junio de 2025, Milos Nikic escribió:
> > Hello there,
> >
> > I am Milos, I am interested in writing code for Hurd.
> > I am developing inside qemu (on Arch linux) with debian
> > image debian-hurd-20230608.img.
> > It loads, boots and looks good! I can use it!
> > However, since I want to contribute code I need more than just that.
> >
> > I git pulled mig, gnumach and hurd.
> > I have installed MIG.
> >
> > $ mig --version
> > mig (GNU MIG) 1.8
> >
> > When i ".configure" and then make gnumach it passes.
> > However when i copy it to my /boot/ and then point GRUB to it, i get
> kernel
> > panic on next reboot:.
> >
> > "Kernel page fault at address 0xc1000000, eip = 0xc10a73f6
> > Kernel Page fault trap, eip 0xc10a73f6
> > kernel trap, type 14, code = 3
> > Dump of i386_saved_state c11dbe98:
> > EAX fffffffc EBX c008993c ECX 3fc22677 EDX 00008000
> > ESI c0ff6e28 EDI c0fffffe EBP c07a3010 ESP 00000004
> > CS 0008 SS 0000 DS 0010 ES 0010 FS 0010 GS 0010
> > v86:            DS 000c ES 0000 FS c037 GS c037
> > EIP c10a73f6 EFLAGS 00010016
> > trapno 14: Page fault, error 00000003
> > panic i386/i386/trap.c:347: kernel_trap: trap"
> >
> > I tried on the current HEAD, I also tried with the tag v1.8+git20230526
> > which is the code that is, I believe, pushed to debian repositories.
> >
> > I get the same kernel panic, no matter what commit I try.
> >
> > I would like to contribute, but I need a way to test my changes locally
> > before sending in patches.
> >
> > Is there a recommended way to develop and test? Or if you can help me
> what
> > exactly am i doing or, what am i missing.
> >
> > Thanks in advance,
> > Milos
> >
>
> --
> Enviado desde mi dispositivo Sailfish

Reply via email to