From sgougeon at free.fr  Mon Feb 10 14:15:16 2020
From: sgougeon at free.fr (Samuel Gougeon)
Date: Mon, 10 Feb 2020 14:15:16 +0100
Subject: [Scilab-Dev] ATOMS server 6.1 not ready / available
Message-ID: <2eae63b0-706a-3ff6-0b7a-63180b3ba035@free.fr>

Hello,

This morning, i still get (with the master)


> --> atomsRepositoryList
> ?ans? =
> ? "http://atoms.scilab.org/6.1"? "official"
>
> --> atomsSystemUpdate
> ""
> ? "gzip: TMPDIR\ATOMS~1\1_TOOLBOXES.gz: not in gzip format"
> WARNING: atomsDESCRIPTIONget: Extraction of the DESCRIPTION file 
> ('TMPDIR\ATOMS~1\1_TOOLBOXES.gz') has failed.
> Scanning repository http://atoms.scilab.org/6.1 ... Skipped
>
> at line?? 198 of function atomsDESCRIPTIONget ( 
> SCI\modules\atoms\macros\atoms_internals\atomsDESCRIPTIONget.sci line 
> 217 )
> at line??? 16 of function atomsSystemUpdate?? ( 
> SCI\modules\atoms\macros\atomsSystemUpdate.sci line 33 )
>
> All ATOMS repositories scan failed.
>
In atomsDownload(), we have well the download command (with SCI & TMPDIR 
replacements)

 ? ""SCI\tools\curl\curl.exe" --connect-timeout 5? -s 
"http://atoms.scilab.org/6.1/TOOLBOXES/64/windows.gz" -o 
"TMPDIR\ATOMS~1\1_TOOLBOXES.gz""

but in a web browser, the URL 
http://atoms.scilab.org/6.1/TOOLBOXES/64/windows.gz is still redirected 
and leads to a 404 error.

Regards
Samuel




From wrthissell at verizon.net  Sun Feb 16 20:05:46 2020
From: wrthissell at verizon.net (Rich Thissell)
Date: Sun, 16 Feb 2020 14:05:46 -0500
Subject: [Scilab-Dev] Please make Scilab 6.0.2 and 6.1.0 selinux enforcing
	compatible
References: <001e01d5e4fc$18b452a0$4a1cf7e0$.ref@verizon.net>
Message-ID: <001e01d5e4fc$18b452a0$4a1cf7e0$@verizon.net>

Dear Scilab developers,

                We are required to use selinux enforcing for information
assurance compliance.  I have noticed that scilab 6.0.2 does not start when
selinux is enforcing.  

                I recommend that you resolve this issue so that we may use
Scilab.

 

Sincerely yours,

 

Rich Thissell

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200216/190afad8/attachment.htm>

From Clement.David at esi-group.com  Mon Feb 17 09:28:54 2020
From: Clement.David at esi-group.com (=?iso-8859-1?Q?Cl=E9ment_David?=)
Date: Mon, 17 Feb 2020 08:28:54 +0000
Subject: [Scilab-Dev] Please make Scilab 6.0.2 and 6.1.0 selinux
	enforcing	compatible
In-Reply-To: <001e01d5e4fc$18b452a0$4a1cf7e0$@verizon.net>
References: <001e01d5e4fc$18b452a0$4a1cf7e0$.ref@verizon.net>
 <001e01d5e4fc$18b452a0$4a1cf7e0$@verizon.net>
Message-ID: <DB6PR0901MB1608B76E0809D53A0E02686EB0160@DB6PR0901MB1608.eurprd09.prod.outlook.com>

Hello Rich,

Thanks for the information, we already tried to fix some issues related to SELinux settings but this really depends on the machine administrator. As far as a stock Scilab binary (from www.scilab.org) embed its own JVM which requires executable stack, it might fail to start on SELinux enforcing mode. If you use a Scilab build from your operating system, this might work without issue as the JVM comes from your operating system and is properly tagged.

