Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

On Fri, 4 Apr 2014, Andreas Schwab wrote: > The fixed version is here: git://git.code.sf.net/p/aranym/code Perhaps your LoadToFastRam changes warrant a release also? It's been a while (the FPU changes were committed in October/November). -- -- To UNSUBSCRIBE, email to debian-68k-requ...@li

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

Andreas Schwab dixit: >The fixed version is here: git://git.code.sf.net/p/aranym/code That’s a source repository. I was asking for released tarballs that have been packaged. But clearly I have been outvoted by the m68k porters. So please feel free to go ahead and break Debian/m68k on released AR

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

The fixed version is here: git://git.code.sf.net/p/aranym/code Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.o

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

Hi Finn, On Fri, Apr 4, 2014 at 10:31 AM, Finn Thain wrote: > Clearly there should be one architecture per user. I want my FPGA. I already got mine ;-) https://www.terasic.com.tw/cgi-bin/page/archive.pl?No=593 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

On Fri, 4 Apr 2014, Geert Uytterhoeven wrote: > On Fri, Apr 4, 2014 at 10:23 AM, Finn Thain > wrote: > >> Once we do have a fixed version, we can communicate that around. > > > > If upsteam python gets fixed and that creates work for you, then pin > > your python version until you can build a

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

On Fri, Apr 4, 2014 at 10:23 AM, Finn Thain wrote: >> Once we do have a fixed version, we can communicate that around. > > If upsteam python gets fixed and that creates work for you, then pin your > python version until you can build a new aranym, or somehow prevent the > new python from being upl

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

On Fri, 4 Apr 2014, Thorsten Glaser wrote: > Once we do have a fixed version, we can communicate that around. If upsteam python gets fixed and that creates work for you, then pin your python version until you can build a new aranym, or somehow prevent the new python from being uploaded. You pr

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

Andreas Schwab dixit: >Finn Thain writes: > >>Sorry, what? You seek to veto an upstream Python bug fix because it will >>lead to correct binaries that a certain emulator can't handle? That Yes, because of the value ARAnyM has for Linux/m68k development and especially testing – for example, con

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

Finn Thain writes: > until Aranym gets fixed. Aranym *is* fixed. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.deb

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

On Thu, 3 Apr 2014, Thorsten Glaser wrote: > Andreas Schwab dixit: > > >Andreas Schwab added the comment: > > > >> Enabling this *will* break Python on Linux/m68k > > > > ??? It will not of course, it will *fix* it. You have no idea what > > you are talking about. > > No: it will break Debian

Re: [issue20904] HAVE_PY_SET_53BIT_PRECISION for m68k

Andreas Schwab dixit: >There is no excuse for using a broken emulator. Sure, if nobody releases a fixed version… and even then, there’s got to be a grace period. I say that if you break ARAnyM you kill off Debian/m68k on ARAnyM (and I’ll have to shut down my buildd, too). >