New packages are up at #7344 and #7345 (http://trac.sagemath.org/sage_trac/ticket/7344 and http://trac.sagemath.org/sage_trac/ticket/7345) for review that should hopefully work for all platforms.
On Tue, Aug 3, 2010 at 2:31 AM, Tim Joseph Dumol <t...@timdumol.com> wrote: > Hi, > > SAGE_BINARY_BUILD was introduced as a compromise when it was decided > that libjpeg and libtiff were to be introduced first as optional > packages, since PIL is a standard package. Without SAGE_BINARY_BUILD > set, binary distributions have PIL link with libjpeg and libtiff as > shared libraries, which may not exist in client machines. (c.f. > http://groups.google.com/group/sage-devel/msg/6ea0a0e0a0a2a71a and > http://trac.sagemath.org/sage_trac/ticket/7273) > > The libjpeg and libtiff packages are at > http://trac.sagemath.org/sage_trac/ticket/7344 and > http://trac.sagemath.org/sage_trac/ticket/7345. However, they have > some issues that I cannot attend to right now due to time constraints. > > On Tue, Aug 3, 2010 at 2:17 AM, kcrisman <kcris...@gmail.com> wrote: >> >> >> On Aug 2, 2:05 pm, John H Palmieri <jhpalmier...@gmail.com> wrote: >>> On Aug 2, 11:01 am, kcrisman <kcris...@gmail.com> wrote: >>> >>> > Great, this is exactly what I had figured was going on now. It is >>> > very unfortunate that PIL does this. But at any rate I am making sure >>> > these tickets have that thread referenced, which they currently >>> > don't. >>> >>> > Also, what other effects will SAGE_BINARY_BUILD have on a source >>> > build? After all, I'm not distributing the binary I make! It would >>> > be nice to not have to deal with this, but since I don't use PIL it >>> > doesn't matter that much to me. >>> >>> Starting very recently, Sage environment variables are now documented >>> in the Sage installation guide. See >>> >>> <http://sagemath.org/doc/installation/source.html#environment- >>> variables> >>> >>> When I was looking into this, I only found SAGE_BINARY_BUILD in the >>> pil package, so I think it has no other effect. >> >> Having two environment variables used by only one package seems odd as >> well ;) Maybe we should just include the libjpeg or whatever - >> otherwise it's yet another dependency for Sage to test right, though >> as noted it only impacts my testing, not any use I can think of for >> me. >> >> - 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 >> > > > > -- > Tim Joseph Dumol <tim (at) timdumol (dot) com> > http://timdumol.com > -- Tim Joseph Dumol <tim (at) timdumol (dot) com> http://timdumol.com -- 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