Do you have any issue with a Scilab from your operating system packaging system ?

Thanks,

--
Cl?ment

From: dev <dev-bounces at lists.scilab.org> On Behalf Of Rich Thissell
Sent: Sunday, February 16, 2020 8:06 PM
To: dev at lists.scilab.org
Subject: [Scilab-Dev] Please make Scilab 6.0.2 and 6.1.0 selinux enforcing compatible
Importance: High

Dear Scilab developers,
                We are required to use selinux enforcing for information assurance compliance.  I have noticed that scilab 6.0.2 does not start when selinux is enforcing.
                I recommend that you resolve this issue so that we may use Scilab.

Sincerely yours,

Rich Thissell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200217/f5d1805b/attachment.htm>

From sgougeon at free.fr  Mon Feb 17 10:19:00 2020
From: sgougeon at free.fr (Samuel Gougeon)
Date: Mon, 17 Feb 2020 10:19:00 +0100
Subject: [Scilab-Dev] Numerous .po fuzzy irrelevant and misleading
	translations
Message-ID: <ff227b32-47c8-7d1d-0bb3-5eea3fdc154c@free.fr>

Hello,

After some recent commit on CodeReview including some .po files, we can 
scan all .po files against fuzzy entries.
This yields a set of 1508 fuzzy entries, over almost 8700 msgid.
The issue is that, when we have a look to related translations, for more 
than 90% of them they are actually completely irrelevant. A very short 
sample (for fr_FR):

/#, fuzzy//
//msgid "Number of output event ports"//
//msgstr "Le nombre de lignes doit ?tre une puissance de deux."//
//
//#, fuzzy//
//msgid "The block must have at least two output ports"//
//msgstr "Le bloc Trigger doit avoir des valeurs discr?tes en entr?e."//
//
//#, fuzzy//
//msgid "Indices to extract"//
//msgstr "Bits ? extraire"//
//
//#, fuzzy//
//msgid "Number of outputs"//
//msgstr "Nombre de n?uds :"//
/

It is then easy to understand that errors messages or labels in 
interfaces will be completely misleading.

How about clearing all the fuzzy translations?

Best regards
Samuel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200217/1f0d0727/attachment.htm>

From Clement.David at esi-group.com  Wed Feb 19 16:08:30 2020
From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=)
Date: Wed, 19 Feb 2020 15:08:30 +0000
Subject: [Scilab-Dev] Numerous .po fuzzy irrelevant and
	misleading	translations
In-Reply-To: <ff227b32-47c8-7d1d-0bb3-5eea3fdc154c@free.fr>
References: <ff227b32-47c8-7d1d-0bb3-5eea3fdc154c@free.fr>
Message-ID: <DB6PR0901MB16080C2140A89CFB88263AEFB0100@DB6PR0901MB1608.eurprd09.prod.outlook.com>

Hello Samuel,

The fuzzy translation is cleared by the dispatchLocalization.sh script. So for 6.1, the commit [1] should remove them all.

[1]: https://codereview.scilab.org/#/c/21361/

--
Cl?ment

> -----Original Message-----
> From: dev <dev-bounces at lists.scilab.org> On Behalf Of Samuel Gougeon
> Sent: Monday, February 17, 2020 10:19 AM
> To: List dedicated to development questions <dev at lists.scilab.org>
> Subject: [Scilab-Dev] Numerous .po fuzzy irrelevant and misleading translations
> 
> Hello,
> 
> After some recent commit on CodeReview including some .po files, we can scan
> all .po files against fuzzy entries.
> This yields a set of 1508 fuzzy entries, over almost 8700 msgid.
> The issue is that, when we have a look to related translations, for more than
> 90% of them they are actually completely irrelevant. A very short sample (for
> fr_FR):
> 
> 
> #, fuzzy
> msgid "Number of output event ports"
> msgstr "Le nombre de lignes doit ?tre une puissance de deux."
> 
> #, fuzzy
> msgid "The block must have at least two output ports"
> msgstr "Le bloc Trigger doit avoir des valeurs discr?tes en entr?e."
> 
> #, fuzzy
> msgid "Indices to extract"
> msgstr "Bits ? extraire"
> 
> #, fuzzy
> msgid "Number of outputs"
> msgstr "Nombre de n?uds :"
> 
> 
> It is then easy to understand that errors messages or labels in interfaces will be
> completely misleading.
> 
> How about clearing all the fuzzy translations?
> 
> Best regards
> Samuel
> 
> 


