From bvl at btconnect.com Mon Nov 1 14:23:16 2010 From: bvl at btconnect.com (bv) Date: Mon, 1 Nov 2010 13:23:16 +0000 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <201010312235.02619.bvl@btconnect.com> References: <201010290328.57390.bvl@btconnect.com> <201010312210.39249.bvl@btconnect.com> <201010312235.02619.bvl@btconnect.com> Message-ID: <201011011323.17023.bvl@btconnect.com> On Sunday 31 October 2010 22:35:02 bv wrote: > > I just found this link for a report of the said problem on suse-11.2 > http://scigroups.net/comp.soft-sys.math.scilab/compiling-scilab-5.2.2-on- > opensuse-11.2 > > could anyone advise if there is a fix upstream in scilab for this? ############## this error:- configure: error: libamd: Library missing (Cannot find symbol amd_info). Check if libamd (sparse matrix minimum degree ordering) is installed and if the version is correct Seems to plague versions of scilab I have tried with umfpack. It occurs with both older and new versions of imfpack+co. And the checks I have made show both static and shared libs of libamd are archived with amd_i_info.o as shown in the build log below:- ----------------------------------------- ################################################ 1-- compiling AMD-2.2.1 ################################################## gfortran -fomit-frame-pointer -mfpmath=sse -msse3 -O2 -falign-loops=32 -fPIC - m64 -c ../Source/amd.f -o amd.o gfortran -fomit-frame-pointer -mfpmath=sse -msse3 -O2 -falign-loops=32 -fPIC - m64 -c ../Source/amdbar.f -o amdbar.o ar cr libamdf77.a amd.o amdbar.o ranlib libamdf77.a ( cd Lib ; make ) make[1]: Entering directory `$SOURCES/buildNUMERICS/AMD-2.2.1/Lib' gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -c ../Source/amd_global.c -o amd_global.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_aat.c -o amd_i_aat.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_1.c -o amd_i_1.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_2.c -o amd_i_2.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_dump.c -o amd_i_dump.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_postorder.c -o amd_i_postorder.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_post_tree.c -o amd_i_post_tree.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_defaults.c -o amd_i_defaults.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_order.c -o amd_i_order.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_control.c -o amd_i_control.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_info.c -o amd_i_info.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_valid.c -o amd_i_valid.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c ../Source/amd_preprocess.c -o amd_i_preprocess.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_aat.c -o amd_l_aat.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_1.c -o amd_l_1.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_2.c -o amd_l_2.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_dump.c -o amd_l_dump.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_postorder.c -o amd_l_postorder.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_post_tree.c -o amd_l_post_tree.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_defaults.c -o amd_l_defaults.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_order.c -o amd_l_order.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_control.c -o amd_l_control.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_info.c -o amd_l_info.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_valid.c -o amd_l_valid.o gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c ../Source/amd_preprocess.c -o amd_l_preprocess.o ar cr libamd.a amd_global.o amd_i_aat.o amd_i_1.o amd_i_2.o amd_i_dump.o amd_i_postorder.o amd_i_post_tree.o amd_i_defaults.o amd_i_order.o amd_i_control.o amd_i_info.o amd_i_valid.o amd_i_preprocess.o amd_l_aat.o amd_l_1.o amd_l_2.o amd_l_dump.o amd_l_postorder.o amd_l_post_tree.o amd_l_defaults.o amd_l_order.o amd_l_control.o amd_l_info.o amd_l_valid.o amd_l_preprocess.o ranlib libamd.a gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -c ../Source/amd_global.c -o amd_global.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_aat.c -o amd_i_aat.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_1.c -o amd_i_1.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_2.c -o amd_i_2.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_dump.c -o amd_i_dump.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_postorder.c -o amd_i_postorder.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_post_tree.c -o amd_i_post_tree.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_defaults.c -o amd_i_defaults.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_order.c -o amd_i_order.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_control.c -o amd_i_control.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_info.c -o amd_i_info.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_valid.c -o amd_i_valid.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c ../Source/amd_preprocess.c -o amd_i_preprocess.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_aat.c -o amd_l_aat.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_1.c -o amd_l_1.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_2.c -o amd_l_2.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_dump.c -o amd_l_dump.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_postorder.c -o amd_l_postorder.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_post_tree.c -o amd_l_post_tree.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_defaults.c -o amd_l_defaults.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_order.c -o amd_l_order.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_control.c -o amd_l_control.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_info.c -o amd_l_info.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_valid.c -o amd_l_valid.oo gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - c ../Source/amd_preprocess.c -o amd_l_preprocess.oo gcc -shared amd_global.oo amd_i_aat.oo amd_i_1.oo amd_i_2.oo amd_i_dump.oo amd_i_postorder.oo amd_i_post_tree.oo amd_i_defaults.oo amd_i_order.oo amd_i_control.oo amd_i_info.oo amd_i_valid.oo amd_i_preprocess.oo amd_l_aat.oo amd_l_1.oo amd_l_2.oo amd_l_dump.oo amd_l_postorder.oo amd_l_post_tree.oo amd_l_defaults.oo amd_l_order.oo amd_l_control.oo amd_l_info.oo amd_l_valid.oo amd_l_preprocess.oo -lm -Wl,-soname -Wl,libamd.so.2.2.1 -o libamd.so.2.2.1 ln -s libamd.so.2.2.1 libamd.so make[1]: Leaving directory `$SOURCES/buildNUMERICS/AMD-2.2.1/Lib' ( cd Demo ; make ) ------------------------------------------- ####### I have also now tried scilab-5.3.0-beta4. running configue ends like so:- ------------------- checking for umfpack.h... yes checking for amd_info in -lamd... no configure: error: libamd: Library missing (Cannot find symbol amd_info). Check if libamd (sparse matrix minimum degree ordering) is installed and if the version is correct ----------------- I am using a machine with pure 64-bit (x86_64) libraries. I am wondering if scilab (or at least parts of it) currently has problems building on pure 64- bit-libs-machines. Suggestions would be appreciated. sincerely bv From calixte at contrib.scilab.org Mon Nov 1 13:42:42 2010 From: calixte at contrib.scilab.org (Calixte Denizet) Date: Mon, 01 Nov 2010 13:42:42 +0100 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <201011011323.17023.bvl@btconnect.com> References: <201010290328.57390.bvl@btconnect.com> <201010312210.39249.bvl@btconnect.com> <201010312235.02619.bvl@btconnect.com> <201011011323.17023.bvl@btconnect.com> Message-ID: <1288615362.2567.8.camel@Calixte-Dell> Hello, what's the output of : # ldconfig -v | grep libamd and the output of $ readelf -a /path/to/lib/libamd.so | grep amd_info ? Calixte Le lundi 01 novembre 2010 ? 13:23 +0000, bv a ?crit : > On Sunday 31 October 2010 22:35:02 bv wrote: > > > > > I just found this link for a report of the said problem on suse-11.2 > > http://scigroups.net/comp.soft-sys.math.scilab/compiling-scilab-5.2.2-on- > > opensuse-11.2 > > > > could anyone advise if there is a fix upstream in scilab for this? > > ############## this error:- > configure: error: libamd: Library missing (Cannot find symbol amd_info). Check > if libamd (sparse matrix minimum degree ordering) is installed and if the > version is correct > > Seems to plague versions of scilab I have tried with umfpack. It occurs with > both older and new versions of imfpack+co. And the checks I have made show > both static and shared libs of libamd are archived with amd_i_info.o as > shown in the build log below:- > ----------------------------------------- > > ################################################ > 1-- compiling AMD-2.2.1 > ################################################## > > gfortran -fomit-frame-pointer -mfpmath=sse -msse3 -O2 -falign-loops=32 -fPIC - > m64 -c ../Source/amd.f -o amd.o > gfortran -fomit-frame-pointer -mfpmath=sse -msse3 -O2 -falign-loops=32 -fPIC - > m64 -c ../Source/amdbar.f -o amdbar.o > ar cr libamdf77.a amd.o amdbar.o > ranlib libamdf77.a > ( cd Lib ; make ) > make[1]: Entering directory `$SOURCES/buildNUMERICS/AMD-2.2.1/Lib' > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -c > ../Source/amd_global.c -o amd_global.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_aat.c -o amd_i_aat.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_1.c -o amd_i_1.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_2.c -o amd_i_2.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_dump.c -o amd_i_dump.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_postorder.c -o amd_i_postorder.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_post_tree.c -o amd_i_post_tree.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_defaults.c -o amd_i_defaults.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_order.c -o amd_i_order.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_control.c -o amd_i_control.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_info.c -o amd_i_info.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_valid.c -o amd_i_valid.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDINT -c > ../Source/amd_preprocess.c -o amd_i_preprocess.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_aat.c -o amd_l_aat.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_1.c -o amd_l_1.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_2.c -o amd_l_2.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_dump.c -o amd_l_dump.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_postorder.c -o amd_l_postorder.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_post_tree.c -o amd_l_post_tree.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_defaults.c -o amd_l_defaults.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_order.c -o amd_l_order.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_control.c -o amd_l_control.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_info.c -o amd_l_info.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_valid.c -o amd_l_valid.o > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -DDLONG -c > ../Source/amd_preprocess.c -o amd_l_preprocess.o > ar cr libamd.a amd_global.o amd_i_aat.o amd_i_1.o amd_i_2.o amd_i_dump.o > amd_i_postorder.o amd_i_post_tree.o amd_i_defaults.o amd_i_order.o > amd_i_control.o amd_i_info.o amd_i_valid.o amd_i_preprocess.o amd_l_aat.o > amd_l_1.o amd_l_2.o amd_l_dump.o amd_l_postorder.o amd_l_post_tree.o > amd_l_defaults.o amd_l_order.o amd_l_control.o amd_l_info.o amd_l_valid.o > amd_l_preprocess.o > ranlib libamd.a > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -c > ../Source/amd_global.c -o amd_global.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_aat.c -o amd_i_aat.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_1.c -o amd_i_1.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_2.c -o amd_i_2.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_dump.c -o amd_i_dump.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_postorder.c -o amd_i_postorder.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_post_tree.c -o amd_i_post_tree.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_defaults.c -o amd_i_defaults.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_order.c -o amd_i_order.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_control.c -o amd_i_control.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_info.c -o amd_i_info.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_valid.c -o amd_i_valid.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDINT -c > ../Source/amd_preprocess.c -o amd_i_preprocess.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_aat.c -o amd_l_aat.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_1.c -o amd_l_1.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_2.c -o amd_l_2.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_dump.c -o amd_l_dump.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_postorder.c -o amd_l_postorder.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_post_tree.c -o amd_l_post_tree.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_defaults.c -o amd_l_defaults.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_order.c -o amd_l_order.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_control.c -o amd_l_control.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_info.c -o amd_l_info.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_valid.c -o amd_l_valid.oo > gcc -O3 -fexceptions -m64 -fPIC -I../Include -I../../UFconfig -fPIC -DDLONG - > c ../Source/amd_preprocess.c -o amd_l_preprocess.oo > gcc -shared amd_global.oo amd_i_aat.oo amd_i_1.oo amd_i_2.oo amd_i_dump.oo > amd_i_postorder.oo amd_i_post_tree.oo amd_i_defaults.oo amd_i_order.oo > amd_i_control.oo amd_i_info.oo amd_i_valid.oo amd_i_preprocess.oo amd_l_aat.oo > amd_l_1.oo amd_l_2.oo amd_l_dump.oo amd_l_postorder.oo amd_l_post_tree.oo > amd_l_defaults.oo amd_l_order.oo amd_l_control.oo amd_l_info.oo amd_l_valid.oo > amd_l_preprocess.oo -lm -Wl,-soname -Wl,libamd.so.2.2.1 -o libamd.so.2.2.1 > ln -s libamd.so.2.2.1 libamd.so > make[1]: Leaving directory `$SOURCES/buildNUMERICS/AMD-2.2.1/Lib' > ( cd Demo ; make ) > > ------------------------------------------- > > ####### I have also now tried scilab-5.3.0-beta4. running configue ends like > so:- > ------------------- > checking for umfpack.h... yes > checking for amd_info in -lamd... no > configure: error: libamd: Library missing (Cannot find symbol amd_info). Check > if libamd (sparse matrix minimum degree ordering) is installed and if the > version is correct > ----------------- > > I am using a machine with pure 64-bit (x86_64) libraries. I am wondering if > scilab (or at least parts of it) currently has problems building on pure 64- > bit-libs-machines. Suggestions would be appreciated. > > sincerely > bv From bvl at btconnect.com Mon Nov 1 16:23:12 2010 From: bvl at btconnect.com (bv) Date: Mon, 1 Nov 2010 15:23:12 +0000 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <1288615362.2567.8.camel@Calixte-Dell> References: <201010290328.57390.bvl@btconnect.com> <201011011323.17023.bvl@btconnect.com> <1288615362.2567.8.camel@Calixte-Dell> Message-ID: <201011011523.12985.bvl@btconnect.com> On Monday 01 November 2010 12:42:42 Calixte Denizet wrote: > Hello, > > what's the output of : > # ldconfig -v | grep libamd > > and the output of > $ readelf -a /path/to/lib/libamd.so | grep amd_info > root [ ~ ]# ldconfig -v | grep libamd libamd.so.2.2.1 -> libamd.so.2.2.1 root [ ~ ]# root [ ~ ]# readelf -a /usr/local/numerics/lib/libamd.so | grep amd_info 23: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info 48: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c 60: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c 88: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info root [ ~ ]# From Cercueil.Paul at addi-data.com Tue Nov 2 15:57:43 2010 From: Cercueil.Paul at addi-data.com (Cercueil.Paul) Date: Tue, 2 Nov 2010 14:57:43 +0000 Subject: XCOS: add custom menus Message-ID: <7EE4421365BD634B886BF50FF73F2EEA05B587@Exchange02.addi-data.intra> Hello, I am currently porting a plugin made for Scicos to XCOS. Unfortunately, it seems that the interface changed a lot between these two. I would like to add menu entries on the XCOS main window. I found some macros like scicos_menubar() that seem to do it, unfortunately I am unable to find a way to use them. Any help would be very welcome. Best regards, Paul Cercueil ADDI-DATA GmbH Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Cercueil.Paul at addi-data.com Wed Nov 3 08:29:00 2010 From: Cercueil.Paul at addi-data.com (Cercueil.Paul) Date: Wed, 3 Nov 2010 07:29:00 +0000 Subject: XCOS: custom menu entries Message-ID: <7EE4421365BD634B886BF50FF73F2EEA05B5D4@Exchange02.addi-data.intra> Hello, I am currently porting a plugin made for Scicos to XCOS. Unfortunately, it seems that the interface changed a lot between these two. I would like to add menu entries on the XCOS main window, from a script file loaded when Scilab starts. I found some macros like scicos_menubar() that seem to do it, unfortunately it seems like it belongs to the old Scilab module, and does not work anymore. Any help would be very welcome. Best regards, Paul Cercueil ADDI-DATA GmbH Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 From sylvestre.ledru at scilab.org Thu Nov 4 05:52:33 2010 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 04 Nov 2010 05:52:33 +0100 Subject: [Scilab-Dev] XCOS: custom menu entries In-Reply-To: <7EE4421365BD634B886BF50FF73F2EEA05B5D4@Exchange02.addi-data.intra> References: <7EE4421365BD634B886BF50FF73F2EEA05B5D4@Exchange02.addi-data.intra> Message-ID: <1288846353.5389.329.camel@zlarin> Hello Paul, Looks like you just fall into a Mac OS X bug. I reported this here: http://bugzilla.scilab.org/show_bug.cgi?id=4074 If I understand correctly your problem, you have to go into a dedicated menu for your module. Sylvestre Le mercredi 03 novembre 2010 ? 07:29 +0000, Cercueil.Paul a ?crit : > Hello, > > I am currently porting a plugin made for Scicos to XCOS. > Unfortunately, it seems that the interface changed a lot between these two. > > I would like to add menu entries on the XCOS main window, from a script file loaded when Scilab starts. > I found some macros like scicos_menubar() that seem to do it, unfortunately it seems like it belongs to the old Scilab module, and does not work anymore. > > Any help would be very welcome. > > Best regards, > > Paul Cercueil > ADDI-DATA GmbH > > > > Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: > - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN > - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS > > > Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! > > > ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann > UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 > -- ------------------------- Sylvestre Ledru ------------------------- The Scilab Consortium Digiteo Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex France From Cercueil.Paul at addi-data.com Thu Nov 4 08:30:08 2010 From: Cercueil.Paul at addi-data.com (Cercueil.Paul) Date: Thu, 4 Nov 2010 07:30:08 +0000 Subject: AW: [Scilab-Dev] XCOS: custom menu entries In-Reply-To: <1288846353.5389.329.camel@zlarin> References: <7EE4421365BD634B886BF50FF73F2EEA05B5D4@Exchange02.addi-data.intra> <1288846353.5389.329.camel@zlarin> Message-ID: <7EE4421365BD634B886BF50FF73F2EEA08643B@Exchange02.addi-data.intra> Hello Sylvestre, I'm sorry, I don't use Mac OSX, and all the menus of XCOS work just as they should. However, I am unable to find a way to create a new menu on the menu bar, as it was possible on the old Scicos with simple scripts. Later I found that the menus are hardcoded inside the Java code... I will modify the source so that it fits our needs, but I'm simply surprised that there's no practical way to control XCOS from Scilab. Best Regards, Paul Cercueil ADDI-DATA GmbH -----Urspr?ngliche Nachricht----- Von: Sylvestre Ledru [mailto:sylvestre.ledru at scilab.org] Gesendet: Donnerstag, 4. November 2010 05:53 An: dev at lists.scilab.org Betreff: Re: [Scilab-Dev] XCOS: custom menu entries Hello Paul, Looks like you just fall into a Mac OS X bug. I reported this here: http://bugzilla.scilab.org/show_bug.cgi?id=4074 If I understand correctly your problem, you have to go into a dedicated menu for your module. Sylvestre Le mercredi 03 novembre 2010 ? 07:29 +0000, Cercueil.Paul a ?crit : > Hello, > > I am currently porting a plugin made for Scicos to XCOS. > Unfortunately, it seems that the interface changed a lot between these two. > > I would like to add menu entries on the XCOS main window, from a script file loaded when Scilab starts. > I found some macros like scicos_menubar() that seem to do it, unfortunately it seems like it belongs to the old Scilab module, and does not work anymore. > > Any help would be very welcome. > > Best regards, > > Paul Cercueil > ADDI-DATA GmbH > > > > Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: > - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN > - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS > > > Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! > > > ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann > UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 > -- ------------------------- Sylvestre Ledru ------------------------- The Scilab Consortium Digiteo Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex France Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 From clement.david at scilab.org Thu Nov 4 09:18:57 2010 From: clement.david at scilab.org (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Thu, 04 Nov 2010 09:18:57 +0100 Subject: AW: [Scilab-Dev] XCOS: custom menu entries In-Reply-To: <7EE4421365BD634B886BF50FF73F2EEA08643B@Exchange02.addi-data.intra> References: <7EE4421365BD634B886BF50FF73F2EEA05B5D4@Exchange02.addi-data.intra> <1288846353.5389.329.camel@zlarin> <7EE4421365BD634B886BF50FF73F2EEA08643B@Exchange02.addi-data.intra> Message-ID: <1288858737.2441.3.camel@pinarellu.inria.fr> Hello, Paul you are right, Xcos GUI is a full java implementation. Currently the only way to for a user to customize a diagram is to put a custom block with a Scilab gui (uicontrols) on the 'set' action. Can you describe your specific use-case please ? It will help us determine the need of such an heavy customize requirement. Regards, Cl?ment Le jeudi 04 novembre 2010 ? 07:30 +0000, Cercueil.Paul a ?crit : > Hello Sylvestre, > > I'm sorry, I don't use Mac OSX, and all the menus of XCOS work just as they should. However, I am unable to find a way to create a new menu on the menu bar, as it was possible on the old Scicos with simple scripts. > > Later I found that the menus are hardcoded inside the Java code... > I will modify the source so that it fits our needs, but I'm simply surprised that there's no practical way to control XCOS from Scilab. > > Best Regards, > > Paul Cercueil > ADDI-DATA GmbH > > -----Urspr?ngliche Nachricht----- > Von: Sylvestre Ledru [mailto:sylvestre.ledru at scilab.org] > Gesendet: Donnerstag, 4. November 2010 05:53 > An: dev at lists.scilab.org > Betreff: Re: [Scilab-Dev] XCOS: custom menu entries > > Hello Paul, > > Looks like you just fall into a Mac OS X bug. I reported this here: > http://bugzilla.scilab.org/show_bug.cgi?id=4074 > > If I understand correctly your problem, you have to go into a dedicated > menu for your module. > > Sylvestre > > > Le mercredi 03 novembre 2010 ? 07:29 +0000, Cercueil.Paul a ?crit : > > Hello, > > > > I am currently porting a plugin made for Scicos to XCOS. > > Unfortunately, it seems that the interface changed a lot between these two. > > > > I would like to add menu entries on the XCOS main window, from a script file loaded when Scilab starts. > > I found some macros like scicos_menubar() that seem to do it, unfortunately it seems like it belongs to the old Scilab module, and does not work anymore. > > > > Any help would be very welcome. > > > > Best regards, > > > > Paul Cercueil > > ADDI-DATA GmbH > > > > > > > > Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: > > - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN > > - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS > > > > > > Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! > > > > > > ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann > > UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 > > > -- Cl?ment David From Cercueil.Paul at addi-data.com Thu Nov 4 09:45:56 2010 From: Cercueil.Paul at addi-data.com (Cercueil.Paul) Date: Thu, 4 Nov 2010 08:45:56 +0000 Subject: AW: [Scilab-Dev] XCOS: custom menu entries In-Reply-To: <1288858737.2441.3.camel@pinarellu.inria.fr> References: <7EE4421365BD634B886BF50FF73F2EEA05B5D4@Exchange02.addi-data.intra> <1288846353.5389.329.camel@zlarin> <7EE4421365BD634B886BF50FF73F2EEA08643B@Exchange02.addi-data.intra>, <1288858737.2441.3.camel@pinarellu.inria.fr> Message-ID: <7EE4421365BD634B886BF50FF73F2EEA088C10@Exchange02.addi-data.intra> Hello, The final goal is to port the Scicos plugin of Gene-Auto to XCOS. Gene-Auto is an alternative code generator, that produces C code more suitable for embedded hardware. The old Scicos plugin provided a "GeneAuto" entry on the "Tools" menu of Scicos, which was starting the code generation when activated. I somewhat found a workaround for this; I redefined the xcosCodeGeneration Scilab function, so that Gene-Auto will be called instead of Scilab's code generator when the user click on "Code generation". I would nonetheless highly prefer to have a separate menu, so that I don't have to mask existing features to implement mines. Regards, Paul Cercueil ADDI-DATA GmbH ________________________________________ De : Cl?ment David [clement.david at scilab.org] Date d'envoi : jeudi 4 novembre 2010 9:18 ? : dev at lists.scilab.org Objet : Re: AW: [Scilab-Dev] XCOS: custom menu entries Hello, Paul you are right, Xcos GUI is a full java implementation. Currently the only way to for a user to customize a diagram is to put a custom block with a Scilab gui (uicontrols) on the 'set' action. Can you describe your specific use-case please ? It will help us determine the need of such an heavy customize requirement. Regards, Cl?ment Le jeudi 04 novembre 2010 ? 07:30 +0000, Cercueil.Paul a ?crit : > Hello Sylvestre, > > I'm sorry, I don't use Mac OSX, and all the menus of XCOS work just as they should. However, I am unable to find a way to create a new menu on the menu bar, as it was possible on the old Scicos with simple scripts. > > Later I found that the menus are hardcoded inside the Java code... > I will modify the source so that it fits our needs, but I'm simply surprised that there's no practical way to control XCOS from Scilab. > > Best Regards, > > Paul Cercueil > ADDI-DATA GmbH > > -----Urspr?ngliche Nachricht----- > Von: Sylvestre Ledru [mailto:sylvestre.ledru at scilab.org] > Gesendet: Donnerstag, 4. November 2010 05:53 > An: dev at lists.scilab.org > Betreff: Re: [Scilab-Dev] XCOS: custom menu entries > > Hello Paul, > > Looks like you just fall into a Mac OS X bug. I reported this here: > http://bugzilla.scilab.org/show_bug.cgi?id=4074 > > If I understand correctly your problem, you have to go into a dedicated > menu for your module. > > Sylvestre > > > Le mercredi 03 novembre 2010 ? 07:29 +0000, Cercueil.Paul a ?crit : > > Hello, > > > > I am currently porting a plugin made for Scicos to XCOS. > > Unfortunately, it seems that the interface changed a lot between these two. > > > > I would like to add menu entries on the XCOS main window, from a script file loaded when Scilab starts. > > I found some macros like scicos_menubar() that seem to do it, unfortunately it seems like it belongs to the old Scilab module, and does not work anymore. > > > > Any help would be very welcome. > > > > Best regards, > > > > Paul Cercueil > > ADDI-DATA GmbH > > > > > > > > Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: > > - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN > > - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS > > > > > > Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! > > > > > > ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann > > UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 > > > -- Cl?ment David Produktneuheiten! Sehen Sie auf der SPS/IPC/Drives 2010 in N?rnberg: - Echtzeit-Ethernet Systeme x-ARTS zum Messen, Steuern, Regeln ?ber Echtzeit-Protokolle wie EtherCAT, ProfiNet oder VARAN - Mit MODBUS-Bibliothek: einfache Steuerung der Ethernet-Systeme MSX-E ?ber SPS Besuchen Sie uns vom 23. bis 25. November 2010: Halle 7, Stand 7.123. Wir freuen uns auf Sie! ADDI-DATA GmbH - Airport Boulevard B210 - 77836 Rheinm?nster (Germany) Amtsgericht Mannheim HRB210433 Gesch?ftsf?hrer Ren? Ohlmann UST-ID-Nr.: DE 143754253 WEEE-Reg.-Nr. DE 65862200 From bvl at btconnect.com Thu Nov 4 16:10:38 2010 From: bvl at btconnect.com (bv) Date: Thu, 4 Nov 2010 15:10:38 +0000 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <201011011523.12985.bvl@btconnect.com> References: <201010290328.57390.bvl@btconnect.com> <1288615362.2567.8.camel@Calixte-Dell> <201011011523.12985.bvl@btconnect.com> Message-ID: <201011041510.38633.bvl@btconnect.com> On Monday 01 November 2010 15:23:12 bv wrote: > On Monday 01 November 2010 12:42:42 Calixte Denizet wrote: > > Hello, > > > > what's the output of : > > # ldconfig -v | grep libamd > > > > and the output of > > $ readelf -a /path/to/lib/libamd.so | grep amd_info > > root [ ~ ]# ldconfig -v | grep libamd > libamd.so.2.2.1 -> libamd.so.2.2.1 > root [ ~ ]# > > > root [ ~ ]# readelf -a /usr/local/numerics/lib/libamd.so | grep amd_info > 23: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > 48: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > 60: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > 88: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > root [ ~ ]# I supplied the above answers on Monday and I would be grateful to know if there is a problem with them or otherwise. sincerely bv From calixte at contrib.scilab.org Sat Nov 6 00:13:51 2010 From: calixte at contrib.scilab.org (Calixte Denizet) Date: Sat, 06 Nov 2010 00:13:51 +0100 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <201011041510.38633.bvl@btconnect.com> References: <201010290328.57390.bvl@btconnect.com> <1288615362.2567.8.camel@Calixte-Dell> <201011011523.12985.bvl@btconnect.com> <201011041510.38633.bvl@btconnect.com> Message-ID: <1288998831.2639.204.camel@Calixte-Dell> Le jeudi 04 novembre 2010 ? 15:10 +0000, bv a ?crit : > On Monday 01 November 2010 15:23:12 bv wrote: > > On Monday 01 November 2010 12:42:42 Calixte Denizet wrote: > > > Hello, > > > > > > what's the output of : > > > # ldconfig -v | grep libamd > > > > > > and the output of > > > $ readelf -a /path/to/lib/libamd.so | grep amd_info > > > > root [ ~ ]# ldconfig -v | grep libamd > > libamd.so.2.2.1 -> libamd.so.2.2.1 > > root [ ~ ]# > > > > > > root [ ~ ]# readelf -a /usr/local/numerics/lib/libamd.so | grep amd_info > > 23: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > 48: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > 60: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > 88: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > root [ ~ ]# Hello, Unfortunatelly, that doesn't help me to have an idea :( An other idea: in the configure file, search for string 'return amd_info ()' and replace it by 'return amd_info (0)', save and ./configure. Best regards Calixte > > > I supplied the above answers on Monday and I would be grateful to know if > there is a problem with them or otherwise. > > sincerely > bv From sylvestre.ledru at scilab.org Thu Nov 4 15:40:43 2010 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 04 Nov 2010 15:40:43 +0100 Subject: [Scilab-Dev] java compile errors when building metanet In-Reply-To: <1288382103.23232.67.camel@Calixte-Dell> References: <1288382103.23232.67.camel@Calixte-Dell> Message-ID: <1288881643.5389.654.camel@zlarin> Le vendredi 29 octobre 2010 ? 21:55 +0200, Calixte Denizet a ?crit : > > and in looking at the 7th link you'll understand that Sylvestre moved > the file ScilabString from scilabTypes to types ! Calixte is right. I did that because the previous package naming (org.scilab.modules.types.scilabTypes.ScilabString) was containing some useless information. If Metanet hasn't been updated, it is mainly because we are first working on the stable release of Scilab 5.3.0. Sylvestre -- ------------------------- Sylvestre Ledru ------------------------- The Scilab Consortium Digiteo Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex France From sylvestre.ledru at scilab.org Sat Nov 6 19:18:00 2010 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Sat, 06 Nov 2010 19:18:00 +0100 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <201011041510.38633.bvl@btconnect.com> References: <201010290328.57390.bvl@btconnect.com> <1288615362.2567.8.camel@Calixte-Dell> <201011011523.12985.bvl@btconnect.com> <201011041510.38633.bvl@btconnect.com> Message-ID: <1289067480.5389.1065.camel@zlarin> Le jeudi 04 novembre 2010 ? 15:10 +0000, bv a ?crit : > On Monday 01 November 2010 15:23:12 bv wrote: > > On Monday 01 November 2010 12:42:42 Calixte Denizet wrote: > > > Hello, > > > > > > what's the output of : > > > # ldconfig -v | grep libamd > > > > > > and the output of > > > $ readelf -a /path/to/lib/libamd.so | grep amd_info > > > > root [ ~ ]# ldconfig -v | grep libamd > > libamd.so.2.2.1 -> libamd.so.2.2.1 > > root [ ~ ]# > > > > > > root [ ~ ]# readelf -a /usr/local/numerics/lib/libamd.so | grep amd_info > > 23: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > 48: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > 60: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > 88: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > root [ ~ ]# > > > I supplied the above answers on Monday and I would be grateful to know if > there is a problem with them or otherwise. --without-umfpack will be way easier here... Sylvestre -- ------------------------- Sylvestre Ledru ------------------------- The Scilab Consortium Digiteo Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex France From calixte at contrib.scilab.org Sat Nov 6 18:25:57 2010 From: calixte at contrib.scilab.org (Calixte Denizet) Date: Sat, 06 Nov 2010 18:25:57 +0100 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <1289067480.5389.1065.camel@zlarin> References: <201010290328.57390.bvl@btconnect.com> <1288615362.2567.8.camel@Calixte-Dell> <201011011523.12985.bvl@btconnect.com> <201011041510.38633.bvl@btconnect.com> <1289067480.5389.1065.camel@zlarin> Message-ID: <1289064357.13469.2.camel@Calixte-Dell> Ceci dit le amd_info prend un double* en param et qd tu appelles amd_info() ca fait une erreur de segmentation (ca va prendre n'importe quoi dans la pile)... Le samedi 06 novembre 2010 ? 19:18 +0100, Sylvestre Ledru a ?crit : > Le jeudi 04 novembre 2010 ? 15:10 +0000, bv a ?crit : > > On Monday 01 November 2010 15:23:12 bv wrote: > > > On Monday 01 November 2010 12:42:42 Calixte Denizet wrote: > > > > Hello, > > > > > > > > what's the output of : > > > > # ldconfig -v | grep libamd > > > > > > > > and the output of > > > > $ readelf -a /path/to/lib/libamd.so | grep amd_info > > > > > > root [ ~ ]# ldconfig -v | grep libamd > > > libamd.so.2.2.1 -> libamd.so.2.2.1 > > > root [ ~ ]# > > > > > > > > > root [ ~ ]# readelf -a /usr/local/numerics/lib/libamd.so | grep amd_info > > > 23: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > > 48: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > > 60: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > > 88: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > > root [ ~ ]# > > > > > > I supplied the above answers on Monday and I would be grateful to know if > > there is a problem with them or otherwise. > --without-umfpack will be way easier here... > > Sylvestre > From sylvestre.ledru at scilab.org Sat Nov 6 19:30:52 2010 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Sat, 06 Nov 2010 19:30:52 +0100 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <1289064357.13469.2.camel@Calixte-Dell> References: <201010290328.57390.bvl@btconnect.com> <1288615362.2567.8.camel@Calixte-Dell> <201011011523.12985.bvl@btconnect.com> <201011041510.38633.bvl@btconnect.com> <1289067480.5389.1065.camel@zlarin> <1289064357.13469.2.camel@Calixte-Dell> Message-ID: <1289068252.5389.1101.camel@zlarin> Yep, this is an expected behavior. The configure is just trying to link against the symbol of the library (with the C library, it has no way to check the consistency of the input argument of the C function at link time). It is not called. Sylvestre Le samedi 06 novembre 2010 ? 18:25 +0100, Calixte Denizet a ?crit : > Ceci dit le amd_info prend un double* en param et qd tu appelles > amd_info() ca fait une erreur de segmentation (ca va prendre n'importe > quoi dans la pile)... > > Le samedi 06 novembre 2010 ? 19:18 +0100, Sylvestre Ledru a ?crit : > > Le jeudi 04 novembre 2010 ? 15:10 +0000, bv a ?crit : > > > On Monday 01 November 2010 15:23:12 bv wrote: > > > > On Monday 01 November 2010 12:42:42 Calixte Denizet wrote: > > > > > Hello, > > > > > > > > > > what's the output of : > > > > > # ldconfig -v | grep libamd > > > > > > > > > > and the output of > > > > > $ readelf -a /path/to/lib/libamd.so | grep amd_info > > > > > > > > root [ ~ ]# ldconfig -v | grep libamd > > > > libamd.so.2.2.1 -> libamd.so.2.2.1 > > > > root [ ~ ]# > > > > > > > > > > > > root [ ~ ]# readelf -a /usr/local/numerics/lib/libamd.so | grep amd_info > > > > 23: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > > > 48: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > > > 60: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > > > 88: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > > > root [ ~ ]# > > > > > > > > > I supplied the above answers on Monday and I would be grateful to know if > > > there is a problem with them or otherwise. > > --without-umfpack will be way easier here... > > > > Sylvestre > > > > -- ------------------------- Sylvestre Ledru ------------------------- The Scilab Consortium Digiteo Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex France From calixte at contrib.scilab.org Sat Nov 6 18:33:30 2010 From: calixte at contrib.scilab.org (Calixte Denizet) Date: Sat, 06 Nov 2010 18:33:30 +0100 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <1289068252.5389.1101.camel@zlarin> References: <201010290328.57390.bvl@btconnect.com> <1288615362.2567.8.camel@Calixte-Dell> <201011011523.12985.bvl@btconnect.com> <201011041510.38633.bvl@btconnect.com> <1289067480.5389.1065.camel@zlarin> <1289064357.13469.2.camel@Calixte-Dell> <1289068252.5389.1101.camel@zlarin> Message-ID: <1289064810.13469.5.camel@Calixte-Dell> Le samedi 06 novembre 2010 ? 19:30 +0100, Sylvestre Ledru a ?crit : > Yep, this is an expected behavior. > The configure is just trying to link against the symbol of the library > (with the C library, it has no way to check the consistency of the input > argument of the C function at link time). > It is not called. > Ok, thanks for this information. Calixte > Sylvestre > > > Le samedi 06 novembre 2010 ? 18:25 +0100, Calixte Denizet a ?crit : > > Ceci dit le amd_info prend un double* en param et qd tu appelles > > amd_info() ca fait une erreur de segmentation (ca va prendre n'importe > > quoi dans la pile)... > > > > Le samedi 06 novembre 2010 ? 19:18 +0100, Sylvestre Ledru a ?crit : > > > Le jeudi 04 novembre 2010 ? 15:10 +0000, bv a ?crit : > > > > On Monday 01 November 2010 15:23:12 bv wrote: > > > > > On Monday 01 November 2010 12:42:42 Calixte Denizet wrote: > > > > > > Hello, > > > > > > > > > > > > what's the output of : > > > > > > # ldconfig -v | grep libamd > > > > > > > > > > > > and the output of > > > > > > $ readelf -a /path/to/lib/libamd.so | grep amd_info > > > > > > > > > > root [ ~ ]# ldconfig -v | grep libamd > > > > > libamd.so.2.2.1 -> libamd.so.2.2.1 > > > > > root [ ~ ]# > > > > > > > > > > > > > > > root [ ~ ]# readelf -a /usr/local/numerics/lib/libamd.so | grep amd_info > > > > > 23: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > > > > 48: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > > > > 60: 0000000000000000 0 FILE LOCAL DEFAULT ABS amd_info.c > > > > > 88: 0000000000003800 1493 FUNC GLOBAL DEFAULT 10 amd_info > > > > > root [ ~ ]# > > > > > > > > > > > > I supplied the above answers on Monday and I would be grateful to know if > > > > there is a problem with them or otherwise. > > > --without-umfpack will be way easier here... > > > > > > Sylvestre > > > > > > > > From luga_2003 at hotmail.com Sun Nov 14 23:11:45 2010 From: luga_2003 at hotmail.com (Lucas Benitez Demmler) Date: Sun, 14 Nov 2010 22:11:45 +0000 Subject: FW: Help !--error 21 In-Reply-To: References: Message-ID: Hello, My name is Lucas , I'm from Argentina , and I'm a frecuently user of Scilab. I found a problem when I try to run "spdsolver.sci" I have a problem when i want to run "SPDsolver.sci" In command window appears an error after executing this: !--error 21 Invalid index SPDSolve file use internally a function called SPDverif but i don't understand why it is not working. Both files were translated form MATLAB to SCILAB and i use loadmatfile command to load all the variables. I would like to know where the mistake is. I'm sending you the .sci files for testing thanks in advance for your help Lucas Benitez Demmler Universidad Tecnologica Nacional - FRHaedo - Bs As - Argentina -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SPDverif.sci Type: application/octet-stream Size: 1961 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SPDsolve.sci Type: application/octet-stream Size: 2299 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fuselage_after_bc.mat Type: application/octet-stream Size: 69812 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Scilab console.JPG Type: image/pjpeg Size: 45114 bytes Desc: not available URL: From mathieu.olivier at cnrm.meteo.fr Mon Nov 15 09:13:05 2010 From: mathieu.olivier at cnrm.meteo.fr (OLIVIER Mathieu) Date: Mon, 15 Nov 2010 09:13:05 +0100 Subject: [Scilab-Dev] FW: Help !--error 21 In-Reply-To: References: Message-ID: <4CE0EB91.3050306@cnrm.meteo.fr> Hi, Try with : function lines0_K0=zeroslines(K0) lines0=[]; cont=0; for j=1:size(K0,2) if K0(:,j)==0 cont=cont+1; lines0_K0(cont)=j; else end end endfunction To my mind, the error come from the use of "length". Best regards Mathieu OLIVIER On 14/11/2010 23:11, Lucas Benitez Demmler wrote: > Hello, My name is Lucas , I'm from Argentina , and I'm a frecuently user > of Scilab. I found a problem when I try to run "spdsolver.sci" > I have a problem when i want to run "SPDsolver.sci" > In command window appears an error after executing this: > !--error 21 > Invalid index > > SPDSolve file use internally a function called SPDverif but i don't > understand why it is not working. > Both files were translated form MATLAB to SCILAB and i use loadmatfile > command to load all the variables. > I would like to know where the mistake is. > I'm sending you the .sci files for testing > thanks in advance for your help > > Lucas Benitez Demmler > Universidad Tecnologica Nacional - FRHaedo - Bs As - Argentina -- Mathieu OLIVIER CNRM/GMEI/LISA Navier Bureau 033 M?t?o-France 42 Av. G. Coriolis 31057 Toulouse Cedex Tel : +33 5 61 07 98 01 Port : +33 6 88 48 73 20 Mail : mathieu.olivier at cnrm.meteo.fr From bvl at btconnect.com Mon Nov 15 15:16:30 2010 From: bvl at btconnect.com (bv) Date: Mon, 15 Nov 2010 14:16:30 +0000 Subject: [Scilab-Dev] Oh scilab!what a beaut you are you are if only you'd build without the war In-Reply-To: <201010291047.08354.bvl@btconnect.com> References: <201010290328.57390.bvl@btconnect.com> <1288328303.5490.32446.camel@korcula.inria.fr> <201010291047.08354.bvl@btconnect.com> Message-ID: <201011151416.30697.bvl@btconnect.com> On Friday 29 October 2010 10:47:08 bv wrote: > On Friday 29 October 2010 05:58:23 Sylvestre Ledru wrote: > > Le vendredi 29 octobre 2010 ? 03:28 +0100, bv a ?crit : > > > Greetings, > > > > > > > > > I am atempting to compile scilab-5.2.2 on a machine with these:- > > > ---cpu-amd64 2 cores > > > ---o/s CBLFS linux (64-bit only) compiled from sources kernel-2.6.32 > > > ---numerical progs: atlas3.9.26,lapack-3.2.2 and umfpack~co > > > > > > > > > I have umfpack and co in /usr/local/numerics > > > rt [ ~ ]# ls /usr/local/numerics/lib > > > libamd.a libcamd.a libcerbla.a libcolamd.a libcxsparse.a > > > libldl.a libumfpack.a > > > libbtf.a libccolamd.a libcholmod.a libcsparse.a libklu.a > > > libspqr.a rt [ ~ ]# > > > > Usually, Scilab is expecting some dynamic libraries to build correctly. > > [...] > > ....ehm here is the home of SuiteSparse > http://www.cise.ufl.edu/research/sparse/SuiteSparse/ After a lot of to-ing and fro-ing I think I have found a resolution. AND it does net seem to be related to having shared libraries. In a nutshell, Scilab-5.2.2 seems to require the now ageing components of SuiteSparse-3.4.0 and I was using the new{er/est} components. (The latter for example has UMFPACK-5.5..0 with at least one source file umf_cholmod.c (or some such) not in the UMFPACK in the ageing SuiteSparse-3.4.0.). This is the narrative:- -- I compiled both shared libraries and static libraries of the new components and the scilab-5.2.2 configure script failed complaining it cound not find umfpack.h --I set CPPFLAGS to point to the OLD (i.e. as in SuiteSparse-3.4.0) umfpach.h with NEW (i.e. from UMFPACK-5.5.0) libumfpack..a and the configure script generated Makefiles and a successful scilab-5.2.2 build resulted --I rebuilt SuitSparse-3.4.0 with both sharedlibs and static libs AND the Scilab-5.2.2 configure script failed with shared libs but the build succeed with static libs. perhaps you shoud update scilab upstream so that the newer components of SuiteSparse can be used. sincerely bv From deanm at sharplabs.com Wed Nov 17 20:24:21 2010 From: deanm at sharplabs.com (Dean S. Messing) Date: Wed, 17 Nov 2010 11:24:21 -0800 Subject: Serious bug in find()? Message-ID: Before I submit this to Bugzilla I'd like your expert opinions: does the following tickle a longstanding bug in find()? I have is an array of 19,200,000 reals. There are seven sub-vectors w/in the array that each contain 2000 Nan's (due to hardware failure in a device). When I use find() together with isnan() to find the beginning of each sub-vector, some indices that find() returns are off by 1. Following is a short script to demonstrate. This bug is in both scilab-branch-5.3 and scilab-4.1.1. I've verified that the vector isnan() returns is correct. How to demonstrate the bug: Fire up Scilab and run the following script: // Generate a vector, v, containing 7 subvectors == %nan*ones(2000,1) // Each subvector begins at a multiple of 2000 (plus 1). stacksize(100000000) clear v v=rand(19200000,1); i=[10336001,.. 13716001,.. 15400001,.. 15402001,.. 18278001,.. 18762001,.. 19198001]; for j=i v(j:j+1999) = %nan*ones(2000,1); end // w conforms to v and contains %t everywhere v == %nan. w=isnan(v); // w1 are the indices in v at whose location v == %nan w1=find(w); // zero out all the Nan's in v. v(w1) = 0; // This shd. be a real. But it's Nan! // So v still contains at least one Nan. sum(v) // Step though w1 to and print the seven starting indices of each // subvector of Nan's in v. w1(1 : 2000 : 7*2000) The output of the last two insructions is: -->sum(v) ans = Nan --> -->// Step though w1 to and print the seven starting indices of each -->// subvector of Nan's in v. -->w1(1 : 2000 : 7*2000) ans = 10336001. 13716001. 15400001. 15402001. 18278000. 18762000. 19198000. The last three indices are off by 1! Indeed, for example, w(18278000) == %f and w(18278001) == %t. So find() has returned the wrong indices! Dean From Serge.Steer at inria.fr Thu Nov 18 10:21:07 2010 From: Serge.Steer at inria.fr (Serge Steer) Date: Thu, 18 Nov 2010 10:21:07 +0100 Subject: [Scilab-Dev] Serious bug in find()? In-Reply-To: References: Message-ID: <4CE4F003.8060008@inria.fr> Le 17/11/2010 20:24, Dean S. Messing a ?crit : > Before I submit this to Bugzilla I'd like your expert opinions: does the > following tickle a longstanding bug in find()? > > I have tested your script with Scilab-4.1.2 and Scilab-5.3.0-beta-4 under Linux (SuSe 11.2) in both case no problem detected sum gives a finite result and find(isnan(v)) returns an empty matrix. Please enter a bug report, but give your OS configuration.... Serge Steer > I have is an array of 19,200,000 reals. There are seven sub-vectors > w/in the array that each contain 2000 Nan's (due to hardware failure in > a device). > > When I use find() together with isnan() to find the beginning of each > sub-vector, some indices that find() returns are off by 1. Following is > a short script to demonstrate. This bug is in both scilab-branch-5.3 > and scilab-4.1.1. I've verified that the vector isnan() returns is > correct. > > How to demonstrate the bug: > > Fire up Scilab and run the following script: > > // Generate a vector, v, containing 7 subvectors == %nan*ones(2000,1) > // Each subvector begins at a multiple of 2000 (plus 1). > stacksize(100000000) > clear v > v=rand(19200000,1); > i=[10336001,.. > 13716001,.. > 15400001,.. > 15402001,.. > 18278001,.. > 18762001,.. > 19198001]; > for j=i > v(j:j+1999) = %nan*ones(2000,1); > end > > > // w conforms to v and contains %t everywhere v == %nan. > w=isnan(v); > > // w1 are the indices in v at whose location v == %nan > w1=find(w); > > // zero out all the Nan's in v. > v(w1) = 0; > > // This shd. be a real. But it's Nan! > // So v still contains at least one Nan. > sum(v) > > // Step though w1 to and print the seven starting indices of each > // subvector of Nan's in v. > w1(1 : 2000 : 7*2000) > > > > > The output of the last two insructions is: > > -->sum(v) > ans = > > Nan > > --> > > -->// Step though w1 to and print the seven starting indices of each > > -->// subvector of Nan's in v. > > -->w1(1 : 2000 : 7*2000) > ans = > > 10336001. 13716001. 15400001. 15402001. 18278000. 18762000. 19198000. > > The last three indices are off by 1! > > Indeed, for example, w(18278000) == %f and w(18278001) == %t. > So find() has returned the wrong indices! > > Dean > > From deanm at sharplabs.com Thu Nov 18 20:51:13 2010 From: deanm at sharplabs.com (Dean S. Messing) Date: Thu, 18 Nov 2010 11:51:13 -0800 Subject: [Scilab-Dev] Serious bug in find()? In-Reply-To: <4CE4F003.8060008@inria.fr> (message from Serge Steer on Thu, 18 Nov 2010 10:21:07 +0100) References: <4CE4F003.8060008@inria.fr> Message-ID: Serge Steer wrote: > Le 17/11/2010 20:24, Dean S. Messing a ?crit : > > Before I submit this to Bugzilla I'd like your expert opinions: does the > > following tickle a longstanding bug in find()? > > > > > I have tested your script with Scilab-4.1.2 and Scilab-5.3.0-beta-4 > under Linux (SuSe 11.2) in both case no problem detected > sum gives a finite result and find(isnan(v)) returns an empty matrix. > > Please enter a bug report, but give your OS configuration.... I shall do so. I realised after I sent this off that I had forgotten this info. FYI, I'm running an up-to-date Fedora 13 system. I cannot imagine what would cause this problem. The only thing in common between the two Scilabs I tried where that they were both compiled from source with the same compiler (on the same system, of course). (I had the scilab-4.1.1 source laying around). I'll download the binary of 5.3.0 and try it with that too. Dean From deanm at sharplabs.com Fri Nov 19 02:07:42 2010 From: deanm at sharplabs.com (Dean S. Messing) Date: Thu, 18 Nov 2010 17:07:42 -0800 Subject: [Scilab-Dev] Serious bug in find()? In-Reply-To: <4CE4F003.8060008@inria.fr> (message from Serge Steer on Thu, 18 Nov 2010 10:21:07 +0100) References: <4CE4F003.8060008@inria.fr> Message-ID: I've submitted a bug report on this and added new info on what machines it appears on and a slightly modified script that clarifies the nature of the find() bug somewhat: I apologise for assigning the severity as "Critical" instead of "Major". Truth is that I meant to change it back to Major after I finished writing and just forgot. (Maybe it is critical after all :-). Dean From mruggeri at frh.utn.edu.ar Mon Nov 22 13:20:59 2010 From: mruggeri at frh.utn.edu.ar (Marcos C. Ruggeri) Date: Mon, 22 Nov 2010 09:20:59 -0300 Subject: Error command loadmatfile In-Reply-To: <001601cb89f4$3d6f7010$b84e5030$@utn.edu.ar> References: <001601cb89f4$3d6f7010$b84e5030$@utn.edu.ar> Message-ID: <001c01cb8a3f$bb249260$316db720$@utn.edu.ar> Hi all, I am receiving an error message in the Scilab Console when using the command loadmatfile to import a .mat file (e.g. test_fuselage_complete.mat). However, the command seems to work correctly if I load other .mat files, such as data_high_volt_tower.mat. I have tried updating Scilab, and the same error occurs in both versions: scilab-5.2.2 and scilab-5.3.0-beta-4. Enclosed is a screenshot of the console and the .mat files. Thanks in advance. Regards, Marcos Cesar Ruggeri Grupo de Simulaci?n y Mec?nica Computacional Universidad Tecnol?gica Nacional Facultad Regional Haedo mruggeri at frh.utn.edu.ar www.frh.utn.edu.ar -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: error_loadmatfile.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: data_high_volt_tower.mat Type: application/octet-stream Size: 1185 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test_fuselage_complete.mat Type: application/octet-stream Size: 73412 bytes Desc: not available URL: From vincent.couvert at scilab.org Mon Nov 22 13:29:28 2010 From: vincent.couvert at scilab.org (Vincent COUVERT) Date: Mon, 22 Nov 2010 13:29:28 +0100 Subject: [Scilab-Dev] Error command loadmatfile In-Reply-To: <001c01cb8a3f$bb249260$316db720$@utn.edu.ar> References: <001601cb89f4$3d6f7010$b84e5030$@utn.edu.ar> <001c01cb8a3f$bb249260$316db720$@utn.edu.ar> Message-ID: <4CEA6228.4000102@scilab.org> Hi, This seems to be a Scilab bug. Please report a bug at http://bugzilla.scilab.org/ and attach your files. Regards. Le 22/11/10 13:20, Marcos C. Ruggeri a ?crit : > > Hi all, > > I am receiving an error message in the Scilab Console when using the > command loadmatfile to import a .mat file (e.g. > test_fuselage_complete.mat). > > However, the command seems to work correctly if I load other .mat > files, such as data_high_volt_tower.mat. > > I have tried updating Scilab, and the same error occurs in both > versions: scilab-5.2.2 and scilab-5.3.0-beta-4. > > Enclosed is a screenshot of the console and the .mat files. > > Thanks in advance. > > Regards, > > Marcos Cesar Ruggeri > > /Grupo de Simulaci?n y Mec?nica Computacional/ > > *Universidad Tecnol?gica Nacional* > > Facultad Regional Haedo > > mruggeri at frh.utn.edu.ar > > www.frh.utn.edu.ar > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.gareste at scilab.org Wed Nov 24 15:04:25 2010 From: simon.gareste at scilab.org (Simon GARESTE) Date: Wed, 24 Nov 2010 15:04:25 +0100 Subject: Release of Scilab 5.3.0 - beta 5 Message-ID: <4CED1B69.1050501@scilab.org> Dear all, The Scilab Consortium R&D Team is pleased to announce the release of Scilab 5.3.0 Beta 5 today. You can download it directly from Scilab website at: http://www.scilab.org/products/scilab/download/5.3.0-beta-5 Best Regards, ----------------------------------------------- The Scilab Consortium R&D Team ----------------------------------------------- Digiteo Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex - France" From sylvestre.ledru at scilab.org Thu Nov 25 10:47:17 2010 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 25 Nov 2010 10:47:17 +0100 Subject: Code convention / Coding style Message-ID: <1290678437.24790.10.camel@korcula.inria.fr> Hello Playing with the "indent" program, I published on the wiki the list of all arguments in order to have a C / C++ code complying to the Coding Style of Scilab: http://wiki.scilab.org/Code_Conventions_for_the_C_Programming_Language The command: indent -npro --braces-after-if-line -i4 -ts4 -sob -ss -ncs -sc --no-space-after-parentheses -cp1 --no-tabs -bap -bad -npcs --dont-break-function-decl-args --dont-break-procedure-type -bli0 -l150 -il0 will update the source code to the coding style. Cheers, Sylvestre From clement.david at scilab.org Thu Nov 25 11:01:40 2010 From: clement.david at scilab.org (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Thu, 25 Nov 2010 11:01:40 +0100 Subject: [Scilab-Dev] Code convention / Coding style In-Reply-To: <1290678437.24790.10.camel@korcula.inria.fr> References: <1290678437.24790.10.camel@korcula.inria.fr> Message-ID: <1290679300.2479.2.camel@pinarellu.inria.fr> Hello, Thanks for the tips. I have included it in my attached pre-commit hook. > Hello > > Playing with the "indent" program, I published on the wiki the list of > all arguments in order to have a C / C++ code complying to the Coding > Style of Scilab: > http://wiki.scilab.org/Code_Conventions_for_the_C_Programming_Language > > The command: > indent -npro --braces-after-if-line -i4 -ts4 -sob -ss -ncs -sc > --no-space-after-parentheses -cp1 --no-tabs -bap -bad -npcs > --dont-break-function-decl-args --dont-break-procedure-type -bli0 -l150 > -il0 > > will update the source code to the coding style. > > Cheers, > Sylvestre > > -- Cl?ment David -------------- next part -------------- A non-text attachment was scrubbed... Name: pre-commit Type: application/x-shellscript Size: 1674 bytes Desc: not available URL: From michael.baudin at scilab.org Tue Nov 30 14:41:42 2010 From: michael.baudin at scilab.org (=?ISO-8859-1?Q?Micha=EBl_Baudin?=) Date: Tue, 30 Nov 2010 14:41:42 +0100 Subject: New scientific features & Performances of linear algebra Message-ID: <4CF4FF16.7070202@scilab.org> Hello, We are often asked about the new computational features of Scilab. The CHANGES file associated with each release provides some information, but it mainly focuses on the updates and does not provide the context of the new features. Moreover, this does not give any informations about the external modules, provided by ATOMS, for example. This is why we have written the wiki page : http://wiki.scilab.org/New_Scientific_Features The goal of this page is to focus on the new scientific, computational features in Scilab. This document aims at presenting a short abstract of the each new module along with the changes that were made to it. This allows to gather the various developments which are made both inside Scilab and outside Scilab, for example as external modules. By this mean, we can have a knowledge of the computational algorithms and functions which are available in the Scilab environment, in a broad sense. The presentation is based on a year-by-year analysis, from 2008 to 2010. We had recently the opportunity to check the performances of linear algebra in Scilab. In order to gather the best performances which can be obtained with linear algebra algorithms provided in Scilab, we have created the page : http://wiki.scilab.org/Linalg_performances In this page, we present performance of various Scilab scripts involving linear algebra. We emphasize the use of Mflops as a measure of performance of linear algebra routines used in Scilab. We consider here two benchmarks: * the dense, real, matrix-matrix multiply, * the solution of dense, real linear systems of equations. These wiki pages are designed to be improved by anyone willing to. Please insert directly any information that you would like to publish. Best regards, Micha?l Baudin -- Micha?l Baudin Ing?nieur de d?veloppement michael.baudin at scilab.org ------------------------- Consortium Scilab - Digiteo Domaine de Voluceau - Rocquencourt B.P. 105 - 78153 Le Chesnay Cedex Tel. : 01 39 63 56 87 - Fax : 01 39 63 55 94