Thanks. I'll check Macports again.
I wasn't sure where to find the binaries.
Regards,
Jack
"Trust me. I have a lot of experience at this."
General Custer's unremembered message to his men,
just before leadin
On Sun, 2010-06-13 at 23:45 -0500, Jack Uretsky wrote:
> Thanks. I believe I have Macports installed. Here's what I get on the
> first command:
>
> Macintosh-2:~ jackuretsky$ sudo port install libjpeg
> Password:
> sudo: port: command not found
>
> Further suggestions?
I bet you don't. Any re
Thanks. I believe I have Macports installed. Here's what I get on the
first command:
Macintosh-2:~ jackuretsky$ sudo port install libjpeg
Password:
sudo: port: command not found
Further suggestions?
Regards,
Jack
"Trust
Jack Uretsky wrote:
Hi-
I'm a newcomer, about to try to install PIL. I'm running OS X snow
leopard pm am intel Mac. I'm at the point where I've downloaded the 4
files mentioned in the README (
libjpeg62
zlib1g
libfreetype6
liblcmsl)
but don't know what
Hi-
I'm a newcomer, about to try to install PIL. I'm running OS X
snow leopard pm am intel Mac. I'm at the point where I've downloaded the
4 files mentioned in the README (
libjpeg62
zlib1g
libfreetype6
liblcmsl)
but don't know what to do with them.
On Wed, May 26, 2010 at 9:00 PM, Fredrik Lundh wrote:
> PIL's setup.py script (which uses Python's standard "distutils" build
> mechanisms) work the same was as the venerable "make" utility (1);
> that is, if a target exists and is newer than the source files, it's
> assumed to be correct. This i
PIL's setup.py script (which uses Python's standard "distutils" build
mechanisms) work the same was as the venerable "make" utility (1);
that is, if a target exists and is newer than the source files, it's
assumed to be correct. This is great when you change only a few
source files, but less great
Hi--
I just wanted to close out this thread, for the benefit of anyone reading
the archives in the future.
The problem was solved by following Chris Barker's advice/observation that
the files "site-packages/PIL/_imaging*.so" needed to be deleted and then the
PIL package rebuilt. That is exactly
Mark Twenhafel wrote:
Chris--I thought I had mailed this Friday, but it never appeared in image-sig,
so here goes again. I'll continue with the interleaved response-style. Thanks
for the help--for my part, I'm working through K&R,
I doubt K&R will help there -- I'd look for something about g
Chris--I thought I had mailed this Friday, but it never appeared in image-sig,
so here goes again. I'll continue with the interleaved response-style. Thanks
for the help--for my part, I'm working through K&R, hoping that this will teach
me enough about compiling and linking C to puzzle out why th
Mark Twenhafel wrote:
Try adding
print Image.core.__file__
to your script and make sure that the output is what you expect.
what was the result of that?
At this point, my working hypothesis is that I did not install libjpeg
correctly. I'm working on OS X Tiger. What I did was download
On Fri, May 14, 2010 at 8:22 AM, Mark Twenhafel wrote:
> Hi--
>
> Follow-up to yesterday's question. Also, thanks to Fredrik Lundh for
> off-list assistance. At one point, I was momentarily speechless when I
> turned from an email back to the documentation I was reading and noticed
> that both w
Hi--
Follow-up to yesterday's question. Also, thanks to Fredrik Lundh for
off-list assistance. At one point, I was momentarily speechless when I
turned from an email back to the documentation I was reading and noticed
that both were authored by the same, Mr. Lundh. :-)
>From yesterday, I progr
13 matches
Mail list logo