From Clement.David at esi-group.com  Tue Feb 25 14:10:28 2020
From: Clement.David at esi-group.com (=?iso-8859-1?Q?Cl=E9ment_David?=)
Date: Tue, 25 Feb 2020 13:10:28 +0000
Subject: [Scilab-Dev] Scilab 6.1.0 is available!
Message-ID: <DB6PR0901MB1608E25F549F5E6C2E224096B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>

Dear Scilab-ers,



A brand new Scilab 6.1.0<https://www.scilab.org/download/6.1.0> is released today!



This version includes further improvement atop Scilab 6.0 for better stability and increased algorithm performance. It also includes a reworked display for more compact and meaningful value printing; web tools for HTTP, JSON support; better debug support and various algorithm rewrite/extension.



This first iteration of the 6.1 branch fixes up to 245 bugs and implements missing features from the 6.0.2 version. We would like to give a special thanks to Samuel and Stephane who have been very active this year.



If you find any critical issue or instability that might need a 6.1.x release please alert us<https://bugzilla.scilab.org/>. If you are a toolbox maintainer, please rebuild your code, upgrade it when needed and publish it to atoms.scilab.org<https://atoms.scilab.org/>.



For the complete list of changes and bugs fixed, please take a look at the CHANGES<https://help.scilab.org/CHANGES>  file.



--

Cl?ment on behalf of the Scilab team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200225/0b3732ad/attachment.htm>

From Clement.David at esi-group.com  Tue Feb 25 17:09:08 2020
From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=)
Date: Tue, 25 Feb 2020 16:09:08 +0000
Subject: [Scilab-Dev] [Scilab-users] Scilab 6.1.0 is available!
In-Reply-To: <B6DE3CD4-EB04-467F-9760-8BCB133F4B93@me.com>
References: <DB6PR0901MB1608E25F549F5E6C2E224096B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
 <B6DE3CD4-EB04-467F-9760-8BCB133F4B93@me.com>
Message-ID: <DB6PR0901MB1608F872EC55BBCE741F9C33B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>

Hello Heinz,

The macOS version is still in progress, we don't have any access to a macOS machine anymore and there are hard issues reported by Stephane (a hard crash in GUI mode, the required JVM installation, a non-signed packaging, at least...). So yes, we rely on the community (and especially Stephane) to ship a macOS binary; if you are willing to help, please contact him and keep in mind that it is a very complex task.

Note: this was also the case for Scilab 6.0.0 to 6.0.2.

Regards,

--
Cl?ment

