[scilab-Users] scilab 5.1.1 compilation under Solaris 10
Langella Raphael
raphael.langella at steria.cnes.fr
Thu Sep 17 12:40:26 CEST 2009
> > I've also found out what was wrong with the make install
> under Solaris 9. In libs/blas/Makefile, line 890, there is :
> >
> > for specialExt in $(MACROSSPECIALEXT); do \
> >
> > But the MACROSSPECIALEXT is empty and the shell doesn't
> like it. So I've delete this line and the next 3 ones, and
> did the same in all the (~70!) other Makefiles. Now make
> install works, but it really is an ugly workaround, there
> should be a better way of fixing this.
> :)
> Indeed, there is easier way.
> This stuff is declared in Makefile.incl.am and all makefile
> can be regenerated with autoreconf.
> You will find the patch attached to this email.
> Apply it and launch autoreconf
> it should fix you problem
well, it should have, but it didn't:
/bin/bash: -c: line 1: syntax error near unexpected token `;'
/bin/bash: -c: line 1: `echo "-------- Install macros (if any)
--------"; for dir in macros/ ; do /bin/bash
/Produits/tmp/rla/Sol9/scilab-5.1.1/config/install-sh -d
/Produits/publics/sparc.SunOS.5.9/scilab/5.1.1/share/scilab/modules/blas
/$dir && if test -d ./$dir/; then FILELIST="./$dir/*.sci ./$dir/*.bin
./$dir/*.sce ./$dir/names ./$dir/lib"; if test -n ""; then for
specialExt in ; do specialExtDir="$specialExtDir ./$dir/$specialExt";
done; FILELIST="$FILELIST $specialExtDir"; fi; for file in `ls -1
$FILELIST 2>/dev/null`; do echo
"/Produits/publics/sparc.SunOS.5.9/bin/install -c -m 644 $file
/Produits/publics/sparc.SunOS.5.9/scilab/5.1.1/share/scilab/modules/blas
/$dir" ; /Produits/publics/sparc.SunOS.5.9/bin/install -c -m 644
"$file"
/Produits/publics/sparc.SunOS.5.9/scilab/5.1.1/share/scilab/modules/blas
/$dir ; done; fi; done'
gmake[3]: *** [install-data-local] Error 2
gmake[3]: Leaving directory
`/nfs/Produits/tmp/rla/Sol9/scilab-5.1.1/libs/blas'
But I found another workaround. I changed:
for specialExt in $(MACROSSPECIALEXT); do \
by
for specialExt in "$(MACROSSPECIALEXT) " ; do \
It just didn't like the empty string, but with a space it's ok.
by the way, my (stupid) shell version is:
GNU bash, version 2.05.0(1)-release (sparc-sun-solaris2.9)
More information about the dev
mailing list