[scilab-Users] Mac OS 10.5 Compilation issue

Sylvestre Ledru sylvestre.ledru at scilab.org
Mon Jan 5 10:52:04 CET 2009



Le dimanche 04 janvier 2009 à 18:19 -0500, Eric E a écrit :
> > Well, depends what you mean by "tests of the build", if you want to
> > check the creation of the binary itself, "make macros" is calling Scilab
> > to build our macros.
> > If you want to test Scilab features, "make check" is your friend.

> 315/1152 - [fileio]
> dir..........................................failed  : error_output
> not empty
> 
> Is this standard, or should I look into the outputs of make check?
The output are probably just warnings.
Try to run Scilab like ./bin/scilab -nw. You should not get any output;
if you do, it is what is causing the "error_output not empty".

> > In the root directory of the source tree, what is the result of
> > $ grep -E "(^INSTALL =|^INSTALL_DATA =)" Makefile
> > ?
> >Under Linux, I get:
> >INSTALL = /usr/bin/install -c
> >INSTALL_DATA = ${INSTALL} -m 644
> 
> I get the same thing as you do:
> INSTALL = /usr/bin/install -c
> INSTALL_DATA = ${INSTALL} -m 644
Funny, could you send the modules/core/Makefile file ?

Thx.
Sylvestre
PS: if you are registered to the dev mailing list, we could switch on
this mailing list since it is quite technical questions.





More information about the users mailing list