> -----Original Message-----
> From: Heinz Nabielek <heinznabielek at me.com>
> Sent: Tuesday, February 25, 2020 4:52 PM
> To: Users mailing list for Scilab <users at lists.scilab.org>; Cl?ment David
> <Clement.David at esi-group.com>
> Cc: List dedicated to the development of Scilab <dev at lists.scilab.org>
> Subject: Re: [Scilab-users] Scilab 6.1.0 is available!
> 
> And where is the Mac version?
> Heinz
> 
> 
> 
> 
> > On 25.02.2020, at 14:10, Cl?ment David <Clement.David at esi-group.com>
> wrote:
> >
> > Dear Scilab-ers,
> >
> > A brand new Scilab 6.1.0 is released today!
> >
> > This version includes further improvement atop Scilab 6.0 for better stability
> and increased algorithm performance. It also includes a reworked display for
> more compact and meaningful value printing; web tools for HTTP, JSON support;
> better debug support and various algorithm rewrite/extension.
> >
> > This first iteration of the 6.1 branch fixes up to 245 bugs and implements
> missing features from the 6.0.2 version. We would like to give a special thanks
> to Samuel and Stephane who have been very active this year.
> >
> > If you find any critical issue or instability that might need a 6.1.x release please
> alert us. If you are a toolbox maintainer, please rebuild your code, upgrade it
> when needed and publish it to atoms.scilab.org.
> >
> > For the complete list of changes and bugs fixed, please take a look at the
> CHANGES  file.
> >
> > --
> > Cl?ment on behalf of the Scilab team
> > _______________________________________________
> > users mailing list
> > users at lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users


From sylvain.corlay at gmail.com  Thu Feb 27 13:49:46 2020
From: sylvain.corlay at gmail.com (Sylvain Corlay)
Date: Thu, 27 Feb 2020 13:49:46 +0100
Subject: [Scilab-Dev] Scilab 6.1.0 is available!
In-Reply-To: <DB6PR0901MB1608E25F549F5E6C2E224096B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
References: <DB6PR0901MB1608E25F549F5E6C2E224096B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
Message-ID: <CAK=Phk4_T0mk6O3Gb00R5VpbZgZToQro+y0Xn-dM8MW8nvkgaw@mail.gmail.com>

Congratulations on the release.

I am the author of the conda package for scilab, and unfortunately, it does
not seem that 6.1.0 can be successfully packaged for conda-forge with the
new requirement for the* <filesystem>* C++17 header, which requires *GCC 8*.

Conda-forge is still based on GCC 7, which is fairly recent, with C++17
enabled by default. Would you consider not using the <filesystem> from the
C++17 standard so that Scilab can be made available to a wider audience?

Another blocker to the packaging of Scilab is the outdated version of java
that is required by the GUI. Is there any plan to support a more recent
version of OpenJDK?

Best,

Sylvain Corlay

On Tue, Feb 25, 2020 at 2:10 PM Cl?ment David <Clement.David at esi-group.com>
wrote:

> Dear Scilab-ers,
>
>
>
> A brand new Scilab 6.1.0 <https://www.scilab.org/download/6.1.0> is
> released today!
>
>
>
> This version includes further improvement atop Scilab 6.0 for better
> stability and increased algorithm performance. It also includes a reworked
> display for more compact and meaningful value printing; web tools for HTTP,
> JSON support; better debug support and various algorithm rewrite/extension.
>
>
>
> This first iteration of the 6.1 branch fixes up to 245 bugs and implements
> missing features from the 6.0.2 version. We would like to give a special
> thanks to Samuel and Stephane who have been very active this year.
>
>
>
> If you find any critical issue or instability that might need a 6.1.x
> release please alert us <https://bugzilla.scilab.org/>. If you are a
> toolbox maintainer, please rebuild your code, upgrade it when needed and
> publish it to atoms.scilab.org.
>
>
>
> For the complete list of changes and bugs fixed, please take a look at the
> CHANGES <https://help.scilab.org/CHANGES>  file.
>
>
>
> --
>
> Cl?ment on behalf of the Scilab team
> _______________________________________________
> dev mailing list
> dev at lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200227/ff72c07e/attachment.htm>

From Clement.David at esi-group.com  Thu Feb 27 14:25:25 2020
From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=)
Date: Thu, 27 Feb 2020 13:25:25 +0000
Subject: [Scilab-Dev] Scilab 6.1.0 is available!
In-Reply-To: <CAK=Phk4_T0mk6O3Gb00R5VpbZgZToQro+y0Xn-dM8MW8nvkgaw@mail.gmail.com>
References: <DB6PR0901MB1608E25F549F5E6C2E224096B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
 <CAK=Phk4_T0mk6O3Gb00R5VpbZgZToQro+y0Xn-dM8MW8nvkgaw@mail.gmail.com>
