maxima-discuss

[Maxima-discuss] Announcing 5.47.0

[Viktor T. T. <vt...@vt...>]

Dear all,

I just finished preparing the 5.47.0 release. Hopefully, no major glitches beyond the ones I caught, related to building the documentation. But please let me know if you run into any issues.

The tar.gz archive and RPMs (source, and GCL compiled binaries for CentOS/RHEL 7+) are uploaded. I updated the English-language project Web page with information on the new release.

Thanks to everyone for all the fixes and improvements in this version.


Viktor

Re: [Maxima-discuss] Announcing 5.47.0

[Wolfgang D. <wol...@da...>]

Am 01.06.23 um 02:38 schrieb Viktor T. Toth:
> Dear all,
> 
> I just finished preparing the 5.47.0 release. 

Thanks, Viktor.

Sorry for the short delay. I added a Windows installer now (I tested it 
on Windows 10 and Windows 11).
I build and released a 32-bit version too, although for 5.46.0 there are 
less than 1% downloads of the 32-bit version.

Currently: 50 downloads / week for 32-bit,
5547 downloads / week for the 64-bit installer.

Maybe for the next release, we should drop the 32-bit version?

Best regards, Wolfgang

Re: [Maxima-discuss] Announcing 5.47.0

[Viktor T. T. <vt...@vt...>]

Dear Wolfgang,

Well, I suppose it depends on how much trouble it is to build a 32-bit installer. The few folks who still download it presumably appreciate its availability, letting them run Maxima on older hardware or less capable VMs.

But if it is too much trouble then I believe dropping it is not an outrageous thing to do, considering the limited number of downloads.


Viktor


> -----Original Message-----
> From: Wolfgang Dautermann <wol...@da...>
> Sent: Saturday, June 3, 2023 7:57 AM
> To: max...@li...
> Subject: Re: [Maxima-discuss] Announcing 5.47.0
> 
> Am 01.06.23 um 02:38 schrieb Viktor T. Toth:
> > Dear all,
> >
> > I just finished preparing the 5.47.0 release.
> 
> Thanks, Viktor.
> 
> Sorry for the short delay. I added a Windows installer now (I tested it
> on Windows 10 and Windows 11).
> I build and released a 32-bit version too, although for 5.46.0 there are
> less than 1% downloads of the 32-bit version.
> 
> Currently: 50 downloads / week for 32-bit,
> 5547 downloads / week for the 64-bit installer.
> 
> Maybe for the next release, we should drop the 32-bit version?
> 
> Best regards, Wolfgang
> 
> 
> 
> _______________________________________________
> Maxima-discuss mailing list
> Max...@li...
> https://lists.sourceforge.net/lists/listinfo/maxima-discuss

Re: [Maxima-discuss] Announcing 5.47.0

[Wolfgang D. <wol...@da...>]

Am 03.06.23 um 21:23 schrieb Viktor T. Toth:
> Dear Wolfgang,
> 
> Well, I suppose it depends on how much trouble it is to build a
> 32-bit installer.

Building? No trouble at all. As I have everything, which is needed for 
builing the installer on my PC: Entering 3 command line commands and 
wait a few minutes. Well, 4 commands for a signed installer.


But as the installer does not only contain Maxima, but also other
projects, on which Maxima depends, the 32-bit version it is usually *NOT
SO GOOD* as the 64-bit installer.
It contains some older versions of the bundled third party programs. In
the current installer e.g. Gnuplot.

Their last 32-bit Windows installer (5.2.7) was published 2019 - and as
I include it, it is much older as for the 64-bit Maxima installer.
Well - I could try, if I can crosscompile it too...


And - of course - I do some manual testing before I upload an installer 
to Sourceforge:
install it on Win11 and/or Win10, check, that it installs and uninstalls
cleanly afterwards, check, that it works with CLISP and SBCL, check that
command line Maxima, XMaxima and wxMaxima works, etc.
*That* needs some time.

But I do such tests occasionally with the current development version
(there too with ABCL as a third Lisp), so I would recognize severe
issues with the windows installer during the development process (of 
Maxima and wxMaxima).

Best regards, Wolfgang

Re: [Maxima-discuss] Announcing 5.47.0

[Gunter K. <gu...@pe...>]

