Re: [sage-devel] maxima install should not consider local config files
I'll see if I can figure that out. The Lisp is ECL, which I'm not very familiar with. Bill On Wednesday, September 23, 2015 at 11:57:38 PM UTC-7, François wrote: > > > > On 24/09/2015, at 16:51, Bill Janssen <bill.j...@gmail.com > > wrote: > > > > Compiling Sage from scratch (6.8 sources) fails because the maxima > install fails, because it loads ~/quicklisp/setup.lisp. > > > > Am I the first Lisp programmer to try this? > > I suspect you are. Is there a variable you can set to point to a > “setup.lisp” file? > If there is we could had a location in the sage install tree to bypass any > local > files. And can you open a ticket. > > François -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] sage -update not working
I downloaded the OS X version of Sage 6.8, unpacked it, and tried to run "sage -update". However, it fails immediately: touch /Volumes/datanew/local/sage-6.8/local/var/lib/sage/installed/prereq /Volumes/datanew/local/sage-6.8/build/pipestatus "sage-spkg -f bzip2-1.0.6.20140317 2>&1" "tee -a /Volumes/datanew/local/sage-6.8/logs/pkgs/bzip2-1.0.6.20140317.log" Found local metadata for bzip2-1.0.6.20140317 Attempting to download package bzip2-1.0.6.20140317 >>> Trying to download http: //www.sagemath.org/packages/upstream/bzip2/bzip2-1.0.6.20140317.tar.gz [Traceback (most recent call last): File "", line 35, in File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", line 240, in retrieve fp = self.open(url, data) File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", line 208, in open return getattr(self, name)(url) File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", line 359, in open_http return self.http_error(url, fp, errcode, errmsg, headers) File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", line 376, in http_error return self.http_error_default(url, fp, errcode, errmsg, headers) File "", line 17, in http_error_default IOError: [Errno 404] Not Found: '//www.sagemath.org/packages/upstream/bzip2/bzip2-1.0.6.20140317.tar.gz' Error: failed to download package bzip2-1.0.6.20140317 make[2]: *** [/Volumes/datanew/local/sage-6.8/local/var/lib/sage/installed/ bzip2-1.0.6.20140317] Error 1 make[1]: *** [all] Error 2 real0m8.869s user0m1.960s sys0m2.425s *** Error building Sage. The following package(s) may have failed to build: package: bzip2-1.0.6.20140317 log file: /Volumes/datanew/local/sage-6.8/logs/pkgs/bzip2-1.0.6.20140317.log build directory: /Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build/ bzip2-1.0.6.20140317 Sure enough, if I try to wget that location (https://www.sagemath.org/packages/upstream/bzip2/bzip2-1.0.6.20140317.tar.gz), I get a 404 error. Bill -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] maxima install should not consider local config files
Compiling Sage from scratch (6.8 sources) fails because the maxima install fails, because it loads ~/quicklisp/setup.lisp. Am I the first Lisp programmer to try this? Bill /usr/bin/install -c mgnuplot '/Volumes/datanew/local/sage-6.8/local/libexec/maxima/5.35.1' /bin/sh /Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build/maxima-5.35 .1.p2/src/install-sh -d make[5]: Nothing to be done for `install-exec-am'. /bin/sh /Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh -d ;;; Warning: Lisp compilation had style-warnings while compiling # Now installing the Maxima library as ';;; Loading #P"/tilde/janssen/quicklisp/setup.lisp" ;;; Loading #P"/Volumes/datanew/local/sage-6.8/local/lib/ecl/cmp.fas" ;;; Loading #P"/Volumes/datanew/local/sage-6.8/local/lib/ecl/asdf.fas" ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable EXPLAIN is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable PROMPT is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable VERBOSE is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable SYSTEMS is not used./Volumes/datanew/local/sage-6.8/local/lib/ecl//maxima.fas'... cp: ;;; Loading #P"/tilde/janssen/quicklisp/setup.lisp" ;;; Loading #P"/Volumes/datanew/local/sage-6.8/local/lib/ecl/cmp.fas" ;;; Loading #P"/Volumes/datanew/local/sage-6.8/local/lib/ecl/asdf.fas" ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable EXPLAIN is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable PROMPT is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable VERBOSE is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable SYSTEMS is not used./Volumes/datanew/local/sage-6.8/local/lib/ecl//maxima.fas: No such file or directory *** Error: Failed to install '/Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build/maxima-5.35.1.p2/src/src/binary-ecl/maxima.fas' as ';;; Loading #P"/tilde/janssen/quicklisp/setup.lisp" ;;; Loading #P"/Volumes/datanew/local/sage-6.8/local/lib/ecl/cmp.fas" ;;; Loading #P"/Volumes/datanew/local/sage-6.8/local/lib/ecl/asdf.fas" ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable EXPLAIN is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable PROMPT is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable VERBOSE is not used. ;;; Style warning: ;;; in file client.lisp, position 809 ;;; at (DEFMETHOD QUICKLOAD ...) ;;; ! The variable SYSTEMS is not used./Volumes/datanew/local/sage-6.8/local/lib/ecl//maxima.fas'. *** real6m27.393s user5m9.944s sys0m52.326s Error installing package maxima-5.35.1.p2 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /Volumes/datanew/local/sage-6.8/logs/pkgs/maxima-5.35.1.p2.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build/maxima-5.35.1.p2 and type 'make' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build/maxima-5.35.1.p2' && '/Volumes/datanew/local/sage-6.8/sage' --sh) When you are done debugging, you can type "exit" to leave the subshell. make[2]: *** [/Volumes/datanew/local/sage-6.8/local/var/lib/sage/installed/maxima-5.35.1.p2] Error 1 make[1]: *** [all] Error 2 real268m48.226s user224m41.870s sys33m53.334s *** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all'): * package: maxima-5.35.1.p2 log file: /Volumes/datanew/local/sage-6.8/logs/pkgs/maxima-5.35.1.p2.log build directory: /Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build/maxima-5.35.1.p2 The build directory may contain
[sage-devel] Re: sage -update not working
I'm trying to get around a build problem with sqlite3. I thought that doing an update might address that (I was wrong about that). But that's incidental; shouldn't "sage -update" work even if it's pointless? Bill On Wednesday, September 23, 2015 at 3:45:54 PM UTC-7, Dima Pasechnik wrote: > > > > On Wednesday, 23 September 2015 15:38:11 UTC-7, Bill Janssen wrote: >> >> I downloaded the OS X version of Sage 6.8, unpacked it, and tried to run >> "sage -update". However, it fails immediately: >> > > 6.8 is the latest stable version. What are you trying to upgrade? > > > >> >> touch /Volumes/datanew/local/sage-6.8/local/var/lib/sage/installed/prereq >> /Volumes/datanew/local/sage-6.8/build/pipestatus "sage-spkg -f >> bzip2-1.0.6.20140317 2>&1" "tee -a >> /Volumes/datanew/local/sage-6.8/logs/pkgs/bzip2-1.0.6.20140317.log" >> Found local metadata for bzip2-1.0.6.20140317 >> Attempting to download package bzip2-1.0.6.20140317 >> >>> Trying to download http:// >> www.sagemath.org/packages/upstream/bzip2/bzip2-1.0.6.20140317.tar.gz >> [Traceback (most recent call last): >> File "", line 35, in >> File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", >> line 240, in retrieve >> fp = self.open(url, data) >> File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", >> line 208, in open >> return getattr(self, name)(url) >> File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", >> line 359, in open_http >> return self.http_error(url, fp, errcode, errmsg, headers) >> File "/Volumes/datanew/local/sage-6.8/local/lib/python/urllib.py", >> line 376, in http_error >> return self.http_error_default(url, fp, errcode, errmsg, headers) >> File "", line 17, in http_error_default >> IOError: [Errno 404] Not Found: '// >> www.sagemath.org/packages/upstream/bzip2/bzip2-1.0.6.20140317.tar.gz' >> Error: failed to download package bzip2-1.0.6.20140317 >> make[2]: *** [/Volumes/datanew/local/sage-6.8/local/var/lib/sage/ >> installed/bzip2-1.0.6.20140317] Error 1 >> make[1]: *** [all] Error 2 >> >> real0m8.869s >> user0m1.960s >> sys0m2.425s >> *** >> Error building Sage. >> >> The following package(s) may have failed to build: >> >> package: bzip2-1.0.6.20140317 >> log file: /Volumes/datanew/local/sage-6.8/logs/pkgs/bzip2-1.0.6.20140317. >> log >> build directory: /Volumes/datanew/local/sage-6.8/local/var/tmp/sage/build >> /bzip2-1.0.6.20140317 >> >> >> Sure enough, if I try to wget that location ( >> https://www.sagemath.org/packages/upstream/bzip2/bzip2-1.0.6.20140317.tar.gz), >> >> I get a 404 error. >> >> Bill >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] updating sage-env LD_LIBRARY_PATH from spkg-install
Yes, but in the absence of an achieved utopia, is there something we can do here? I see that sage-env already has a lot of LD_LIBRARY_PATH hacking in it. Might be good to design a system for regularizing this, and moving all this hacking to that system. My solution has been to add Python code to detect this, and put out a warning to the user, telling them to add the required LD_LIBRARY_PATH setting to their sagerc file. Somewhat unsatisfactory. Bill On Monday, September 21, 2015 at 10:49:05 AM UTC-7, Jeroen Demeyer wrote: > > On 2015-09-21 19:23, Bill Janssen wrote: > > On OS X, The CasADi subsystem now installs its dynamic > > libraries in a subdirectory of JModelica, a subdirectory which then has > > to be put on the LD_LIBRARY_PATH the Python interpreter is run with > That is clearly an issue with the build system. Instead of requiring > Sage to change sage-env, it would be better to report this problem > upstream. Libraries should be installed in the standard places, such > that no special LD_LIBRARY_PATH hacks are needed. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] updating sage-env LD_LIBRARY_PATH from spkg-install
I'm updating an old-style JModelica spkg to version 1.16, which just came out. On OS X, The CasADi subsystem now installs its dynamic libraries in a subdirectory of JModelica, a subdirectory which then has to be put on the LD_LIBRARY_PATH the Python interpreter is run with, as CasADi is packaged as a Python extension. There seems to be no standardized way of hacking the LD_LIBRARY_PATH to include directories required by a new Python extension. Am I missing something? Is there a better way to do this than adding a sed script to hack sage-env? Bill -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] adventures with cdefs.h on OS X
Thought I'd share this in case anyone else blundered in the same way I just did... I installed 6.8 on an OS X Mavericks (10.9) system on which the "xcode-select --install" command had not been run. I ran "sage -upgrade" to upgrade it. I then tried to install a custom spkg, which failed in the configure step. To fix it, I tried running xcode-select --install, which had no effect. Turns out, this was because the Sage environment sets CPATH to an internal "include" directory, which when I looked at it, contained a "sys" subdirectory with an empty "cdefs.h" file in it. Not sure how it got there, but I'm guessing it's a result of doing the upgrade without having first run xcode-select. Once I deleted the "sys" subdirectory from the Sage internal "include" directory, I was able to install. Bill -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Problem building Sage after upgrading OS X 10.6.8 -> 10.9.1
I've got this problem right now, with Sage 6.8, on 10.9. And I've run xcode-select --install from a terminal; it just outputs the line "xcode-select: note: install requested for command line developer tools" (which are already installed). Help! Bill On Wednesday, February 5, 2014 at 6:32:23 PM UTC-8, John H Palmieri wrote: > > > > On Wednesday, February 5, 2014 4:33:58 PM UTC-8, David Roe wrote: >> >> I recently upgraded OS X and now run into trouble building Sage. XCode >> displays the version number as Version 5.0.2 (5A3005). >> > > Maybe see http://trac.sagemath.org/ticket/15783? That is, after upgrading > Xcode, you need to type > >xcode-select --install > > from a Terminal. Or have you done that already? > > John > > > >> >> When I try "make build" in my existing Sage (built before the upgrade), I >> get the following error: >> >> checking for C compiler default output file name... >> configure: error: C compiler cannot create executables >> >> (log available at http://pastebin.com/WQ5ssXVi) >> I checked my C compiler: gcc -v returns >> >> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr >> --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1 >> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) >> Target: x86_64-apple-darwin13.0.0 >> Thread model: posix >> >> and it successfully builds a hello_world.c. So I decided to try building >> from scratch, using a fresh sage-6.1 tarball. It errored with >> >> sed: /usr/include/sys/cdefs.h: No such file or directory >> >> (log available at http://pastebin.com/G9Ajqs4n) >> After running "sudo ln -s >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include >> >> /usr/include/" the build proceeded, with lots of warnings of the form >> >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/5.0/include/stddef.h:84:24: >> >> note: expanded from macro 'offsetof' >> #define offsetof(t, d) __builtin_offsetof(t, d) >>^ >> In file included from ../../src/gcc/graphite-scop-detection.c:25: >> In file included from ../../src/gcc/tree-flow.h:27: >> In file included from ../../src/gcc/basic-block.h:26: >> In file included from ../../src/gcc/function.h:27: >> ../../src/gcc/vecprim.h:29:1: warning: using extended field designator is >> an extension [-Wextended-offsetof] >> DEF_VEC_ALLOC_I(uchar,gc); >> ^ >> ../../src/gcc/vec.h:572:34: note: expanded from macro 'DEF_VEC_ALLOC_I' >> DEF_VEC_ALLOC_FUNC_I(T,A) >> \ >> >> ^ >> ../../src/gcc/vec.h:1274:21: note: expanded from macro '\ >> DEF_VEC_NONALLOC_FUNCS_I' >> (*vec_, alloc_, offsetof (VEC(T,A),base.vec), >> \ >> ^ >> >> and some suspicious lines that looked like >> >> /usr/bin/ranlib: file: libgcc_eh.a(unwind-sjlj.o) has no symbols >> /usr/bin/ranlib: file: ../.././gcc/libgcc.a(_trampoline.o) has no symbols >> >> Eventually it failed as before, with >> >> checking for C compiler default output file name... >> configure: error: in >> `/Users/roed/sage/sage6/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/x86_64-apple-darwin13.0.0/libgomp': >> configure: error: C compiler cannot create executables >> See `config.log' for more details. >> make[5]: *** [configure-stage1-target-libgomp] Error 77 >> make[4]: *** [stage1-bubble] Error 2 >> make[3]: *** [all] Error 2 >> >> (log available at http://people.ucalgary.ca/~roed/gcc-4.7.3.p1.log, >> since it's too big for pastebin) >> >> Something appears to be screwed up with my development environment, but >> I'm not sure what. Any ideas? >> David >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Problem building Sage after upgrading OS X 10.6.8 -> 10.9.1
I take it back. Apparently installing them from the Xcode app gives you the compilers, etc, but not the header files. Using xcode-select --install seems to yield both. Bill On Tuesday, September 15, 2015 at 4:50:47 PM UTC-7, Bill Janssen wrote: > > I've got this problem right now, with Sage 6.8, on 10.9. And I've run > xcode-select --install from a terminal; it just outputs the line > "xcode-select: note: install requested for command line developer tools" > (which are already installed). > > Help! > > Bill > > On Wednesday, February 5, 2014 at 6:32:23 PM UTC-8, John H Palmieri wrote: >> >> >> >> On Wednesday, February 5, 2014 4:33:58 PM UTC-8, David Roe wrote: >>> >>> I recently upgraded OS X and now run into trouble building Sage. XCode >>> displays the version number as Version 5.0.2 (5A3005). >>> >> >> Maybe see http://trac.sagemath.org/ticket/15783? That is, after >> upgrading Xcode, you need to type >> >>xcode-select --install >> >> from a Terminal. Or have you done that already? >> >> John >> >> >> >>> >>> When I try "make build" in my existing Sage (built before the upgrade), >>> I get the following error: >>> >>> checking for C compiler default output file name... >>> configure: error: C compiler cannot create executables >>> >>> (log available at http://pastebin.com/WQ5ssXVi) >>> I checked my C compiler: gcc -v returns >>> >>> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr >>> --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1 >>> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) >>> Target: x86_64-apple-darwin13.0.0 >>> Thread model: posix >>> >>> and it successfully builds a hello_world.c. So I decided to try >>> building from scratch, using a fresh sage-6.1 tarball. It errored with >>> >>> sed: /usr/include/sys/cdefs.h: No such file or directory >>> >>> (log available at http://pastebin.com/G9Ajqs4n) >>> After running "sudo ln -s >>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include >>> >>> /usr/include/" the build proceeded, with lots of warnings of the form >>> >>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/5.0/include/stddef.h:84:24: >>> >>> note: expanded from macro 'offsetof' >>> #define offsetof(t, d) __builtin_offsetof(t, d) >>>^ >>> In file included from ../../src/gcc/graphite-scop-detection.c:25: >>> In file included from ../../src/gcc/tree-flow.h:27: >>> In file included from ../../src/gcc/basic-block.h:26: >>> In file included from ../../src/gcc/function.h:27: >>> ../../src/gcc/vecprim.h:29:1: warning: using extended field designator >>> is an extension [-Wextended-offsetof] >>> DEF_VEC_ALLOC_I(uchar,gc); >>> ^ >>> ../../src/gcc/vec.h:572:34: note: expanded from macro 'DEF_VEC_ALLOC_I' >>> DEF_VEC_ALLOC_FUNC_I(T,A) >>> \ >>> >>> ^ >>> ../../src/gcc/vec.h:1274:21: note: expanded from macro '\ >>> DEF_VEC_NONALLOC_FUNCS_I' >>> (*vec_, alloc_, offsetof >>> (VEC(T,A),base.vec),\ >>> ^ >>> >>> and some suspicious lines that looked like >>> >>> /usr/bin/ranlib: file: libgcc_eh.a(unwind-sjlj.o) has no symbols >>> /usr/bin/ranlib: file: ../.././gcc/libgcc.a(_trampoline.o) has no symbols >>> >>> Eventually it failed as before, with >>> >>> checking for C compiler default output file name... >>> configure: error: in >>> `/Users/roed/sage/sage6/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/x86_64-apple-darwin13.0.0/libgomp': >>> configure: error: C compiler cannot create executables >>> See `config.log' for more details. >>> make[5]: *** [configure-stage1-target-libgomp] Error 77 >>> make[4]: *** [stage1-bubble] Error 2 >>> make[3]: *** [all] Error 2 >>> >>> (log available at http://people.ucalgary.ca/~roed/gcc-4.7.3.p1.log, >>> since it's too big for pastebin) >>> >>> Something appears to be screwed up with my development environment, but >>> I'm not sure what. Any ideas? >>> David >>> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: UTF-8 and old terminals (new startup banner)
It's hard to sufficiently emphasize how ugly this looks in an Emacs shell buffer. I use the Inconsolata font with emacs, and it doesn't have those characters (the dashes and corner characters), so Emacs goes to a different fixed-width font for them, and that font has a different width, so the horizontal dashes are about twice the width of the text lines! I just turn it off by setting SAGE_BANNER to no. Bill On Friday, August 2, 2013 at 6:49:21 PM UTC-7, Volker Braun wrote: Its always hard to please everybody, We haven't really reached any consensus, nor does it sound like there is much to be gained by further discussion. So i'll set the ticket to positive review and leave you with Lichtenberg's aphorism: Ich weiss nicht, ob es besser wird, wenn es anders wird. Aber es muss anders werden, wenn es besser werden soll. (I don't know if it'll become better if it is changed. But it must be changed to become better.) -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] broken prompts in Emacs shell-mode
Still better is this, in ~/.sage/ipython-0.12/profile_sage/ipython_config.py: o = get_config() try: import curses curses.initscr() except: print can't initscr with curses pass else: try: if not curses.has_colors(): o.SageInteractiveShell.colors = NoColor finally: curses.endwin() On Wednesday, September 25, 2013 7:52:54 AM UTC-7, Bill Janssen wrote: Better would be this: c = get_config() try: import curses curses.initscr() except: pass else: try: if not curses.has_colors(): c.InteractiveShell.colors = NoColor finally: curses.endwin() This could also go into the regular Sage ipython startup script -- it's only effective if the terminal does not support colors. Bill -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: How can an spkg extend the interactive Sage environment?
On Tuesday, October 1, 2013 1:39:42 AM UTC-7, Volker Braun wrote: Just patch the JModelica module to set the path on import. Requiring global variables to point to your home dir is already so much bad practice that I don't want to see the source code. Well, I hope you won't have to look at it. Though the practice is quite common in the Modelica tool world. In general, I think lots of software solutions built by engineers rather than software people tend to do this, because they either don't understand or don't care about the various alternatives. Thanks, I'll do as you suggest. -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: How can an spkg extend the interactive Sage environment?
On Monday, September 30, 2013 11:50:36 PM UTC-7, Felix Salfelder wrote: On Mon, Sep 30, 2013 at 03:51:15PM -0700, Bill Janssen wrote: However, I've also got to make sure that the environment variable JMODELICA_HOME is set. Is there some way for an spkg to hook into sage-env and extend it? Hello? Anyone? that's pretty easy to do. actually, unhardwiring the parts of sage-env solves a lot more problems. it is #15087, and it does no longer merge cleanly, because of some other changes I dont know about. have fun. felix Thanks, Felix. -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: How can an spkg extend the interactive Sage environment?
Hello? Anyone?
On Monday, September 23, 2013 2:29:00 PM UTC-7, Bill Janssen wrote:
I'm building JModelica for Sage. It installs into its own little private
directory (I'm using ${SAGE_LOCAL}/JModelica-1.11), including its Python
code. When I fire up the interactive Sage prompt, I'd like it to be able
to locate the JModelica Python modules. To do that, I need to integrate
JModelica's Python installation with Sage's.
What's the correct procedure here? I thought I'd just symlink the
directories in ${SAGE_LOCAL}/JModelica-1.11/Python/ to
${SAGE_LOCAL}/lib/python2.7/site-packages/.
However, I've also got to make sure that the environment variable
JMODELICA_HOME is set. Is there some way for an spkg to hook into sage-env
and extend it?
Bill
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] sage-env always sets LDFLAGS, which clobbers Numpy's distutils Fortran compiler support
On Tuesday, September 24, 2013 11:51:37 AM UTC-7, Felix Salfelder wrote: There's a difference between an empty value and not defined, after all. there *is* a difference. in my experience there's nothing useful about it. implicitly overriding (not appending!) flags from the environment is merely asking for trouble. So isn't what Sage is doing -- implicitly overriding a from-environment value of not set with a new value of empty -- merely asking for trouble, which is what I got with this package? But, yes, the root problem is that there's no standard for the use of LDFLAGS. I don't know with whom to file a bug report to fix that :-). Bill -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] broken prompts in Emacs shell-mode
Better would be this: c = get_config() try: import curses curses.initscr() except: pass else: try: if not curses.has_colors(): c.InteractiveShell.colors = NoColor finally: curses.endwin() This could also go into the regular Sage ipython startup script -- it's only effective if the terminal does not support colors. Bill -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] sage-env always sets LDFLAGS, which clobbers Numpy's distutils Fortran compiler support
Hmmm, but that would replicate the fairly complicated Python code that it already uses to determine the proper flags. For the moment, I've fixed it by doing an unset LDFLAGS in the spkg-install file, but I think it's still a Sage bug to export empty LDFLAGS if the user hasn't set them that way. There's a difference between an empty value and not defined, after all. Bill On Monday, September 23, 2013 11:19:43 PM UTC-7, Felix Salfelder wrote: On Mon, Sep 23, 2013 at 02:21:39PM -0700, Bill Janssen wrote: I was trying to compile the Python+Fortran Assimulo package on Sage (5.11) on OS X, and I couldn't figure out why the gfortran link step kept failing -- the correct linker flags for shared libraries weren't being used. Turns out that the fcompiler support in Numpy's distutils will *always* look at LDFLAGS and use them instead of the carefully determined platform-specific flags. And there's this code in sage-env: if [ $LDFLAGS = ]; then LDFLAGS= export LDFLAGS fi So the empty LDFLAGS setting was always clobbering the carefully determined platform-specific flags. Not sure this is a good thing... While it does not exactly make sense to export empty LDFLAGS in case they are empty already, this shouldn't affect the spkg. the correct place to figure out appropriate flags for the Assimulo build system is its spkg-install file/program (you may want to *append* global LDFLAGS, maybe...). regards felix -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] sage-env always sets LDFLAGS, which clobbers Numpy's distutils Fortran compiler support
I was trying to compile the Python+Fortran Assimulo package on Sage (5.11) on OS X, and I couldn't figure out why the gfortran link step kept failing -- the correct linker flags for shared libraries weren't being used. Turns out that the fcompiler support in Numpy's distutils will *always* look at LDFLAGS and use them instead of the carefully determined platform-specific flags. And there's this code in sage-env: if [ $LDFLAGS = ]; then LDFLAGS= export LDFLAGS fi So the empty LDFLAGS setting was always clobbering the carefully determined platform-specific flags. Not sure this is a good thing... Bill -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] How can an spkg extend the interactive Sage environment?
I'm building JModelica for Sage. It installs into its own little private
directory (I'm using ${SAGE_LOCAL}/JModelica-1.11), including its Python
code. When I fire up the interactive Sage prompt, I'd like it to be able
to locate the JModelica Python modules. To do that, I need to integrate
JModelica's Python installation with Sage's.
What's the correct procedure here? I thought I'd just symlink the
directories in ${SAGE_LOCAL}/JModelica-1.11/Python/ to
${SAGE_LOCAL}/lib/python2.7/site-packages/.
However, I've also got to make sure that the environment variable
JMODELICA_HOME is set. Is there some way for an spkg to hook into sage-env
and extend it?
Bill
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: Parsing XML in Sage
I have an spkg for lxml (required for JModelica) and I intend to make it available in the near future. Bill On Tuesday, September 17, 2013 4:45:22 AM UTC-7, Nathann Cohen wrote: Hell everybody ! We have in Sage an interface with ISGCI [1], and most of the code it contains amounts to parsing a xml file, i.e. the db it gives access to. The code is (very) ugly, and a friend of mine told me that I should use some Python library to objectify this XML file, so that we only need work with dictionaries (and not with the XML file) in the code. It looks like lxml would do the job, and there are others like gnosis or amara that seem to do the same kind of things. Did you ever use any of those, and would you think it a good idea to add them into Sage ? It would definitely simplify this code, at least.. :-) By the way, this interface is being patched by #14396, and it would be great if somebody was willing to give it a review... The db's author has been very kind with us, and the improvements I promised him are not available in Sage yet ^^; Have fun :-) Nathann [1] http://graphclasses.org/ -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] broken prompts in Emacs shell-mode
Same problem with straight ipython. Bill On Friday, September 20, 2013 11:12:37 AM UTC-7, William wrote: Hi, What happens if you run straight ipython? sage -ipython If the problem is the same, you could ask on the ipython list... (since sage's command line is ipython). William On Fri, Sep 20, 2013 at 10:54 AM, Bill Janssen bill.j...@gmail.comjavascript: wrote: In an Emacs shell, Sage seems to be ignoring the TERM setting (dumb) and sending ANSI escape sequences to the terminal around the sage: prompt. [pippin:~] wjanssen% printenv TERM dumb [pippin:~] wjanssen% /local/sage-5.11/sage ++ | Sage Version 5.11, Release Date: 2013-08-13| | Type notebook() for the browser-based notebook interface.| | Type help() for help.| ++ [0;34msage: [0m Is there a way to defeat this? Should I file a bug on this? Bill -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] broken prompts in Emacs shell-mode
Thanks, Nils. That worked. Use sage -ipython profile list to find out where your profile is (it wasn't using ~/.ipython/, it was using ~/.sage/ipython-0.12/), then put the following lines into ~/.sage/ipython-0.12/profile_default/ipython_config.py: c = get_config() try: import curses curses.initscr() except: pass else: if not curses.has_colors(): c.InteractiveShell.colors = NoColor finally: curses.endwin() One of the most irritating side-effects of pervasive readlinery is the need to do this over and over everywhere. Bill On Friday, September 20, 2013 11:22:57 AM UTC-7, Nils Bruin wrote: On Friday, September 20, 2013 11:12:37 AM UTC-7, William wrote: If the problem is the same, you could ask on the ipython list... (since sage's command line is ipython). William It is. I don't think IPython's prompt configuration looks at the environment TERM at all. It's fully configurable, though, so you can make it do that. Perhaps start with %config PromptManager and take it from there. -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] broken prompts in Emacs shell-mode
In an Emacs shell, Sage seems to be ignoring the TERM setting (dumb) and sending ANSI escape sequences to the terminal around the sage: prompt. [pippin:~] wjanssen% printenv TERM dumb [pippin:~] wjanssen% /local/sage-5.11/sage ++ | Sage Version 5.11, Release Date: 2013-08-13| | Type notebook() for the browser-based notebook interface.| | Type help() for help.| ++ [0;34msage: [0m Is there a way to defeat this? Should I file a bug on this? Bill -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: talk about sage -i and sage -f in the developer's guide?
On Nov 15, 6:47 pm, William Stein wst...@gmail.com wrote: On Tue, Nov 15, 2011 at 5:46 PM, BillJanssenbill.jans...@gmail.com wrote: One trivial thing you could do would be to build from source in /tmp/, then just move your install to your home directory. Sage supports moving complete installs. That's basically what I am doing. Still breaks because it's trying to do stuff in ~janssen/.sage/ as part of the build. Set the environment variable DOT_SAGE to something under /tmp/. Then it shouldn't touch ~janssen/.sage. That works, thanks! Bill -- 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
[sage-devel] Re: tentative PIL-1.1.7.p0.spkg
I've now placed a new version of pil-1.1.7.p0.spkg at
http://uplib.parc.com/misc/pil-1.1.7.p0.spkg. This contains the .hg
files, but I'm still not sure I've got that correct.
By the way, spkg-check still runs on OS X, but not on Ubuntu. I've
tested it with Sage 4.7.2 on both; seems to build and work fine.
If the test suite runs, you'll see extra output at the end of the
build:
Running the test suite.
testing formats...
PNG: L (512, 512) {}
JPEG: L (512, 512) {'jfif_version': (1, 1), 'jfif': 257, 'jfif_unit':
0, 'jfif_density': (1, 1)}
TIFF: L (512, 512) {'resolution': (1, 1), 'compression': 'raw'}
BMP: L (512, 512) {'compression': 0}
test resize...
after resize: L (50, 50)
test convert...
RGB (512, 512) = RGB (512, 512)
RGBA (512, 512) = RGBA (512, 512)
1 (512, 512)
1 (512, 512)
L (512, 512) = L (512, 512)
P (512, 512) = L (512, 512)
Bill
On Nov 22, 3:59 pm, John H Palmieri jhpalmier...@gmail.com wrote:
On Tuesday, November 22, 2011 3:45:28 PM UTC-8, Bill Janssen wrote:
On Nov 22, 12:53 pm, John H Palmieri jhpalm...@gmail.com wrote:
So pil-1.1.6.p5 *is* the old one.
pil-1.1.6.p4 is the old one.
Remove the src directory from that
one, replacing it with the new source. Modify any patches as necessary,
along with the spkg-install, spkg-check, and SPKG.txt files, as I said in
my previous message. Commit your changes using hg commit (or sage
--hg
commit).
How do I change the name? Just hg rename? Won't that delete
pil-1.1.6.p4? What if someone wants 1.1.6 instead of 1.1.7?
You just change the name of the parent directory:
$ mv pil-1.1.6.p4 pil-1.1.7.p0
The Mercurial repository is contained in this directory, but it doesn't
actually care what the name of the directory is.
As far as 1.1.6 vs. 1.1.7, the new version should only be merged it if
represents an upgrade and works on all platforms where the old one worked,
so most people should be happy with 1.1.7. If someone really wants the old
version, they can download an old version of Sage and get it from there.
We don't keep old versions of spkgs around, as far as I know.
--
John
--
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
[sage-devel] CPPFLAGS not preserved by sage-env
I'm guessing that CPPFLAGS should also be preserved by sage-env. Similar to CXXFLAGS and LDFLAGS, it's typically used to pass include options to the C preprocessor. -- 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
[sage-devel] Re: talk on Sage that I gave today
Nice graphic in there, William. Page 8 in the PDF. Just what I need for a talk this afternoon. Is it available as an image somwhere? Thanks. Bill On Nov 20, 12:05 am, William Stein wst...@gmail.com wrote: On Sat, Nov 19, 2011 at 11:50 PM, Thierry Dumont tdum...@math.univ-lyon1.fr wrote: Le 20/11/2011 08:48, William Stein a écrit : Hi, I gave a general audience talk today at the Combinatorial Potlatch here at Seattle University. My slides, the worksheet, and a clear recording of the audio of the talk are here, in case you're interested: http://wstein.org/talks/2011-potlatch/ This is similar to the talk I gave in Budapest, but this talk has a long discussion with the audience in the middle... William Hi, the pdf link does not work. Fixed. -- 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 -- William Stein Professor of Mathematics University of Washingtonhttp://wstein.org -- 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
[sage-devel] Re: MIME type for .spkg files?
The MIME registration is a bit screwed up in this respect. tar might be OK as a document format (though I believe no one has registered a MIME type for it), but bzip2 is more of what they think of as a content-transfer-encoding. I've argued in the past to the IETF that they should define additional content-transfer-encodings for gzip and zip and bzip2, but they haven't, because it doesn't really come up in the email application domain. I'd suggest registering a real MIME type for it, something like application/vnd.sagemath-spkg. That would allow servers and browsers to agree on what they're passing around. It would also handle the case where it's maybe bzip2 one time and maybe tar the next time. Same for .sws, if that isn't already registered. Bill On Nov 18, 12:12 am, Jeroen Demeyer jdeme...@cage.ugent.be wrote: On 2011-11-17 22:33, Bill Janssen wrote: Is there a MIME type for .spkg files? I guess not, but spkg files are simply bzip2'ed tar files, so if there is a MIME type for that, you should probably use that. -- 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
[sage-devel] Re: tentative PIL-1.1.7.p0.spkg
OK, I'll look at that this long weekend. Bill On Nov 17, 2:07 pm, William Stein wst...@gmail.com wrote: On Thu, Nov 17, 2011 at 1:49 PM, Bill Janssen bill.jans...@gmail.com wrote: Some issues with this spkg: - The mercurial repository is completely missing. Yes, it's not a patch to the Sage sources, so there's no Mercurial stuff as there would be if it were. Each spkg has its own Mercurial repository. Look at another spkg. - There are lots of backup files around (SPKG.txt~, etc.). I've put up a new version which should fix this. - You shouldn't build libjpeg in /tmp/..., but probably in a subdirectory of SAGE_ROOT/spkg/build/pil- You also shouldn't delete this temporary directory: the sage-spkg script will clean up spkg/build/pil-... automatically unless requested not to. (What if your $TEMPDIR already exists? What if there is an error running spkg-check and someone wants to look at the build directories?) OK, I'll try that. Thanks! -- 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 athttp://groups.google.com/group/sage-devel URL:http://www.sagemath.org -- William Stein Professor of Mathematics University of Washingtonhttp://wstein.org -- 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
[sage-devel] Re: tentative PIL-1.1.7.p0.spkg
On Nov 17, 5:07 pm, kcrisman kcris...@gmail.com wrote: On Nov 17, 5:10 pm, Bill Janssen bill.jans...@gmail.com wrote: OK, the libjpeg now builds in place. I see that on my Ubuntu box, the spkg-check file isn't being run automatically. Any ideas as to why that might be? Did you set SAGE_CHECK=yes ? That is the flag that sets that to run. Otherwise Sage would always fail, because the Python spkg-check always fails... I did not. Neither on my Mac (where spkg-check runs) or on my Ubuntu box (where it doesn't run). I just tried setting it on my Ubuntu machine, then running sage -f pil-1.1.7.p0.spkg again. Still doesn't run spkg-check there. Is there a verbose flag of some sort I could set to see what's going on? Bill Thanks for the work on this. My computer has never passed plot/plot3d/ base.pyx because of not having libjpeg, I guess - at least it says the _imaging_C or whatever extension wasn't built, and my understanding is that that is from PIL (?). - kcrisman -- 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
[sage-devel] Re: talk on Sage that I gave today
On Nov 22, 9:26 am, Bill Janssen bill.jans...@gmail.com wrote: Nice graphic in there, William. Page 8 in the PDF. Just what I need for a talk this afternoon. Is it available as an image somwhere? Ah, got it. Pulled it out of the worksheet. Bill -- 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
[sage-devel] Re: MIME type for .spkg files?
I'd suggest registering a real MIME type for it, something like application/vnd.sagemath-spkg. See http://www.iana.org/cgi-bin/mediatypes.pl. Bill -- 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
[sage-devel] Re: tentative PIL-1.1.7.p0.spkg
You should build your new spkg by starting with the old one Except that the old one doesn't exist -- this is pil-1.1.7.p0, not pil-1.1.6.p5. Still not sure how to go about this -- an example (perhaps it's in the docs) would be helpful. -- 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
[sage-devel] Re: tentative PIL-1.1.7.p0.spkg
On Nov 22, 12:53 pm, John H Palmieri jhpalmier...@gmail.com wrote: So pil-1.1.6.p5 *is* the old one. pil-1.1.6.p4 is the old one. Remove the src directory from that one, replacing it with the new source. Modify any patches as necessary, along with the spkg-install, spkg-check, and SPKG.txt files, as I said in my previous message. Commit your changes using hg commit (or sage --hg commit). How do I change the name? Just hg rename? Won't that delete pil-1.1.6.p4? What if someone wants 1.1.6 instead of 1.1.7? Bill See, for example, http://sagemath.org/doc/developer/patching_spkgs.html#bumping-up-an-s -- John -- 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
[sage-devel] tentative PIL-1.1.7.p0.spkg
I've put up my first try at a PIL 1.1.7 spkg at http://uplib.parc.com/ misc/pil-1.1.7.p0.spkg. Please tell me what I did wrong :-). I've tried this on OS X Leopard, and on Ubuntu64 10.04. This version includes a statically linked libjpeg, *doesn't* rummage around on the local machine trying to find additional libraries in / usr/local or (on Macs) /opt and /sw, and runs both the PIL test suite and a Sage test suite. Bill -- 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
[sage-devel] MIME type for .spkg files?
Is there a MIME type for .spkg files? -- 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
[sage-devel] Re: tentative PIL-1.1.7.p0.spkg
Some issues with this spkg: - The mercurial repository is completely missing. Yes, it's not a patch to the Sage sources, so there's no Mercurial stuff as there would be if it were. - There are lots of backup files around (SPKG.txt~, etc.). I've put up a new version which should fix this. - You shouldn't build libjpeg in /tmp/..., but probably in a subdirectory of SAGE_ROOT/spkg/build/pil- You also shouldn't delete this temporary directory: the sage-spkg script will clean up spkg/build/pil-... automatically unless requested not to. (What if your $TEMPDIR already exists? What if there is an error running spkg-check and someone wants to look at the build directories?) OK, I'll try that. Thanks! -- 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
[sage-devel] Re: tentative PIL-1.1.7.p0.spkg
OK, the libjpeg now builds in place. I see that on my Ubuntu box, the spkg-check file isn't being run automatically. Any ideas as to why that might be? Bill On Nov 17, 1:49 pm, Bill Janssen bill.jans...@gmail.com wrote: - You shouldn't build libjpeg in /tmp/..., but probably in a subdirectory of SAGE_ROOT/spkg/build/pil- You also shouldn't delete this temporary directory: the sage-spkg script will clean up spkg/build/pil-... automatically unless requested not to. (What if your $TEMPDIR already exists? What if there is an error running spkg-check and someone wants to look at the build directories?) OK, I'll try that. Thanks! -- 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
[sage-devel] Re: integrating spkg-check and spkg-install?
Mainly, because there's no current reason to install libjpeg.dylib. It's just a potentional source of confusion and breakage for the future. I'd feel differently if there were other uses of it. For instance, if someone were to wrap Dan Bloomberg's excellent Leptonica library at http://www.leptonica.org/. In that case, there might be some reason to have both PIL and Leptonica use the same libjpeg. Bill On Nov 15, 11:58 pm, William Stein wst...@gmail.com wrote: On Tue, Nov 15, 2011 at 10:52 PM, Bill Janssen bill.jans...@gmail.com wrote: Again, installing libjpeg.dylib and/or libpng.dylib into $SAGE_LOCAL/ lib has bad side effects on OS X, due to the use of DYLD_LIBRARY_PATH in the Sage framework overall. So, maybe make it an optional spkg, but having it as a required or standard spkg would be bad. We already install libpng.dylib standard in all copies of Sage on OS X. There were issues, but they got sorted out a while ago. -- William The reason this works on OS X is that the Sage version of the library is called libpng12.dylib, while the system version is libpng.dylib. This numbering is now built-in to libpng, but not to the jpeg libraries, so the same process won't protect you. Basically, you can't safely override the library names you find in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ Frameworks/ImageIO.framework/Resources/, which are libjp2.dylib, libjpeg.dylib, libopenexr.dylib, libpng.dylib, libradience.dylib, libtiff.dylib, and libgif.dylib. By override, I mean have libraries with the same name (differing only in case) prior to these libraries on the DYLD_LIBRARY_PATH. The version of libpng in /System is 1.4.3 on both my Leopard system and my Lion system. The version in sage-4.7.2 is 1.2.35. But the library name is different, so there's no problem. If all that is the case, why don't you name the jpeg library libjpegsage.dylib or something, and slightly change the PIL build script. -- 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 athttp://groups.google.com/group/sage-devel URL:http://www.sagemath.org -- William Stein Professor of Mathematics University of Washingtonhttp://wstein.org -- 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
[sage-devel] talk about sage -i and sage -f in the developer's guide?
It would be nice if the developer's guide talked about using sage -i and sage -f to test new spkg's. In the section about building spkg's, perhaps. -- 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
[sage-devel] example of sage-check file?
Can someone please point me to an example of a sage-check file? I don't see any explanation in the developer docs. -- 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
[sage-devel] Re: example of sage-check file?
Sorry, I mean spkg-check. Bill On Nov 15, 10:40 am, Bill Janssen bill.jans...@gmail.com wrote: Can someone please point me to an example of a sage-check file? I don't see any explanation in the developer docs. -- 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
[sage-devel] integrating spkg-check and spkg-install?
I'm building a new spkg for PIL 1.1.7. I'd like to build PIL, then run its test suite, then if that passes, install it. Should I just do all of that in spkg-install, or should I run the test suite in spkg-check? If I install it before I test it, that means that broken code could overwrite working code, so I'm inclined to do everything in spkg-install, rather than using spkg- check. Or is there some rollback mechanism if spkg-check fails? Advice? -- 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
[sage-devel] why unpack the source packages?
I'm a bit unclear as to why third-party source packages are unpacked in an spkg? Since the patching protocol is very strict, would it make sense for me to include Imaging-1.1.7.tar in the src directory of the spkg, instead of unpacking it into raw files? -- 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
[sage-devel] Re: integrating spkg-check and spkg-install?
Georg, I'll fix those problems (unwanted binaries in $SAGE_LOCAL/bin/, and linking against unintended libraries), in my new spkg. Little-known fact about PIL: it doesn't actually use libtiff -- the checks are in there for an experimental module which doesn't ship with the distribution. I've decided to run the PIL selftest.py after building PIL, but before installing it. I'll write some other tests to be run by spkg-check which will specifically test the integration with Sage. Bill On Nov 15, 12:29 pm, Georg S. Weber georgswe...@googlemail.com wrote: On 15 Nov., 20:03, Bill Janssen bill.jans...@gmail.com wrote: I'm building a new spkg for PIL 1.1.7. I'd like to build PIL, then run its test suite, then if that passes, install it. Should I just do all of that in spkg-install, or should I run the test suite in spkg-check? If I install it before I test it, that means that broken code could overwrite working code, so I'm inclined to do everything in spkg-install, rather than using spkg- check. Or is there some rollback mechanism if spkg-check fails? Advice? Unfortunately, the current Sage (distribution) build system has no rollback mechanism. I advise to create a new directory test somewhere, and use a throw- away/test installation of Sage there specifically for fiddling with a new spkg. I always have half a dozen full Sage installations around. PIL is/was especially unsuited for integration in Sage. On the one hand, it installs quite some files e.g. under $SAGE_LOCAL/bin/ which no Sage user needs (or even knows of, I guess), thus polluting the tree without having cleanup mechansims at hand. On the other hand it tries greedily to link against libraries it finds somewhere (by some hand-made custom logic implemented in Python ...) on the system it gets installed. Which is bad for Sage binary distributions (bdists) made out of such an installation, if on the target system where the bdist will eventually be installed, those libraries do not exist (libtiff comes to my mind). IIRC, we had to introduce some extra SAGE_BDIST (or so) environment variable especially for the PIL case, in order not to have to uninstall each and every time those libraries from the systems, where official Sage bdists are regularly generated. Good luck for your new spkg! (Is there a trac ticket for it yet?) Cheers, Georg -- 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
[sage-devel] Re: why unpack the source packages?
Fine with me. But if the src directory is allowed to be a modified version of upstream, why not just integrate the Sage-specific patches directly into the sources, too? Bill On Nov 15, 11:29 am, William Stein wst...@gmail.com wrote: On Tue, Nov 15, 2011 at 11:13 AM, Bill Janssen bill.jans...@gmail.com wrote: I'm a bit unclear as to why third-party source packages are unpacked in an spkg? Since the patching protocol is very strict, would it make sense for me to include Imaging-1.1.7.tar in the src directory of the spkg, instead of unpacking it into raw files? Please don't do that, if for no other reason than that there are over 100 packages that don't do that, and over 100 people who are used to having src by the extracted upstream source. We could have included a tarball version of the src directory in spkg's, but that just slows down development (one has to go through an extra step to look at it every time) and complicates things, and it doesn't actually prove anything about the contents actually being correct. Also, often upstream tarballs are full of crap (e.g., windows binaries, pdf's that are huge and useless, etc.) that have to be deleted. -- William -- William Stein Professor of Mathematics University of Washingtonhttp://wstein.org -- 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
[sage-devel] Re: integrating spkg-check and spkg-install?
On Nov 15, 1:02 pm, Georg S. Weber georgswe...@googlemail.com wrote: Some people buidling Sage from source do *want* a libjpeg on their system to be taken into accont by their PIL in Sage! Really? Do you have user studies or other evidence of that I could look at on that? It's surprising to me; I'd think that one build of libjpeg would be much like any other build. -- 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
[sage-devel] Re: talk about sage -i and sage -f in the developer's guide?
On Nov 15, 1:29 pm, Georg S. Weber georgswe...@googlemail.com wrote: On 15 Nov., 18:51, Bill Janssen bill.jans...@gmail.com wrote: It would be nice if the developer's guide talked about using sage -i and sage -f to test new spkg's. In the section about building spkg's, perhaps. Yes. Two or three sentences, maybe? Something like that. I think you could better formulate what you (it seems) have sought in vain there, than one of the veterans. Yep. Opening up a trac ticket (and eventually posting there a respective doc patch) is the easier part. Once I figure out how to build from source (see http://groups.google.com/group/sage-support/browse_thread/thread/5c35b0550f0dd04) I can try to figure out how to make a doc patch. -- 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
[sage-devel] Re: why unpack the source packages?
The only real advantages of keeping the upstream sources packaged is that (1) you can know what's in them, check md5sums, etc., and (2) there's less chance of introducing hard-to-find errors by fat- fingering a particular unpacked source file. But I'm happy to unpack, too. On Nov 15, 2:01 pm, Maarten Derickx m.derickx.stud...@gmail.com wrote: Hi, there is another reason: tar is not necessarily equal to tar. The Sage build scripts try to use only the most generic options, and provenly work on the supported number of systems. If you provide some file tarred upstream, then this might not be out-of-the-box readable by the system tar on some of the supported platforms (think of e.g. Solaris). Sage could bring its own tar with it to circumvent this problem, but up to now, there was no real need for that. This is not a valid argument since all spkg files are already tarred and gnu tar is requiered on solaris anyway. Just to quote from $SAGE_ROOT/spkg/base/prereq-0.9-install if [ `uname` = SunOS ] ; then if [ -z `tar --version 21 | grep GNU` ] ; then echo echo ERROR ** echo ERROR ** echo You MUST also use the GNU version of tar, as some parts echo of the Sage source code are compressed tar files, which echo were compressed with GNU tar. GNU tar does not produce echo POSIX compliant tar files unless called with the --posix echo option, so can not always be extracted with Sun's tar. Altough I do agree that the src directory should not be tarred. Mainly for the reasons by William. And since the spkg are tarred already there is also no benefit in size. -- 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
[sage-devel] Re: talk about sage -i and sage -f in the developer's guide?
One trivial thing you could do would be to build from source in /tmp/, then just move your install to your home directory. Sage supports moving complete installs. That's basically what I am doing. Still breaks because it's trying to do stuff in ~janssen/.sage/ as part of the build. I can build with a local account, though, instead of my network account. Anyone tried to build this with MinGW (Minimal GNU for Windows) yet? -- 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
[sage-devel] Re: integrating spkg-check and spkg-install?
On Nov 15, 12:29 pm, Georg S. Weber georgswe...@googlemail.com wrote: it installs quite some files e.g. under $SAGE_LOCAL/bin/ which no Sage user needs (or even knows of, I guess), thus polluting the tree without having cleanup mechansims at hand. I've just reviewed the scripts in Imaging-1.1.7/Scripts/, and I see no good reason to install any of them. They don't have tests, and the ones that aren't obsolete have better alternatives elsewhere on any system. Bill -- 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
[sage-devel] Re: integrating spkg-check and spkg-install?
Are there any spkgs elsewhere in Sage which require libjpeg? If so, what version of it? I know that scipy has an imread function; anyone know what does it do for JPEG? Again, installing libjpeg.dylib and/or libpng.dylib into $SAGE_LOCAL/ lib has bad side effects on OS X, due to the use of DYLD_LIBRARY_PATH in the Sage framework overall. So, maybe make it an optional spkg, but having it as a required or standard spkg would be bad. Bill On Nov 15, 6:49 pm, William Stein wst...@gmail.com wrote: On Tue, Nov 15, 2011 at 6:01 PM, kcrisman kcris...@gmail.com wrote: On Nov 15, 5:34 pm, William Stein wst...@gmail.com wrote: On Tue, Nov 15, 2011 at 2:10 PM, Bill Janssen bill.jans...@gmail.com wrote: On Nov 15, 1:02 pm, Georg S. Weber georgswe...@googlemail.com wrote: Some people buidling Sage from source do *want* a libjpeg on their system to be taken into accont by their PIL in Sage! Really? Do you have user studies or other evidence of that I could look at on that? It's surprising to me; I'd think that one build of libjpeg would be much like any other build. Georg surely just meant that with the current setup where libjpeg is not included in Sage, they would want PIL to be able t use libjpeg if they have it installed on their system. Of course if you include libjpeg in Sage, then this argument vanishes. So are you not-so-subtly hinting thathttp://trac.sagemath.org/sage_trac/ticket/7344 should be a standard spkg? Just checking. Yes. A standard function in matlab is imread [1], which can read in jpg images. I'm sure Mathematica can too. Given the Sage mission statement, which is to be a viable alternative to Matlab, Mathematica, etc., it would make a lot of sense to include jpeg support standard in Sage. [1]http://www.mathworks.com/help/techdoc/ref/imread.html -- 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 athttp://groups.google.com/group/sage-devel URL:http://www.sagemath.org -- William Stein Professor of Mathematics University of Washingtonhttp://wstein.org -- 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
[sage-devel] Re: integrating spkg-check and spkg-install?
On Nov 15, 7:01 pm, Bill Janssen bill.jans...@gmail.com wrote: Are there any spkgs elsewhere in Sage which require libjpeg? If so, what version of it? I know that scipy has an imread function; anyone know what does it do for JPEG? I looked it up; it uses PIL. -- 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
[sage-devel] question about patch level in spkg file names
I'm a bit unclear on what the value of patchlevel should be in my new PIL package. I carry over the two patches from pil-1.1.6.p4, but it's a new PIL version, so I'm thinking pil-1.1.7.p0. Would that be correct? -- 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
[sage-devel] Re: integrating spkg-check and spkg-install?
Again, installing libjpeg.dylib and/or libpng.dylib into $SAGE_LOCAL/ lib has bad side effects on OS X, due to the use of DYLD_LIBRARY_PATH in the Sage framework overall. So, maybe make it an optional spkg, but having it as a required or standard spkg would be bad. We already install libpng.dylib standard in all copies of Sage on OS X. There were issues, but they got sorted out a while ago. -- William The reason this works on OS X is that the Sage version of the library is called libpng12.dylib, while the system version is libpng.dylib. This numbering is now built-in to libpng, but not to the jpeg libraries, so the same process won't protect you. Basically, you can't safely override the library names you find in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ Frameworks/ImageIO.framework/Resources/, which are libjp2.dylib, libjpeg.dylib, libopenexr.dylib, libpng.dylib, libradience.dylib, libtiff.dylib, and libgif.dylib. By override, I mean have libraries with the same name (differing only in case) prior to these libraries on the DYLD_LIBRARY_PATH. The version of libpng in /System is 1.4.3 on both my Leopard system and my Lion system. The version in sage-4.7.2 is 1.2.35. But the library name is different, so there's no problem. -- 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