Message-ID: <DB6PR0901MB16082AC1FB1EB89FDCCA9A96B0EB0@DB6PR0901MB1608.eurprd09.prod.outlook.com>

Hello Sylvain,

First, thank you for your work on the conda packaging. The c++17 requirements is only needed for a single file that is used to implement fullpath() (named fullpath.cpp). The used API is reduced to std::filesystem::weakly_canonical and std::filesystem::absolute [1]. I guess using a light patch might relax the use of the filesystem header, for example, something like [2].

About the Java8 requirement, I guess you could ./configure --without-xcos as a first approach. I started porting the Java code out of javax.xml.bind [3] but that's very repetitive and error prone work.

[1]: https://codereview.scilab.org/#/c/21041/25/scilab/modules/fileio/src/cpp/fullpath.cpp
[2]: https://stackoverflow.com/questions/45867379/why-does-gcc-not-seem-to-have-the-filesystem-standard-library
[3]: https://codereview.scilab.org/#/c/20630/

Regards,

--
Cl?ment

> -----Original Message-----
> From: dev <dev-bounces at lists.scilab.org> On Behalf Of Sylvain Corlay
> Sent: Thursday, February 27, 2020 1:50 PM
> To: List dedicated to the development of Scilab <dev at lists.scilab.org>
> Subject: Re: [Scilab-Dev] Scilab 6.1.0 is available!
> 
> Congratulations on the release.
> 
> I am the author of the conda package for scilab, and unfortunately, it does not
> seem that 6.1.0 can be successfully packaged for conda-forge with the new
> requirement for the <filesystem> C++17 header, which requires GCC 8.
> 
> Conda-forge is still based on GCC 7, which is fairly recent, with C++17 enabled by
> default. Would you consider not using the <filesystem> from the C++17 standard
> so that Scilab can be made available to a wider audience?
> 
> Another blocker to the packaging of Scilab is the outdated version of java that is
> required by the GUI. Is there any plan to support a more recent version of
> OpenJDK?
> 
> Best,
> 
> Sylvain Corlay
> 
> On Tue, Feb 25, 2020 at 2:10 PM Cl?ment David <Clement.David at esi-
> group.com <mailto:Clement.David at esi-group.com> > wrote:
> 
> 
> 	Dear Scilab-ers,
> 
> 
> 
> 	A brand new Scilab 6.1.0 <https://www.scilab.org/download/6.1.0>  is
> released today!
> 
> 
> 
> 	This version includes further improvement atop Scilab 6.0 for better
> stability and increased algorithm performance. It also includes a reworked
> display for more compact and meaningful value printing; web tools for HTTP,
> JSON support; better debug support and various algorithm rewrite/extension.
> 
> 
> 
> 	This first iteration of the 6.1 branch fixes up to 245 bugs and implements
> missing features from the 6.0.2 version. We would like to give a special thanks
> to Samuel and Stephane who have been very active this year.
> 
> 
> 
> 	If you find any critical issue or instability that might need a 6.1.x release
> please alert us <https://bugzilla.scilab.org/> . If you are a toolbox maintainer,
> please rebuild your code, upgrade it when needed and publish it to
> atoms.scilab.org <https://atoms.scilab.org/> .
> 
> 
> 
> 	For the complete list of changes and bugs fixed, please take a look at
> the CHANGES <https://help.scilab.org/CHANGES>   file.
> 
> 
> 
> 	--
> 
> 	Cl?ment on behalf of the Scilab team
> 
> 	_______________________________________________
> 	dev mailing list
> 	dev at lists.scilab.org <mailto:dev at lists.scilab.org>
> 	http://lists.scilab.org/mailman/listinfo/dev
> 


