Re: [Scilab-users] plot(x,y,':') & dotted line : is this a bug?

2020-09-14 Thread Antoine Monmayrant


On 15/09/2020 07:32, Samuel Gougeon wrote:

Le 14/09/2020 à 16:14, Antoine Monmayrant a écrit :

Hello all,

For some reason, I don't understand the output of:

    plot(rand(1:10),':')

This should be a 'dotted line', as explained on the page:
    https://help.scilab.org/docs/6.1.0/en_US/LineSpec.html

But I get a line_style==5 which is some kind of 1dash-2dots line.
Looking at what's on page:
https://help.scilab.org/docs/6.1.0/en_US/polyline_properties.html
I think it would make more sense to get line_style==7, 9 or 10, no?

I have the same behaviour with 5.5.2.
Do you think this is worth a bug report?



Please see http://bugzilla.scilab.org/16366
The bug was fixed on last April 16th, for 6.1.1


Thanks a lot Samuel.

Antoine



Samuel



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


Re: [Scilab-users] plot(x,y,':') & dotted line : is this a bug?

2020-09-14 Thread Samuel Gougeon

Le 14/09/2020 à 16:14, Antoine Monmayrant a écrit :

Hello all,

For some reason, I don't understand the output of:

    plot(rand(1:10),':')

This should be a 'dotted line', as explained on the page:
    https://help.scilab.org/docs/6.1.0/en_US/LineSpec.html

But I get a line_style==5 which is some kind of 1dash-2dots line.
Looking at what's on page:
https://help.scilab.org/docs/6.1.0/en_US/polyline_properties.html
I think it would make more sense to get line_style==7, 9 or 10, no?

I have the same behaviour with 5.5.2.
Do you think this is worth a bug report?



Please see http://bugzilla.scilab.org/16366
The bug was fixed on last April 16th, for 6.1.1

Samuel



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


Re: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container

2020-09-14 Thread EnigmaVoidX
It still fails even with the configure flag:

make[1]: Entering directory '/opt/Scilab/scilab/scilab'
/bin/bash ./libtool  --tag=CXX   --mode=link g++ -std=c++17 -DNDEBUG -g1 -O2
-fno-stack-protector -lstdc++ -lgfortran  -Wl,--no-as-needed -o
scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o 
./modules/libscilab.la ./modules/libscilab-cli.la  -lxml2 
-L/usr/local/lib/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc
-L/usr/lib/gcc/aarch64-linux-gnu/9
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu
-L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. -lpthread -ldl -lcurses
-lgfortran -lm ./modules/console/libsciconsole.la ./modules/jvm/libscijvm.la
./modules/commons/libscicommons.la  ./modules/libscilab.la -lopenblas 
-L/usr/lib/gcc/aarch64-linux-gnu/9
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu
-L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. -lpthread -ldl -lcurses
-lgfortran -lm -lpthread -ldl -lcurses  -lm
libtool: link: g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector
-Wl,--no-as-needed -o .libs/scilab-bin
modules/startup/src/cpp/scilab_bin-scilab.o  -lstdc++
-L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64
-L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64/server
-L/usr/lib/aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
-L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu
-L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../..
./modules/.libs/libscilab-cli.so -L/usr/local/lib/valgrind
-lcoregrind-arm64-linux -lvex-arm64-linux -lgcc
./modules/console/.libs/libsciconsole.so ./modules/jvm/.libs/libscijvm.so
./modules/commons/.libs/libscicommons.so ./modules/.libs/libscilab.so
/opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui.so
/opt/Scilab/scilab/scilab/modules/renderer/.libs/libscirenderer.so
/opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics.so
/opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export.so
/opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole.so
/opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding.so
/opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects.so
/opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes.so
/opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data.so
/opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_browser.so
/opt/Scilab/scilab/scilab/modules/types/.libs/libscitypes-java.so
/opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences.so
/opt/Scilab/scilab/scilab/modules/external_objects_java/.libs/libsciexternal_objects_java.so
/opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm.so -ljava -lverify
-ljvm /opt/Scilab/scilab/scilab/modules/helptools/.libs/libscihelptools.so
/opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons.so
/opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci.so -ltk8.6
-ltcl8.6 /opt/Scilab/scilab/scilab/modules/.libs/libscilab-cli.so
/usr/lib/aarch64-linux-gnu/libcurl-gnutls.so
/opt/Scilab/scilab/scilab/modules/functions/.libs/libscifunctions.so
/opt/Scilab/scilab/scilab/modules/call_scilab/.libs/libscicall_scilab.so
/opt/Scilab/scilab/scilab/modules/localization/.libs/libscilocalization.so
/opt/Scilab/scilab/scilab/modules/special_functions/.libs/libscispecial_functions.so
/opt/Scilab/scilab/scilab/modules/completion/.libs/libscicompletion.so
/opt/Scilab/scilab/scilab/modules/history_manager/.libs/libscihistory_manager.so
-lpcreposix -lpcre
/opt/Scilab/scilab/scilab/modules/hdf5/.libs/libscihdf5.so -lhdf5_serial
-lhdf5_serial_hl -lfftw3
/opt/Scilab/scilab/scilab/modules/statistics/.libs/libscistatistics.so
/opt/Scilab/scilab/scilab/modules/ast/.libs/libsciast.so
/opt/Scilab/scilab/scilab/modules/functions_manager/.libs/libscifunctions_manager.so
/opt/Scilab/scilab/scilab/modules/xml/.libs/libscixml.so
/opt/Scilab/scilab/scilab/modules/external_objects/.libs/libsciexternal_objects.so
/opt/Scilab/scilab/scilab/modules/slint/.libs/libscislint.so
/opt/Scilab/scilab/scilab/modules/coverage/.libs/libscicoverage.so -lxml2
/opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui-disable.so
/opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics-disable.so
/opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export-disable.so
/opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole-minimal.so
/opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding-disable.so
/opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm-disable.so
/opt/Scilab/scilab/scilab/modules/xcos/.libs/libscixcos-disable.so
/opt/Scilab/scilab/scilab/modules/graphic_objects/.li

