Well last night I started working on removing all traces of PIL and libjpeg as well as the install instructions from Andrews link (Thansk Andrew!)
If there was a problem to encounter I seemed to hit it... :-( It all started when Git would not unzip, I finally got that with the xjvf flag I believe, and then now I get an error due to a dylib not being linked to x86_64 architecture. JESUS! I spent time trying to research that without much luck :( I upgraded the default mac installation python to python 2.6.6 and also am using virtualenv for my django envs and am having issues installing virtualenvwrapper, yet another install problem... Looks like something with the the source file and the virtualenv_bashrc file. Atleast in the morning my patience is a bit better... I will try hammering away at it again tomororw. I think I need a day off from it. Thanks everybody for all their insight and advice, it is very much appreciated. If you are anywhere near SF, there is beer on me for it. -Ben On Sep 1, 4:09 am, Mathieu Leduc-Hamel <marra...@gmail.com> wrote: > This is because you should not use the Python interpreter from you're > Mac installation. Are you using buildout ? VirtualEnv? or nothing ? > > Buildout: > > /opt/local/bin/python2.6 bootstrap.py > > Virtualenv: > > virtualenv -p /opt/local/bin/python2.6 <name> > > Nothing: > > /opt/local/bin/python2.6 manage.py runserver > > On Tue, Aug 31, 2010 at 9:40 PM, keynesiandreamer > > > > > > <keynesiandr...@gmail.com> wrote: > > So I tried the Macports option and it started to look good, but then I > > got: > > > ---> Installing py26-pil @1.1.7_1 > > ---> Activating py26-pil @1.1.7_1 > > Error: Target org.macports.activate returned: Image error: /opt/local/ > > Library/Frameworks/Python.framework/Versions/2.6/bin/pilconvert.py > > already exists and does not belong to a registered port. Unable to > > activate port py26-pil. Use 'port -f activate py26-pil' to force the > > activation. > > Log for py26-pil is at: /opt/local/var/macports/logs/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py2 > > 6- > > pil/main.log > > Error: Status 1 encountered during processing. > > To report a bug, see <http://guide.macports.org/#project.tickets> > > Ben-Jammin-MacBook:~ martinek$ port -f activate py26-pil > > Warning: Failed to open Portfile from registry for py26-pil @1.1.7_1 > > ---> Activating py26-pil > > Error: port activate failed: sqlite error: attempt to write a readonly > > database (8) > > Ben-Jammin-MacBook:~ martinek$ sudo port install py26-pil > > > Sudo didn't work either > > :-( > > > I am not even sure what DB is being discussed there... > > > I also tried reinstalling PIL after the failure of MacPorts and > > something might have worked here. I don't get the same problem at the > > python prompt trying import _imaging > > > Unfortunately Django/Pinax doesn't seem to see this after reactivating > > the ENV and restarting the server: > > > BLurghh!!! > > > Is it worth trying to remake the virtualenv I am working with? Would > > that help or is the problem still up the stream? > > > -Ben > > > On Aug 31, 11:49 am, keynesiandreamer <keynesiandr...@gmail.com> > > wrote: > >> Thanks Bill and Mathieu! > > >> I will try the Mac port option first, in fact I did look at it last > >> night probably around 1am or so... > > >> I treied rebuilding the virtual env I was using as well just to > >> verify, but the problem seem higher up the stream and Bill indicated. > >> I will take a look for the ld.conf equiv in OSX at lunch today. > > >> Thanks! > >> Ben > > >> On Aug 31, 10:20 am, Mathieu Leduc-Hamel <marra...@gmail.com> wrote: > > >> > To work with PIL and other librairies a little bit weird and difficult > >> > to install the best way is to install Macport and after that: > > >> > port install py26-pil > > >> > and you'll need to use the python of the macport installation: > > >> > $ /opt/local/bin/python2.6 > > >> > It's the samething on linux, i'm alway using the PIL package from my > >> > distro... > > >> > On Tue, Aug 31, 2010 at 7:10 PM, Bill Freeman <ke1g...@gmail.com> wrote: > >> > > This sounds more like libjpeg isn't on the library load path, a > >> > > system, rather than python, setting. > > >> > > I haven't done this with a Mac, but PIL has been troublesome on *nix > >> > > servers for us as well. > > >> > > The common problems for us don't sound like your problem. [Some > >> > > versions of PIL install as "Imaging" rather than PIL. If libjpeg > >> > > isn't installed first, including development data (headers, stub > >> > > library (called import library on Windows)) when your packaging system > >> > > separates them, when you first build PIL, you can rebuild it until you > >> > > are blue in the face and it won't pick up libjpeg that you installed > >> > > later - need to totally remove PIL and rebuild] > > >> > > You seem to have successfully built to use libjpeg, but it isn't > >> > > there. I can think of three possibilities: > > >> > > 1. It really isn't there, maybe the reverse problem of installing a > >> > > "development" package but not the main one. > > >> > > 2. It's there, but it doesn't match the version your _imagning.so was > >> > > built against. > > >> > > 3. It's there, but the library loader hasn't been told about it. On > >> > > linux this means findable via ld.conf (or ld.so.conf) and ldconfig has > >> > > been run since. Package installation scripts usually take care of > >> > > this, but it sometimes needs to be done by hand, if you're just, for > >> > > example, unpacking a tarball. I don't know the equivalent for osx. > > >> > > Good luck. > > >> > > Bill > > >> > > On Tue, Aug 31, 2010 at 12:41 PM, keynesiandreamer > >> > > <keynesiandr...@gmail.com> wrote: > >> > >> Howdy! > > >> > >> I have been working with Django/Pinax on a 10.6.4 system with python > >> > >> 2.6.6 and have had no luck getting PIL to work. I have looked through > >> > >> about 10-15 paged including ones listed on this group with no results. > >> > >> Currently the error I am getting is: > >> > >> The _imaging C module is not installed > > >> > >> I have verified _imaging.so is in the file system. So it seems like a > >> > >> syspath issue. I tried verifying that in the python prompt: > > >> > >>>>> import _imaging > >> > >> dlopen("/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ > >> > >> lib/python2.6/site-packages/PIL/_imaging.so", 2); > >> > >> Traceback (most recent call last): > >> > >> File "<stdin>", line 1, in <module> > >> > >> ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/ > >> > >> Versions/2.6/lib/python2.6/site-packages/PIL/_imaging.so, 2): Symbol > >> > >> not found: _jpeg_resync_to_restart > >> > >> Referenced from: /opt/local/Library/Frameworks/Python.framework/ > >> > >> Versions/2.6/lib/python2.6/site-packages/PIL/_imaging.so > >> > >> Expected in: flat namespace > >> > >> in /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/ > >> > >> python2.6/site-packages/PIL/_imaging.so > > >> > >> Any help would be greatly appreciated, too many hours stuck on this > >> > >> with no results.. :-( > > >> > >> -- > >> > >> You received this message because you are subscribed to the Google > >> > >> Groups "Django users" group. > >> > >> To post to this group, send email to django-us...@googlegroups.com. > >> > >> To unsubscribe from this group, send email to > >> > >> django-users+unsubscr...@googlegroups.com. > >> > >> For more options, visit this group > >> > >> athttp://groups.google.com/group/django-users?hl=en. > > >> > > -- > >> > > You received this message because you are subscribed to the Google > >> > > Groups "Django users" group. > >> > > To post to this group, send email to django-us...@googlegroups.com. > >> > > To unsubscribe from this group, send email to > >> > > django-users+unsubscr...@googlegroups.com. > >> > > For more options, visit this group > >> > > athttp://groups.google.com/group/django-users?hl=en. > > >> > -- > >> > Mathieu Leduc-Hamel > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/django-users?hl=en. > > -- > Mathieu Leduc-Hamel -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