From sylvain.corlay at gmail.com  Thu Feb 27 14:28:44 2020
From: sylvain.corlay at gmail.com (Sylvain Corlay)
Date: Thu, 27 Feb 2020 14:28:44 +0100
Subject: [Scilab-Dev] Scilab 6.1.0 is available!
In-Reply-To: <DB6PR0901MB16082AC1FB1EB89FDCCA9A96B0EB0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
References: <DB6PR0901MB1608E25F549F5E6C2E224096B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
 <CAK=Phk4_T0mk6O3Gb00R5VpbZgZToQro+y0Xn-dM8MW8nvkgaw@mail.gmail.com>
 <DB6PR0901MB16082AC1FB1EB89FDCCA9A96B0EB0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
Message-ID: <CAK=Phk6VwA7ox+iAQs_HEBPXV7ffkHH7-V40-Xh_6L=xNd9U6g@mail.gmail.com>

Hi Cl?ment,

Regarding the Java, we already skip xcos in the build but we were really
hoping that we could start including it with this version.

For the filesystem thingy, I will be patching the source as part of the
conda recipe to use <experimental/filesystem> instead and see how it goes -
although it would be really nice if we could support more compilers out of
the box.

Sylvain

On Thu, Feb 27, 2020 at 2:25 PM Cl?ment David <Clement.David at esi-group.com>
wrote:

> Hello Sylvain,
>
> First, thank you for your work on the conda packaging. The c++17
> requirements is only needed for a single file that is used to implement
> fullpath() (named fullpath.cpp). The used API is reduced to
> std::filesystem::weakly_canonical and std::filesystem::absolute [1]. I
> guess using a light patch might relax the use of the filesystem header, for
> example, something like [2].
>
> About the Java8 requirement, I guess you could ./configure --without-xcos
> as a first approach. I started porting the Java code out of javax.xml.bind
> [3] but that's very repetitive and error prone work.
>
> [1]:
> https://codereview.scilab.org/#/c/21041/25/scilab/modules/fileio/src/cpp/fullpath.cpp
> [2]:
> https://stackoverflow.com/questions/45867379/why-does-gcc-not-seem-to-have-the-filesystem-standard-library
> [3]: https://codereview.scilab.org/#/c/20630/
>
> Regards,
>
> --
> Cl?ment
>
> > -----Original Message-----
> > From: dev <dev-bounces at lists.scilab.org> On Behalf Of Sylvain Corlay
> > Sent: Thursday, February 27, 2020 1:50 PM
> > To: List dedicated to the development of Scilab <dev at lists.scilab.org>
> > Subject: Re: [Scilab-Dev] Scilab 6.1.0 is available!
> >
> > Congratulations on the release.
> >
> > I am the author of the conda package for scilab, and unfortunately, it
> does not
> > seem that 6.1.0 can be successfully packaged for conda-forge with the new
> > requirement for the <filesystem> C++17 header, which requires GCC 8.
> >
> > Conda-forge is still based on GCC 7, which is fairly recent, with C++17
> enabled by
> > default. Would you consider not using the <filesystem> from the C++17
> standard
> > so that Scilab can be made available to a wider audience?
> >
> > Another blocker to the packaging of Scilab is the outdated version of
> java that is
> > required by the GUI. Is there any plan to support a more recent version
> of
> > OpenJDK?
> >
> > Best,
> >
> > Sylvain Corlay
> >
> > On Tue, Feb 25, 2020 at 2:10 PM Cl?ment David <Clement.David at esi-
> > group.com <mailto:Clement.David at esi-group.com> > wrote:
> >
> >
> >       Dear Scilab-ers,
> >
> >
> >
> >       A brand new Scilab 6.1.0 <https://www.scilab.org/download/6.1.0>
> is
> > released today!
> >
> >
> >
> >       This version includes further improvement atop Scilab 6.0 for
> better
> > stability and increased algorithm performance. It also includes a
> reworked
> > display for more compact and meaningful value printing; web tools for
> HTTP,
> > JSON support; better debug support and various algorithm
> rewrite/extension.
> >
> >
> >
> >       This first iteration of the 6.1 branch fixes up to 245 bugs and
> implements
> > missing features from the 6.0.2 version. We would like to give a special
> thanks
> > to Samuel and Stephane who have been very active this year.
> >
> >
> >
> >       If you find any critical issue or instability that might need a
> 6.1.x release
> > please alert us <https://bugzilla.scilab.org/> . If you are a toolbox
> maintainer,
> > please rebuild your code, upgrade it when needed and publish it to
> > atoms.scilab.org <https://atoms.scilab.org/> .
> >
> >
> >
> >       For the complete list of changes and bugs fixed, please take a
> look at
> > the CHANGES <https://help.scilab.org/CHANGES>   file.
> >
> >
> >
> >       --
> >
> >       Cl?ment on behalf of the Scilab team
> >
> >       _______________________________________________
> >       dev mailing list
> >       dev at lists.scilab.org <mailto:dev at lists.scilab.org>
> >       http://lists.scilab.org/mailman/listinfo/dev
> >
>
> _______________________________________________
> dev mailing list
> dev at lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200227/0decba08/attachment.htm>

