On 06/ 6/10 11:39 PM, William Stein wrote:
In case anybody from Singular is reading this -- the above is the
opinion of David and not the Sage project as a whole. I'll add that,
in my experience, Singular is fairly easy to build and portable, more
so than many other programs. When I've personally poked around in
the Singular source code and actually tried to understand the code,
it's been surprisingly easy to understand, compared to many other
sophisticated C++ programs.
That may be true, but the build process is far from clean.
Type
$ configure
$ make
$ make distclean
and it appears to delete a load of files. Then type:
$ configure
$ make
and it reports:
make: `/tmp/Singular-3-1-1/ix86-SunOS/Singular-3-1-1' is up to date.
in other words, the 'make distclean' is not cleaning things properly. There is
no 'make check' or 'make test'. The configure script silently ignores what
appear to be unsupported options like '--without-bison'
I've not looked at the C/C++ source code, but accept it might be quite clear.
The build process is far from clean.
The spkg-install in Sage is also rather messy, with tons of options that are not
listed by the configure script as being valid options.
Regarding multiple copies of install-sh, please note that like Sage,
Singular is built up from other libraries and components. One could
criticize Sage on the same grounds for including multiple copies of
various autoconf scripts in the various src/ subdirectories of spkg's.
As such, I think this hack is the best we can do.
It at least allows Sage to build when flex is not installed.
I think using touch is reasonable given the circumstances.
Me too.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
