Re: Help needed for debugging OCaml failure on m68k

To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, debian-68k@lists.debian.org
Subject: Re: Help needed for debugging OCaml failure on m68k
From: Stéphane Glondu <glondu@debian.org>
Date: Wed, 19 Jun 2024 12:37:42 +0200
Message-id: <[🔎] ef925a54-4b56-4790-a4a1-75b0b4c073a3@debian.org>
In-reply-to: <[🔎] fc32c08f9a09ff3700fcf93a7b377514a6900add.camel@physik.fu-berlin.de>
References: <[🔎] f618aec5-15e3-4dda-ac8f-742e130ab95b@debian.org> <[🔎] fc32c08f9a09ff3700fcf93a7b377514a6900add.camel@physik.fu-berlin.de>

Hi,

Le 19/06/2024 à 09:06, John Paul Adrian Glaubitz a écrit :

To reproduce the problem quickly:
- unpack ocaml 5.2.0 source package
- ./configure --enable-imprecise-c99-float-ops
- make coldstart

Is there some subtlety with thread local variables on m68k?


Can you please try reproduce the issue on the porterbox mitchy.debian.net first to
make sure it's not related to the QEMU build environment on the buildds?


I can reproduce the issue on mitchy.debian.net.


Cheers,

--
Stéphane

Reply to:

Follow-Ups:
- Re: Help needed for debugging OCaml failure on m68k
  - From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

References:
- Help needed for debugging OCaml failure on m68k
  - From: Stéphane Glondu <glondu@debian.org>
- Re: Help needed for debugging OCaml failure on m68k
  - From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

Prev by Date: Re: Help needed for debugging OCaml failure on m68k
Next by Date: Re: Help needed for debugging OCaml failure on m68k
Previous by thread: Re: Help needed for debugging OCaml failure on m68k
Next by thread: Re: Help needed for debugging OCaml failure on m68k
Index(es):
- Date
- Thread