From sylvain.corlay at gmail.com  Thu Feb 27 16:12:23 2020
From: sylvain.corlay at gmail.com (Sylvain Corlay)
Date: Thu, 27 Feb 2020 16:12:23 +0100
Subject: [Scilab-Dev] Scilab 6.1.0 is available!
In-Reply-To: <CAK=Phk6VwA7ox+iAQs_HEBPXV7ffkHH7-V40-Xh_6L=xNd9U6g@mail.gmail.com>
References: <DB6PR0901MB1608E25F549F5E6C2E224096B0ED0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
 <CAK=Phk4_T0mk6O3Gb00R5VpbZgZToQro+y0Xn-dM8MW8nvkgaw@mail.gmail.com>
 <DB6PR0901MB16082AC1FB1EB89FDCCA9A96B0EB0@DB6PR0901MB1608.eurprd09.prod.outlook.com>
 <CAK=Phk6VwA7ox+iAQs_HEBPXV7ffkHH7-V40-Xh_6L=xNd9U6g@mail.gmail.com>
Message-ID: <CAK=Phk45qLSXaPXy7S2M1bkYCBw132YCj+b10tEkF2mRMCDVJQ@mail.gmail.com>

Patching the source to use <experimental/filesystem> resolves that
particular issue with C++17 in GCC7.

However, the Scilab build now fails with many occurrences of the error:

error: template with C linkage

- You can see the raw build logs here:
https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/125787/logs/7
- The scilab recipe update including the patches for <filesystem> is
available here: https://github.com/conda-forge/scilab-feedstock/pull/11

Officially supporting older versions of GCC than GCC 8 (which is from May
2018) would be greatly appreciated.

Best,


On Thu, Feb 27, 2020 at 2:28 PM Sylvain Corlay <sylvain.corlay at gmail.com>
wrote:

