lto:dev-boun...@lists.scilab.org>>
On Behalf Of Sylvain Corlay
Sent: Friday, February 17, 2023 4:04 PM
To: List dedicated to the development of Scilab
mailto:dev@lists.scilab.org>>
Subject: Re: [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit
support
Hi Vincent,
The problem wi
break compatibility between versions
(whatever the version type is) but if we have to do it, we will do it in major
versions (planned for October) and try to warn users asap.
Best regards,
Vincent
From: dev mailto:dev-boun...@lists.scilab.org>>
On Behalf Of Sylvain Corlay
Sent: Thursday,
Hi Vincent,
Thank you for the updates and the new releases.
I think that one potential issue with such a versioning scheme is the
communication of backward compatibility of APIs and ABIs. A commonly accepted
schemas is to have Major.major.patch schema where,
1. Patch version updates are binary
Hey,
Any news on supporting another version of gcc than the latest version?
Best,
On Mon, Apr 13, 2020, 11:55 Sylvain Corlay wrote:
> Hello All,
>
> I am following up on this.
>
> Is there any hope for a patch Scilab release that would support gcc < 8 ?
> This regressio
Mar 5, 2020 at 11:56 AM Sylvain Corlay
wrote:
> Hi Clément,
>
> Indeed, this is what I ended up doing - and there are a couple of
> instances of the same error in various places.
>
> This appears to be a legitimate error C++ even though this passes with GCC
> 8.
>
> O
of Ubuntu, or Debian Sid already have GCC8 available. GCC6 and GCC7
are recent compilers and people target older distributions in their builds.
Best,
Sylvain Corlay
On Thu, Mar 5, 2020 at 11:41 AM Clément David
wrote:
> Hello Sylvain,
>
> I took a look at the trace, it looks like g++ 7 is c
Hello,
Is there any update on the support of GCC 7 for Scilab 6.1?
This is a major blocker for us to package it for the conda ecosystem.
Best,
On Thu, Feb 27, 2020 at 4:12 PM Sylvain Corlay
wrote:
> Patching the source to use resolves that
> particular issue with C++17 in GCC7.
>
at 2:28 PM Sylvain Corlay
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 recip
ttps://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 On Behalf Of Sylvain Corlay
> >
recent
version of OpenJDK?
Best,
Sylvain Corlay
On Tue, Feb 25, 2020 at 2:10 PM Clément David
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 im
Hello Everyone,
I am following up on this.
Would you guys be open to a PR making that change?
On Fri, Mar 29, 2019 at 6:56 PM Stéphane Mottelet
wrote:
> Le 29/03/2019 à 18:28, Sylvain Corlay a écrit :
>
> Hello, world!
>
> The Jupyter kernel protocol expect stdout and stder
Hello Everyone,
I figured it may be useful to make a summary of the issues that I
encountered as I made a conda package for Scilab. The information already
exists in a couple of other threads but is scattered accross many messages.
Hopefully, the core team will be able to resolve some of these for
Yes, naturally! This is what I did.
Sylvain
On Fri, Apr 5, 2019 at 8:08 PM Stéphane Mottelet
wrote:
> I mean enable-code-coverage=no
>
> Le 5 avr. 2019 à 19:47, Sylvain Corlay a
> écrit :
>
> Thanks! this configure option is recognized but launching scilab fails
> over th
Thanks! this configure option is recognized but launching scilab fails over
the same missing symbol error.
S.
On Fri, Apr 5, 2019 at 6:17 PM Stéphane Mottelet
wrote:
> sorry its
>
> --enable-code-coverage
>
> (./configure --help)
>
> S.
> Le 05/04/2019 à 18:13, Sylvain
Hi, sorry for the late reply.
It does not fix the issue. The option appears to not be recognized:
configure: WARNING: unrecognized options: --enable-coverage
Best,
Sylvain
On Fri, Apr 5, 2019 at 2:22 PM Stéphane Mottelet
wrote:
> Le 03/04/2019 à 15:40, Sylvain Corlay a écrit :
>
&g
Thanks Stéphane,
Regarding your earlier question, the log for the build is available here:
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=25973&view=logs&jobId=ce7cbaa7-582c-5570-40f4-267b3d85fc9f
I will post a separate message on the list summarizing all the issues th
main in scilab_bin-scilab.o
ld: symbol(s) not found for architecture x86_64
clang-4.0: error: linker command failed with exit code 1 (use -v to see
invocation)
Symbol *_initMacOSXEnv* is not found.
Sincerely,
Sylvain
On Fri, Mar 29, 2019 at 6:12 PM Sylvain Corlay
wrote:
> Thanks I am looking f
Hello, world!
The Jupyter kernel protocol expect stdout and stderr streams to be both
redirected to the frontend, however, it makes a distinction between error
and output messages in the `stream` message type:
content = {
# The name of the stream is one of 'stdout', 'stderr'
'name' : str,
Thanks I am looking forward to it.
On Fri, Mar 29, 2019 at 6:02 PM Stéphane Mottelet
wrote:
>
> Le 29/03/2019 à 17:58, Sylvain Corlay a écrit :
>
> Yeah, or update scilab so as to make it work with openjdk 11.
>
> I think that it is planned for the next release (6.1), m
Yeah, or update scilab so as to make it work with openjdk 11.
On Fri, Mar 29, 2019 at 5:58 PM Stéphane Mottelet
wrote:
>
> Le 29/03/2019 à 17:54, Sylvain Corlay a écrit :
>
> Thanks for the heads up.
>
> I set `--without-matio` because `matio` is not yet packaged for
> c
d be some object files as complimentary arguments in
>
> libtool: link: $BUILD_PREFIX/bin/x86_64-apple-darwin13.4.0-ar cru
> .libs/libscimatio-algo.a
>
> that's why 'ar' complains. I think that the Makefile is already broken
> after the ./configure, but I cannot tell yo
m/conda-forge/scilab-feedstock/pull/1/files#diff-e178b687b10a71a3348107ae3154e44c
Best,
On Fri, Mar 29, 2019 at 4:44 PM Stéphane Mottelet
wrote:
> Sorry, I cannot figure out in the log which version of Scilab you are
> building
>
> Le 29/03/2019 à 16:36, Sylvain Corlay a écrit :
Yes, that error. You got it.
On Fri, Mar 29, 2019 at 4:33 PM Stéphane Mottelet
wrote:
> Le 29/03/2019 à 16:25, SylvainCorlay a écrit :
>
> I meant the build log from the the CI in the pull request.
>
> Here is a direct link:
> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/dev.
Hi Antoine,
Thank you for your quick response. This is exactly what I was looking for!
Cheers,
On Sat, Mar 2, 2019 at 9:05 AM Antoine ELIAS <
antoine.el...@scilab-enterprises.com> wrote:
> Hello Sylvain,
>
> You can get Scilab outputs by setting your own output function.
>
> void scilab_print(c
24 matches
Mail list logo
