#10359: Let PIL search '.../lib64' directories for optional libraries if
appropriate
------------------------------+---------------------------------------------
Reporter: leif | Owner: tbd
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: packages | Keywords: Python Imaging libary JPEG TIFF
PNG CentOS Fedora openSUSE RedHat RHEL
Author: Leif Leonhardy | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:11 vbraun]:
> Clearly its dumb of PIL to look in any particular hard-coded directory
to see whether libjpeg is available. The only correct way (TM) is to build
a test program and see if it compiles, as the autotools would do. We do
have a configurable library search path precisely so that `configure` does
not need to know the location of each library. Did you file an upstream
bug report?
Unfortunately^TM^, upstream might not consider this a problem, since (I
think) usually PIL would find those libraries - if installed - where (a
system-wide) Python was installed, though not necessarily (regarding the
`lib64` issue).
> That being said, the band-aid of having a better hard-coded directory is
probably the best we can do until upstream fixes their broken `setup.py`.
The latest, 1.1.7, isn't much better.
(And I think they won't accept our `if SAGE_BINARY_BUILD = "yes"` fixes...
;-) )
It also has
{{{
#!python
...
# Library pointers.
#
# Use None to look for the libraries in well-known library locations.
# Use a string to specify a single directory, for both the library and
# the include files. Use a tuple to specify separate directories:
# (libpath, includepath). Examples:
#
# JPEG_ROOT = "/home/libraries/jpeg-6b"
# TIFF_ROOT = "/opt/tiff/lib", "/opt/tiff/include"
#
# If you have "lib" and "include" directories under a common parent,
# you can use the "libinclude" helper:
#
# TIFF_ROOT = libinclude("/opt/tiff")
...
# Override settings
try:
from setup_site import *
except ImportError:
pass
}}}
so one could provide such a file giving the exact locations. One could
even create it in `spkg-install`, and / or create symbolic links in
`SAGE_LOCAL/{include,lib}`.
Btw, `isainfo` on Solaris only tells us what ''the kernel'' is built for
or supports, not if Sage or Sage's Python was built 32- or 64-bit.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10359#comment:12>
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.