> Hi Cl?ment,
>
> Regarding the Java, we already skip xcos in the build but we were really
> hoping that we could start including it with this version.
>
> For the filesystem thingy, I will be patching the source as part of the
> conda recipe to use <experimental/filesystem> instead and see how it goes -
> although it would be really nice if we could support more compilers out of
> the box.
>
> Sylvain
>
> On Thu, Feb 27, 2020 at 2:25 PM Cl?ment David <Clement.David at esi-group.com>
> wrote:
>
>> Hello Sylvain,
>>
>> First, thank you for your work on the conda packaging. The c++17
>> requirements is only needed for a single file that is used to implement
>> fullpath() (named fullpath.cpp). The used API is reduced to
>> std::filesystem::weakly_canonical and std::filesystem::absolute [1]. I
>> guess using a light patch might relax the use of the filesystem header, for
>> example, something like [2].
>>
>> About the Java8 requirement, I guess you could ./configure --without-xcos
>> as a first approach. I started porting the Java code out of javax.xml.bind
>> [3] but that's very repetitive and error prone work.
>>
>> [1]:
>> https://codereview.scilab.org/#/c/21041/25/scilab/modules/fileio/src/cpp/fullpath.cpp
>> [2]:
>> https://stackoverflow.com/questions/45867379/why-does-gcc-not-seem-to-have-the-filesystem-standard-library
>> [3]: https://codereview.scilab.org/#/c/20630/
>>
>> Regards,
>>
>> --
>> Cl?ment
>>
>> > -----Original Message-----
>> > From: dev <dev-bounces at lists.scilab.org> On Behalf Of Sylvain Corlay
>> > Sent: Thursday, February 27, 2020 1:50 PM
>> > To: List dedicated to the development of Scilab <dev at lists.scilab.org>
>> > Subject: Re: [Scilab-Dev] Scilab 6.1.0 is available!
>> >
>> > Congratulations on the release.
>> >
>> > I am the author of the conda package for scilab, and unfortunately, it
>> does not
>> > seem that 6.1.0 can be successfully packaged for conda-forge with the
>> new
>> > requirement for the <filesystem> C++17 header, which requires GCC 8.
>> >
>> > Conda-forge is still based on GCC 7, which is fairly recent, with C++17
>> enabled by
>> > default. Would you consider not using the <filesystem> from the C++17
>> standard
>> > so that Scilab can be made available to a wider audience?
>> >
>> > Another blocker to the packaging of Scilab is the outdated version of
>> java that is
>> > required by the GUI. Is there any plan to support a more recent version
>> of
>> > OpenJDK?
>> >
>> > Best,
>> >
>> > Sylvain Corlay
>> >
>> > On Tue, Feb 25, 2020 at 2:10 PM Cl?ment David <Clement.David at esi-
>> > group.com <mailto:Clement.David at esi-group.com> > wrote:
>> >
>> >
>> >       Dear Scilab-ers,
>> >
>> >
>> >
>> >       A brand new Scilab 6.1.0 <https://www.scilab.org/download/6.1.0>
>> is
>> > released today!
>> >
>> >
>> >
>> >       This version includes further improvement atop Scilab 6.0 for
>> better
>> > stability and increased algorithm performance. It also includes a
>> reworked
>> > display for more compact and meaningful value printing; web tools for
>> HTTP,
>> > JSON support; better debug support and various algorithm
>> rewrite/extension.
>> >
>> >
>> >
>> >       This first iteration of the 6.1 branch fixes up to 245 bugs and
>> implements
>> > missing features from the 6.0.2 version. We would like to give a
>> special thanks
>> > to Samuel and Stephane who have been very active this year.
>> >
>> >
>> >
>> >       If you find any critical issue or instability that might need a
>> 6.1.x release
>> > please alert us <https://bugzilla.scilab.org/> . If you are a toolbox
>> maintainer,
>> > please rebuild your code, upgrade it when needed and publish it to
>> > atoms.scilab.org <https://atoms.scilab.org/> .
>> >
>> >
>> >
>> >       For the complete list of changes and bugs fixed, please take a
>> look at
>> > the CHANGES <https://help.scilab.org/CHANGES>   file.
>> >
>> >
>> >
>> >       --
>> >
>> >       Cl?ment on behalf of the Scilab team
>> >
>> >       _______________________________________________
>> >       dev mailing list
>> >       dev at lists.scilab.org <mailto:dev at lists.scilab.org>
>> >       http://lists.scilab.org/mailman/listinfo/dev
>> >
>>
>> _______________________________________________
>> dev mailing list
>> dev at lists.scilab.org
>> http://lists.scilab.org/mailman/listinfo/dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200227/6b1523dd/attachment.htm>