#9864: Error building PIL on RHEL Server 5.5
--------------------------------------------+-------------------------------
   Reporter:  mpatel                        |       Owner:  GeorgSWeber
       Type:  defect                        |      Status:  needs_work 
   Priority:  blocker                       |   Milestone:  sage-4.6.1 
  Component:  build                         |    Keywords:             
     Author:  Leif Leonhardy, Mitesh Patel  |    Upstream:  N/A        
   Reviewer:                                |      Merged:             
Work_issues:  make patches #9419-compliant  |  
--------------------------------------------+-------------------------------

Comment(by leif):

 Replying to [comment:40 Koen]:
 > It's because the PIL setup.py is trying to be smart: it creates its own
 list of search paths for includes & libs, and when it cannot find
 jpeglib.h in the includes or libjpeg.so in the libraries search paths, it
 will disable its own JPEG support. However, it does not check a common
 place for 64-bit Linuxes (which are not Debian-based), so right now it is
 too eager in disabling JPEG support.
 > Note that SciPy uses PIL to read JPEG images, so not having it working
 is quite annoying.

 Yep. If we don't fix that (here), you could still create symbolic links in
 `SAGE_LOCAL/{include,lib}`; then PIL should find them as well.

 (If we build binary distributions (with e.g. JPEG support enabled), we
 have to manually ''copy'' the system's respective libraries and headers to
 `SAGE_LOCAL/...` anyway.)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9864#comment:41>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to