| Re: [hatari-devel] Preparing for next release 2.4 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Preparing for next release 2.4
- From: Teemu Hukkanen <tjhukkan@xxxxxx>
- Date: Mon, 27 Jun 2022 21:45:32 +0200
- Arc-authentication-results: i=1; ORIGINATING; auth=pass smtp.auth=tjhukkan smtp.mailfrom=tjhukkan@xxxxxx
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1656359155; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wnyasN29HUClUlHIYLG2opCzJaeXO3lBfjHIoUrTfBY=; b=APi+kOaDOdd73We5VwfTZEM3KN5VzvL6jDzW66jqQK9+0DFInsQJpdDBiDHx0OCNbdh8RG X9YB/FdT/RVhZ2zt3XlYPLPk2cEigvdft/zOCPTnR+ImLaFLCOTx6uLPfm1keFVGFh7hc0 PpM6H65MminhbCKRIO/667eaO0RsJQA=
- Arc-seal: i=1; s=meesny; d=iki.fi; t=1656359155; a=rsa-sha256; cv=none; b=F+dhbmpBcbzCbgn8j7MyGFZ1FSYeOWrEKLXfRCsbLoDBpxMQPNeruo1TnQzkLxL/iEo9ib iHuvm2/cRk4dpy7r6NXOf5aJljo53VeYZFVRAo44lulQkxmhlNvqm4tXrBkY0Hiy0G+FBl MfxNiC4FGTiMPVwFT45JO46YsM6Piz4=
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1656359155; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wnyasN29HUClUlHIYLG2opCzJaeXO3lBfjHIoUrTfBY=; b=EQ/yS0PMsD6IQhYkJsMuzLpZQqav71WGxr3zfjYeAtMEGVEgZdWUAmi0msL3WQgQbCyJjp kbEpT3RBpcZFHnlLTY8/IdjYZBLBgG1pAJocGNtBSihSz9xZz+yAGyizJhokEwmS/y8mxq TQFYYiq52N6NkdkyKYJ2dlxtAIKD0/M=
Nicolas Pomarède <npomarede@xxxxxxxxxxxx> writes:
> Le 20/06/2022 à 23:33, Eero Tamminen a écrit :
>> Hi,
>>
>> On 20.6.2022 20.48, Nicolas Pomarède wrote:
>>> with the work done recently by everyone, what are the open / blocking
>>> issue ?
>>>
>>> On my side, falcon's sound is fixed and I don't see any urgent fix to
>>> be done.
>> >
>>> Laurent will have a look at the DSP change and maybe fix it (or revert
>>> it).
>>>
>>> what do other need to push ?
>>
>> I have nothing that could not wait until after the release.
>>
>>
>> There's this one issue at atari-forum that would be good to be verified
>> that it's the same issue that Thomas already fixed, before release.
>>
>> I think all the Hatari docs can be updated to 2.4 while waiting couple
>> of days for the user to answer.
>>
>> Btw. There have also been few issues on atari-forum where it seems like
>> Hatari boolean options do not work (enabling NatFeats in one case,
>> selecting ext disassembly output in another), but I think in both case
>> it's under Windows, i.e. out of our hands.
>
> hi
>
> it seems the user didn't answer so far, so I think I will not wait too long.
>
> Unless someone needs to push urgent things to the repo, I ask to not
> commit anything after tomorrow (tuesday 28/6), then I think I can work
> on the release in the next days.
Hi,
A small patch has been sent my way for fixing hatari build on RISC-V,
the patch is attached.
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012255>
01-fix-conftypes-py-build-path.diff fix-rega0-for-riscv.patch
07-fix-python-ui-doc-install.patch series
09-fix-hconsole-doc-install.patch
root@v5:~/hatari/hatari-2.3.1+dfsg# cat debian/patches/fix-rega0-for-riscv.patch
Fix issue where REG_A0 is already defined by riscv64 platform
Index: hatari-2.3.1+dfsg/src/includes/m68000.h
===================================================================
--- hatari-2.3.1+dfsg.orig/src/includes/m68000.h 2020-12-26 21:50:12.000000000 +0000
+++ hatari-2.3.1+dfsg/src/includes/m68000.h 2022-05-26 01:37:55.028838540 +0000
@@ -26,6 +26,9 @@
#include "cycInt.h"
#include "log.h"
+#ifdef REG_A0
+#undef REG_A0
+#endif
/* 68000 Register defines */
enum {