AFAICS it is hard to build a 32-bit install on a current Ubuntu: Of many 
packages the 32 bit version isn't supported any more, and others have 
been dropped from Ubuntu 23.04. Also many windows packages maxima 
depends on no more get updates for their 32-bit version which will they 
will be victims to bit rot and no more receive security updates.

Kind regards,

   Gunter.

Re: [Maxima-discuss] Announcing 5.47.0

[Viktor T. T. <vt...@vt...>]

I think it may be perfectly reasonable to say that 5.47 is the final 32-bit version, especially in light of the very small number of 32-bit downloads.


Viktor


> -----Original Message-----
> From: Gunter Königsmann <gu...@pe...>
> Sent: Sunday, June 4, 2023 3:49 PM
> To: Viktor T. Toth <vt...@vt...>; max...@li...
> Subject: Re: [Maxima-discuss] Announcing 5.47.0
> 
> AFAICS it is hard to build a 32-bit install on a current Ubuntu: Of many
> packages the 32 bit version isn't supported any more, and others have
> been dropped from Ubuntu 23.04. Also many windows packages maxima
> depends on no more get updates for their 32-bit version which will they
> will be victims to bit rot and no more receive security updates.
> 
> Kind regards,
> 
>    Gunter.

Re: [Maxima-discuss] Announcing 5.47.0

[ASSI <Str...@ne...>]

Viktor T. Toth writes:
> I just finished preparing the 5.47.0 release. Hopefully, no major
> glitches beyond the ones I caught, related to building the
> documentation. But please let me know if you run into any issues.

I still keep a bunch of fixes related to out-of-tree building for Cygwin
here:

https://repo.or.cz/maxima/cygwin.git/shortlog/refs/heads/cygwin-5_47

I can't rule out these are not suitable on different systems, but most
of it should be safe and I would encourage you to integrate them.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [Maxima-discuss] Announcing 5.47.0

[Gunter K. <gu...@pe...>]

It would be good if we un-broke out-of-tree builds.

And if we had a way of making sure that we don't break that feature again.

The only thing about yout path sets that I don't understand is:

@@ -12,6 
<https://repo.or.cz/maxima/cygwin.git/blob/3a1c2c2c7363a58814f9c94f47f966d4861634b1:/maxima-local.in#l12> 
+12,9 
<https://repo.or.cz/maxima/cygwin.git/blob/e983c8e84fe008d11d36316aac95da60f9088854:/maxima-local.in#l12> 
@@ MAXIMA_OBJDIR="@abs_top_builddir@/binary"
  export MAXIMA_OBJDIR
  MAXIMA_HTMLDIR=${MAXIMA_DOC_PREFIX}
  export MAXIMA_HTMLDIR
