> I really wonder what those patches are about. AFAIK they are related to
> backporting changes to releases, but the need for this disappears
> completely if the upstream sources are all the time consistent with Sage.
Under the current development and testing model, that would be
extremely hard to do.
> > But what you *could* do is the following:
> > [...]
> > and see what happens.
>
> Hmm, again, it is not something that I would like to do on my own computer,
> but rather provide a daily tarball or "spkg" to be tested in that bot.
>
Yeah, I don't know whether that could be 100% automated or not.
Possibly?
> There is not so much stuff that you can delete: just the libraries that ECL
> ships with it (GMP, Boehm-GC, libffi). Assuming that they are already
> available in Sage, they are not even needed in a normal build -- for
> instance, on my copy of Ubuntu, I rarely use the versions that come with
> ECL, as the operating system already provides better versions --. The rest
> is very much integrated and is what has to be tested.
Just for reference, here is what we delete, and a few other things.
== Special Update/Build Instructions ==
* Deleting the following directories saves space: without doing
this, the spkg can grow from under 2.5 megabytes to almost 7
megabytes. Deleting these files is done automatically by the
`spkg-make` script.
- The directory src/msvc/
- The directory src/src/gc-unstable
- The directory src/src/libffi
- Most of the contents of the src/src/gmp directory:
everything except install-sh, config.*, configfsf.*
- The directory src/contrib/encodings/
- The directory src/contrib/unicode/
* The directories src/contrib/encodings/ and src/contrib/unicode/ may
be removed because we build with --enable-unicode=no.
Building with --enable-unicode=yes, the default in the latest ECL
source, leads to problems with some strings in the Sage-Maxima-ECL
interface.
* Note: the way we configure Sage, CXX and CXXFLAGS are unused.
* Do NOT quote SAGE_LOCAL when setting CPPFLAGS and/or LDFLAGS,
in spkg-install as this caused the build to break. See
http://trac.sagemath.org/sage_trac/ticket/10187#comment:117
* TODO: Add the ECL test suite, and an spkg-check file to run it.
* TODO: Make ECL use Sage's Boehm GC on MacOS X as well (but perhaps
put some changes from ECL's into Sage's Boehm GC), then remove
the src/src/gc directory, too.
The only current patch is from #11119 [2]
diff -r -u src/src/c/ffi/libraries.d src.patched/src/c/ffi/libraries.d
--- src/src/c/ffi/libraries.d 2011-11-07 21:16:18.000000000 +0100
+++ src.patched/src/c/ffi/libraries.d 2011-11-15 11:13:42.000000000
+0100
@@ -70,6 +70,7 @@
#endif /* ENABLE_DLOPEN */
#include <ecl/ecl-inl.h>
#include <ecl/internal.h>
+#include <sys/stat.h>
cl_object
ecl_make_codeblock()
This is for Cygwin. We should only apply it then, but that was before
I knew how to do that. Sorry we didn't report that upstream.
[1] http://cygwin.com/ml/cygwin/2011-04/msg00336.html
[2] http://trac.sagemath.org/sage_trac/ticket/11119
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