Re: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container

2020-09-14 Thread EnigmaVoidX
I'm trying that, currently in the process of make, however the configure log
still shows valgrind path even with the configure options you have given me,
hopefully that won't cause any issues. 


Clément David-3 wrote
> Hello,
> 
> As a first build, I suggest you to compile without valgrind support as
> this is an optional dependency. This can be done using :
>  $ ./configure VALGRIND_CFLAGS="" VALGRIND_LIBS=""
> 
> Otherwise, your analysis looks good. Either your valgrind installation
> provide an extra library we need to link against, either we don't need to
> link against the coregrind library.
> 
> Thanks,
> 
> Clément DAVID 
> 
>> -Original Message-
>> From: users <

> users-bounces@.scilab

> > On Behalf Of EnigmaVoidX
>> Sent: Sunday, September 13, 2020 11:07 PM
>> To: 

> users@.scilab

>> Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10
>> running inside Termux Proot Container
>> 
>> I have been spending a few days compiling Scilab 6.1.0 git on my Ubuntu
>> 19.10
>> arm64 OS running inside a proot container.
>> 
>> After patching for the newer jogl2 packages and getting a few more extra
>> dependencies I have managed to configure and make up to this point:
>> 
>> ```
>> make[1]: Entering directory '/opt/Scilab/scilab/scilab'
>> /bin/bash ./libtool  --tag=CXX   --mode=link g++ -std=c++17 -DNDEBUG -g1
>> -
>> O2
>> -fno-stack-protector -lstdc++ -lgfortran  -Wl,--no-as-needed -o
>> scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o
>> ./modules/libscilab.la ./modules/libscilab-cli.la  -lxml2
>> -L/usr/lib/aarch64-
>> linux-gnu/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc -
>> L/usr/lib/gcc/aarch64-linux-gnu/9
>> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
>> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib
>> -L/lib/aarch64-linux-gnu -
>> L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib
>> -L/usr/lib/gcc/aarch64-
>> linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm
>> ./modules/console/libsciconsole.la ./modules/jvm/libscijvm.la
>> ./modules/commons/libscicommons.la  ./modules/libscilab.la -lopenblas
>> -L/usr/lib/gcc/aarch64-linux-gnu/9
>> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
>> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib
>> -L/lib/aarch64-linux-gnu -
>> L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib
>> -L/usr/lib/gcc/aarch64-
>> linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm -lpthread
>> -ldl -lcurses
>> -lm
>> libtool: link: g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector
>> -Wl,--
>> no-as-needed -o .libs/scilab-bin
>> modules/startup/src/cpp/scilab_bin-scilab.o
>> -lstdc++
>> -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64
>> -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64/server
>> -L/usr/lib/aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9
>> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
>> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib
>> -L/lib/aarch64-linux-gnu -
>> L/lib/../lib -L/usr/lib/../lib
>> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../..
>> ./modules/.libs/libscilab-cli.so -L/usr/lib/aarch64-linux-gnu/valgrind
>> -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc
>> ./modules/console/.libs/libsciconsole.so ./modules/jvm/.libs/libscijvm.so
>> ./modules/commons/.libs/libscicommons.so ./modules/.libs/libscilab.so
>> /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui.so
>> /opt/Scilab/scilab/scilab/modules/renderer/.libs/libscirenderer.so
>> /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics.so
>> /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export.
>> so
>> /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole.so
>> /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding.s
>> o
>> /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects
>> .so
>> /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes.so
>> /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data.so
>> /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_brows
>> er.so
>> /opt/Scilab/scilab/scilab/modules/types/.libs/libscitypes-java.so
>> /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences.so
>> /opt/Scilab/scilab/scilab/modules/external_objects_java/.libs/libsciexternal
>> _objects_java.so
>> /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm.so -ljava -lverify
>> -ljvm
>> /opt/Scilab/scilab/scilab/modules/helptools/.libs/libscihelptools.so
>> /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons.so
>> /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci.so -ltk8.6
>> -ltcl8.6 /opt/Scilab/scilab/scilab/modules/.libs/libscilab-cli.so
>> /usr/lib/aarch64-linux-gnu/libcurl-gnutls.so
>> /opt/Scilab/scilab/scilab/modules/functions/.libs/libscifunctions.so
>> /opt/Scilab/scilab/scilab/modules/call_scilab/.libs/libscicall_scilab.so
>> /opt/Scilab/scilab/scilab/modules/localization/.libs/libsc

Re: [Scilab-users] plot(x,y,':') & dotted line : is this a bug?

2020-09-14 Thread Heinz Nabielek
Ok: perhaps not perfect dots

scf();plot(1:10,':'); scf();plot(1:100,':');


> On 14.09.2020, at 16:28, Antoine Monmayrant  
> wrote:
> 
>  scf();plot(1:10,':')

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


Re: [Scilab-users] plot(x,y,':') & dotted line : is this a bug?

2020-09-14 Thread Heinz Nabielek
> On 14.09.2020, at 16:14, Antoine Monmayrant  
> wrote:
> 
>  plot(rand(1:10),':')


I get a perfect dotted line.
Heinz

  "Scilab Version: ""6.1.1.0"   
 
  "Operating System: "  "Mac OS X 10.15.6"  
 
  "Java version: "  "1.8.0_51"  
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


Re: [Scilab-users] Hybrid simulation in Scilab/Xcos

2020-09-14 Thread Chin Luh Tan
Hi, 



you might want to use the discrete block "DLR" instead. 



first you could convert the PID in s-domain into z domain using the dscr 
function in the Scilab, and then use the value in DLR block for hybrid 
simulation. make sure the clock u use for the block is same as the sampling 
rate in the dscr function. 



hope this helps.



rgds,
CL


 On Mon, 14 Sep 2020 22:13:05 +0800 Steve  
wrote 


Hello, 
 
I have been facing a problem how to develop a hybrid simulation in the 
Scilab/Xcos. The simulation consists of  a SISO (single input single output) 
system in continuous time domain and a discrete PID controller. The PID 
controller is a CBLOCK containing the code in the C programmin language. 
Interface between the "analog world" and the "discrete world" consists of 
two SAMPLEHOLD blocks. My problem is that I don't know how to achieve a 
state when the CBLOCK is calculated in synchronism with the sample and hold 
process realized in the SAMPLEHOLD blocks. Can anybody give me an advice or 
recommend me some tutorial? Thanks in advance. 
 
 
 
-- 
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
 
___ 
users mailing list 
mailto:users@lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/users___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


Re: [Scilab-users] plot(x,y,':') & dotted line : is this a bug?

2020-09-14 Thread Stefan Du Rietz



On 2020-09-14 16:28, Antoine Monmayrant wrote:


Le 14/09/2020 à 16:23, Heinz Nabielek a écrit :


I get a perfect dotted line.



What?
I tested this under linux (ubuntu 18.04) & Windows10, with both 5.5.2 
and the 6.1 and I don't get a dotted line...


I attached the output of:

     scf();plot(1:10,':')



Antoine



Antoine, I get the same erroneous line as you!

Scilab 6.0.2
Linux, Ubuntu 18.04 LTS

/Stefan

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


Re: [Scilab-users] plot(x,y,':') & dotted line : is this a bug?

2020-09-14 Thread Antoine Monmayrant


Le 14/09/2020 à 16:23, Heinz Nabielek a écrit :


I get a perfect dotted line.



What?
I tested this under linux (ubuntu 18.04) & Windows10, with both 5.5.2 
and the 6.1 and I don't get a dotted line...


I attached the output of:

    scf();plot(1:10,':')



Antoine

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


[Scilab-users] plot(x,y,':') & dotted line : is this a bug?

2020-09-14 Thread Antoine Monmayrant

Hello all,

For some reason, I don't understand the output of:

    plot(rand(1:10),':')

This should be a 'dotted line', as explained on the page:
    https://help.scilab.org/docs/6.1.0/en_US/LineSpec.html

But I get a line_style==5 which is some kind of 1dash-2dots line.
Looking at what's on page:
https://help.scilab.org/docs/6.1.0/en_US/polyline_properties.html
I think it would make more sense to get line_style==7, 9 or 10, no?

I have the same behaviour with 5.5.2.
Do you think this is worth a bug report?

Antoine

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


[Scilab-users] Hybrid simulation in Scilab/Xcos

2020-09-14 Thread Steve
Hello,

I have been facing a problem how to develop a hybrid simulation in the
Scilab/Xcos. The simulation consists of  a SISO (single input single output)
system in continuous time domain and a discrete PID controller. The PID
controller is a CBLOCK containing the code in the C programmin language.
Interface between the "analog world" and the "discrete world" consists of
two SAMPLEHOLD blocks. My problem is that I don't know how to achieve a
state when the CBLOCK is calculated in synchronism with the sample and hold
process realized in the SAMPLEHOLD blocks. Can anybody give me an advice or
recommend me some tutorial? Thanks in advance.



--
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


Re: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container

2020-09-14 Thread Clément David
Hello,

As a first build, I suggest you to compile without valgrind support as this is 
an optional dependency. This can be done using :
 $ ./configure VALGRIND_CFLAGS="" VALGRIND_LIBS=""

Otherwise, your analysis looks good. Either your valgrind installation provide 
an extra library we need to link against, either we don't need to link against 
the coregrind library.

Thanks,

Clément DAVID 

> -Original Message-
> From: users  On Behalf Of EnigmaVoidX
> Sent: Sunday, September 13, 2020 11:07 PM
> To: users@lists.scilab.org
> Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10
> running inside Termux Proot Container
> 
> I have been spending a few days compiling Scilab 6.1.0 git on my Ubuntu
> 19.10
> arm64 OS running inside a proot container.
> 
> After patching for the newer jogl2 packages and getting a few more extra
> dependencies I have managed to configure and make up to this point:
> 
> ```
> make[1]: Entering directory '/opt/Scilab/scilab/scilab'
> /bin/bash ./libtool  --tag=CXX   --mode=link g++ -std=c++17 -DNDEBUG -g1 -
> O2
> -fno-stack-protector -lstdc++ -lgfortran  -Wl,--no-as-needed -o
> scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o
> ./modules/libscilab.la ./modules/libscilab-cli.la  -lxml2 -L/usr/lib/aarch64-
> linux-gnu/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc -
> L/usr/lib/gcc/aarch64-linux-gnu/9
> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -
> L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/aarch64-
> linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm
> ./modules/console/libsciconsole.la ./modules/jvm/libscijvm.la
> ./modules/commons/libscicommons.la  ./modules/libscilab.la -lopenblas
> -L/usr/lib/gcc/aarch64-linux-gnu/9
> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -
> L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/aarch64-
> linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm -lpthread -ldl 
> -lcurses
> -lm
> libtool: link: g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector -Wl,--
> no-as-needed -o .libs/scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o
> -lstdc++
> -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64
> -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64/server
> -L/usr/lib/aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9
> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu
> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -
> L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../..
> ./modules/.libs/libscilab-cli.so -L/usr/lib/aarch64-linux-gnu/valgrind
> -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc
> ./modules/console/.libs/libsciconsole.so ./modules/jvm/.libs/libscijvm.so
> ./modules/commons/.libs/libscicommons.so ./modules/.libs/libscilab.so
> /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui.so
> /opt/Scilab/scilab/scilab/modules/renderer/.libs/libscirenderer.so
> /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics.so
> /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export.
> so
> /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole.so
> /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding.s
> o
> /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects
> .so
> /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes.so
> /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data.so
> /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_brows
> er.so
> /opt/Scilab/scilab/scilab/modules/types/.libs/libscitypes-java.so
> /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences.so
> /opt/Scilab/scilab/scilab/modules/external_objects_java/.libs/libsciexternal
> _objects_java.so
> /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm.so -ljava -lverify -ljvm
> /opt/Scilab/scilab/scilab/modules/helptools/.libs/libscihelptools.so
> /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons.so
> /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci.so -ltk8.6
> -ltcl8.6 /opt/Scilab/scilab/scilab/modules/.libs/libscilab-cli.so
> /usr/lib/aarch64-linux-gnu/libcurl-gnutls.so
> /opt/Scilab/scilab/scilab/modules/functions/.libs/libscifunctions.so
> /opt/Scilab/scilab/scilab/modules/call_scilab/.libs/libscicall_scilab.so
> /opt/Scilab/scilab/scilab/modules/localization/.libs/libscilocalization.so
> /opt/Scilab/scilab/scilab/modules/special_functions/.libs/libscispecial_functi
> ons.so
> /opt/Scilab/scilab/scilab/modules/completion/.libs/libscicompletion.so
> /opt/Scilab/scilab/scilab/modules/history_manager/.libs/libscihistory_manag
> er.so
> -lpcreposix -lpcre
> /opt/Scilab/scilab/scilab/modules/hdf5/.libs/libscihdf5.so -lhdf5_serial -
> lhdf5_