<div dir="ltr">Hello,<div><br></div><div>Is there any update on the support of GCC 7 for Scilab 6.1?</div><div><br></div><div>This is a major blocker for us to package it for the conda ecosystem.</div><div><br></div><div>Best,</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 27, 2020 at 4:12 PM Sylvain Corlay <<a href="mailto:sylvain.corlay@gmail.com">sylvain.corlay@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Patching the source to use <experimental/filesystem> resolves that particular issue with C++17 in GCC7.</div><div><br></div><div>However, the Scilab build now fails with many occurrences of the error:</div><br><font face="monospace">error: template with C linkage</font><div><font face="monospace"><br></font></div><div><font face="arial, sans-serif">- You can see the raw build logs here: </font><a href="https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/125787/logs/7" target="_blank">https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/125787/logs/7</a></div><div>- The scilab recipe update including the patches for <filesystem> is available here: <a href="https://github.com/conda-forge/scilab-feedstock/pull/11" target="_blank">https://github.com/conda-forge/scilab-feedstock/pull/11</a></div><div><br></div><div>Officially supporting older versions of GCC than GCC 8 (which is from May 2018) would be greatly appreciated.<br></div><div><br></div><div>Best,</div><div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 27, 2020 at 2:28 PM Sylvain Corlay <<a href="mailto:sylvain.corlay@gmail.com" target="_blank">sylvain.corlay@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Clément,<div><br></div><div>Regarding the Java, we already skip xcos in the build but we were really hoping that we could start including it with this version.</div><div><br></div><div>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.</div><div><br></div><div>Sylvain</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 27, 2020 at 2:25 PM Clément David <<a href="mailto:Clement.David@esi-group.com" target="_blank">Clement.David@esi-group.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Sylvain,<br>
<br>
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].<br>
<br>
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.<br>
<br>
[1]: <a href="https://codereview.scilab.org/#/c/21041/25/scilab/modules/fileio/src/cpp/fullpath.cpp" rel="noreferrer" target="_blank">https://codereview.scilab.org/#/c/21041/25/scilab/modules/fileio/src/cpp/fullpath.cpp</a><br>
[2]: <a href="https://stackoverflow.com/questions/45867379/why-does-gcc-not-seem-to-have-the-filesystem-standard-library" rel="noreferrer" target="_blank">https://stackoverflow.com/questions/45867379/why-does-gcc-not-seem-to-have-the-filesystem-standard-library</a><br>
[3]: <a href="https://codereview.scilab.org/#/c/20630/" rel="noreferrer" target="_blank">https://codereview.scilab.org/#/c/20630/</a><br>
<br>
Regards,<br>
<br>
--<br>
Clément<br>
<br>
> -----Original Message-----<br>
> From: dev <<a href="mailto:dev-bounces@lists.scilab.org" target="_blank">dev-bounces@lists.scilab.org</a>> On Behalf Of Sylvain Corlay<br>
> Sent: Thursday, February 27, 2020 1:50 PM<br>
> To: List dedicated to the development of Scilab <<a href="mailto:dev@lists.scilab.org" target="_blank">dev@lists.scilab.org</a>><br>
> Subject: Re: [Scilab-Dev] Scilab 6.1.0 is available!<br>
> <br>
> Congratulations on the release.<br>
> <br>
> I am the author of the conda package for scilab, and unfortunately, it does not<br>
> seem that 6.1.0 can be successfully packaged for conda-forge with the new<br>
> requirement for the <filesystem> C++17 header, which requires GCC 8.<br>
> <br>
> Conda-forge is still based on GCC 7, which is fairly recent, with C++17 enabled by<br>
> default. Would you consider not using the <filesystem> from the C++17 standard<br>
> so that Scilab can be made available to a wider audience?<br>
> <br>
> Another blocker to the packaging of Scilab is the outdated version of java that is<br>
> required by the GUI. Is there any plan to support a more recent version of<br>
> OpenJDK?<br>
> <br>
> Best,<br>
> <br>
> Sylvain Corlay<br>
> <br>
> On Tue, Feb 25, 2020 at 2:10 PM Clément David <Clement.David@esi-<br>
> <a href="http://group.com" rel="noreferrer" target="_blank">group.com</a> <mailto:<a href="mailto:Clement.David@esi-group.com" target="_blank">Clement.David@esi-group.com</a>> > wrote:<br>
> <br>
> <br>
> Dear Scilab-ers,<br>
> <br>
> <br>
> <br>
> A brand new Scilab 6.1.0 <<a href="https://www.scilab.org/download/6.1.0" rel="noreferrer" target="_blank">https://www.scilab.org/download/6.1.0</a>> is<br>
> released today!<br>
> <br>
> <br>
> <br>
> This version includes further improvement atop Scilab 6.0 for better<br>
> stability and increased algorithm performance. It also includes a reworked<br>
> display for more compact and meaningful value printing; web tools for HTTP,<br>
> JSON support; better debug support and various algorithm rewrite/extension.<br>
> <br>
> <br>
> <br>
> This first iteration of the 6.1 branch fixes up to 245 bugs and implements<br>
> missing features from the 6.0.2 version. We would like to give a special thanks<br>
> to Samuel and Stephane who have been very active this year.<br>
> <br>
> <br>
> <br>
> If you find any critical issue or instability that might need a 6.1.x release<br>
> please alert us <<a href="https://bugzilla.scilab.org/" rel="noreferrer" target="_blank">https://bugzilla.scilab.org/</a>> . If you are a toolbox maintainer,<br>
> please rebuild your code, upgrade it when needed and publish it to<br>
> <a href="http://atoms.scilab.org" rel="noreferrer" target="_blank">atoms.scilab.org</a> <<a href="https://atoms.scilab.org/" rel="noreferrer" target="_blank">https://atoms.scilab.org/</a>> .<br>
> <br>
> <br>
> <br>
> For the complete list of changes and bugs fixed, please take a look at<br>
> the CHANGES <<a href="https://help.scilab.org/CHANGES" rel="noreferrer" target="_blank">https://help.scilab.org/CHANGES</a>> file.<br>
> <br>
> <br>
> <br>
> --<br>
> <br>
> Clément on behalf of the Scilab team<br>
> <br>
> _______________________________________________<br>
> dev mailing list<br>
> <a href="mailto:dev@lists.scilab.org" target="_blank">dev@lists.scilab.org</a> <mailto:<a href="mailto:dev@lists.scilab.org" target="_blank">dev@lists.scilab.org</a>><br>
> <a href="http://lists.scilab.org/mailman/listinfo/dev" rel="noreferrer" target="_blank">http://lists.scilab.org/mailman/listinfo/dev</a><br>
> <br>
<br>
_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@lists.scilab.org" target="_blank">dev@lists.scilab.org</a><br>
<a href="http://lists.scilab.org/mailman/listinfo/dev" rel="noreferrer" target="_blank">http://lists.scilab.org/mailman/listinfo/dev</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>