+CLISP_RUNTIME_PATH="@CLISP_RUNTIME_PATH@"
+export CLISP_RUNTIME_PATH
+PATH=${PATH}:${CLISP_RUNTIME_PATH%/*}
What is the last of these lines needed for - and what does "%/*" mean?

Kind regards,

     Gunter.

On 26.06.23 17:45, ASSI wrote:
> Viktor T. Toth writes:
>> I just finished preparing the 5.47.0 release. Hopefully, no major
>> glitches beyond the ones I caught, related to building the
>> documentation. But please let me know if you run into any issues.
> I still keep a bunch of fixes related to out-of-tree building for Cygwin
> here:
>
> https://repo.or.cz/maxima/cygwin.git/shortlog/refs/heads/cygwin-5_47
>
> I can't rule out these are not suitable on different systems, but most
> of it should be safe and I would encourage you to integrate them.
>
>
> Regards,
> Achim.

Re: [Maxima-discuss] Announcing 5.47.0

[Gunter K. <gu...@pe...>]

...and another one:


@@ -673,8 
<https://repo.or.cz/maxima/cygwin.git/blob/4e7d91c83562c5464f272ce0eb921f8d396a7281?f=doc/info/Makefile.am#l673> 
+673,8 
<https://repo.or.cz/maxima/cygwin.git/blob/fc669b159de52caf91a2b4a007ffc4f636a3c3d4:/doc/info/Makefile.am#l673> 
@@ all-local: html maxima.info maxima-index.lisp maxima-index-html.lisp
  infoname = maxima
  include $(top_srcdir)/common-info.mk
  maxima.info : maxima.texi $(maxima_TEXINFOS)
-       $(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) \
-         --split-size=1000000 $(srcdir)/maxima.texi
+ -$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) \
+         --no-split $(srcdir)/maxima.texi
Is it necessary to add that --no-split?

Kind regards,

   Gunter.

On 26.06.23 17:45, ASSI wrote:
> Viktor T. Toth writes:
>> I just finished preparing the 5.47.0 release. Hopefully, no major
>> glitches beyond the ones I caught, related to building the
>> documentation. But please let me know if you run into any issues.
> I still keep a bunch of fixes related to out-of-tree building for Cygwin
> here:
>
> https://repo.or.cz/maxima/cygwin.git/shortlog/refs/heads/cygwin-5_47
>
> I can't rule out these are not suitable on different systems, but most
> of it should be safe and I would encourage you to integrate them.
>
>
> Regards,
> Achim.

Re: [Maxima-discuss] Announcing 5.47.0

[Gunter K. <gu...@pe...>]

Added all the patches that I understood to the branch KoenGu/OutOfTreeBuild.


On my computer the result doesn't build, currently => Achim, can you 
help me finding out why?

Kind regards,

  Gunter.

On 09.07.23 08:44, Gunter Königsmann via Maxima-discuss wrote:
>
> ...and another one:
>
>
> @@ -673,8 
> <https://repo.or.cz/maxima/cygwin.git/blob/4e7d91c83562c5464f272ce0eb921f8d396a7281?f=doc/info/Makefile.am#l673> 
> +673,8 
> <https://repo.or.cz/maxima/cygwin.git/blob/fc669b159de52caf91a2b4a007ffc4f636a3c3d4:/doc/info/Makefile.am#l673> 
> @@ all-local: html maxima.info maxima-index.lisp maxima-index-html.lisp
>  infoname = maxima
>  include $(top_srcdir)/common-info.mk
>  maxima.info : maxima.texi $(maxima_TEXINFOS)
> -       $(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) \
> -         --split-size=1000000 $(srcdir)/maxima.texi
> + -$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) \
> +         --no-split $(srcdir)/maxima.texi
> Is it necessary to add that --no-split?
>
> Kind regards,
>
>   Gunter.
> On 26.06.23 17:45, ASSI wrote:
>> Viktor T. Toth writes:
>>> I just finished preparing the 5.47.0 release. Hopefully, no major
>>> glitches beyond the ones I caught, related to building the
>>> documentation. But please let me know if you run into any issues.
>> I still keep a bunch of fixes related to out-of-tree building for Cygwin
>> here:
>>
>> https://repo.or.cz/maxima/cygwin.git/shortlog/refs/heads/cygwin-5_47
>>
>> I can't rule out these are not suitable on different systems, but most
>> of it should be safe and I would encourage you to integrate them.
>>
>>
>> Regards,
>> Achim.
>
>
> _______________________________________________
> Maxima-discuss mailing list
> Max...@li...
> https://lists.sourceforge.net/lists/listinfo/maxima-discuss

Re: [Maxima-discuss] Announcing 5.47.0

[Gunter K. <gu...@pe...>]

Investigated a bit further: The patches seem to enable out-of-tree build 
for clisp, only - and I see two additional errors:

  * If I do an in-tree-build maxima with --enable-clisp-exec
    ./maxima-local claims src/binary-clisp/maxima.mem to be missing
    (which isn't the case).
  * and maxima cannot find the html index, in that case.

No idea if I have applied all the patches correctly: Seems like we have 
changed lots of places since the release...

Kind regards,

   Gunter.

On 09.07.23 10:17, Gunter Königsmann via Maxima-discuss wrote:
>
> Added all the patches that I understood to the branch 
> KoenGu/OutOfTreeBuild.
>
>
> On my computer the result doesn't build, currently => Achim, can you 
> help me finding out why?
>
> Kind regards,
>
>  Gunter.
>
> On 09.07.23 08:44, Gunter Königsmann via Maxima-discuss wrote:
>>
>> ...and another one:
>>
>>
>> @@ -673,8 
>> <https://repo.or.cz/maxima/cygwin.git/blob/4e7d91c83562c5464f272ce0eb921f8d396a7281?f=doc/info/Makefile.am#l673> 
>> +673,8 
>> <https://repo.or.cz/maxima/cygwin.git/blob/fc669b159de52caf91a2b4a007ffc4f636a3c3d4:/doc/info/Makefile.am#l673> 
>> @@ all-local: html maxima.info maxima-index.lisp maxima-index-html.lisp
>>  infoname = maxima
>>  include $(top_srcdir)/common-info.mk
>>  maxima.info : maxima.texi $(maxima_TEXINFOS)
>> -       $(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) \
>> -         --split-size=1000000 $(srcdir)/maxima.texi
>> + -$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) \
>> +         --no-split $(srcdir)/maxima.texi
>> Is it necessary to add that --no-split?
>>
>> Kind regards,
>>
>>   Gunter.
>> On 26.06.23 17:45, ASSI wrote:
>>> Viktor T. Toth writes:
>>>> I just finished preparing the 5.47.0 release. Hopefully, no major
>>>> glitches beyond the ones I caught, related to building the
>>>> documentation. But please let me know if you run into any issues.
>>> I still keep a bunch of fixes related to out-of-tree building for Cygwin
>>> here:
>>>
>>> https://repo.or.cz/maxima/cygwin.git/shortlog/refs/heads/cygwin-5_47
>>>
>>> I can't rule out these are not suitable on different systems, but most
>>> of it should be safe and I would encourage you to integrate them.
>>>
>>>
>>> Regards,
>>> Achim.
>>
>>
>> _______________________________________________
>> Maxima-discuss mailing list
>> Max...@li...
>> https://lists.sourceforge.net/lists/listinfo/maxima-discuss
>
>
> _______________________________________________
> Maxima-discuss mailing list
> Max...@li...
> https://lists.sourceforge.net/lists/listinfo/maxima-discuss

Re: [Maxima-discuss] Announcing 5.47.0

[ASSI <Str...@ne...>]

Gunter Königsmann via Maxima-discuss writes:
> +CLISP_RUNTIME_PATH="@CLISP_RUNTIME_PATH@"
  CLISP_RUNTIME_PATH="/usr/lib/clisp-2.49+/base/lisp.exe"
> +export CLISP_RUNTIME_PATH
> +PATH=${PATH}:${CLISP_RUNTIME_PATH%/*}
  PATH=${PATH}:${CLISP_RUNTIME_PATH%/*}
> What is the last of these lines needed for - and what does "%/*" mean?

It removes the trailing (non-directory) component in CLISP_RUNTIME_PATH
so that the directory lisp.exe is in can be added to the PATH (this is
necessary on Windows for clisp to work correctly).  The actual
expansions resulting for the Cygwin installation are shown above.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [Maxima-discuss] Announcing 5.47.0

[ASSI <Str...@ne...>]

Gunter Königsmann via Maxima-discuss writes:
> On my computer the result doesn't build, currently => Achim, can you
> help me finding out why?

Well, if you could tell me what exactly doesn't work?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [Maxima-discuss] Announcing 5.47.0

[ASSI <Str...@ne...>]

Gunter Königsmann via Maxima-discuss writes:
> ...and another one:
> + -$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) \
> +         --no-split $(srcdir)/maxima.texi
> Is it necessary to add that --no-split?

Not neccessary, but dsplitting info files has had no positive effect
whatsoever for more than a decade and might actually be detrimental to
performance when the info directory starts to have very many files in
it.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [Maxima-discuss] Announcing 5.47.0

[ASSI <Str...@ne...>]

Gunter Königsmann via Maxima-discuss writes:
> Investigated a bit further: The patches seem to enable out-of-tree
> build for clisp, only - and I see two additional errors:

That's the only Lisp available on Cygwin, so that's quite possible.

>  * If I do an in-tree-build maxima with --enable-clisp-exec
>    ./maxima-local claims src/binary-clisp/maxima.mem to be missing
>    (which isn't the case).

You might run a different clisp than you think in this case as
clisp-exec should not need the dump file at all.  In any case, I no
longer use that option on Cygwin for other reasons (the resulting
execcutable stops working if clisp is updated).  You need to check that
you've actually produced a new clisp executable with the memory dump and
that you call it correctly.

>  * and maxima cannot find the html index, in that case.

Seems to be another indication that the executable you invoke is in the
wrong place.

> No idea if I have applied all the patches correctly: Seems like we
> have changed lots of places since the release...

Yes, that's why I would love for these to be finally upstreamed.  :-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada