Hi again Graham,
> No, that is a different flag. It is -Wl,-f not -Wl,-F. They mean
> different things. You would use:
>
> LDFLAGS = -Wl,-F/Library/Frameworks .....existing options
OK, I understand. The -F option is just to point to the right
framework location.
But my previous compilation/installation found the right framework
path, using the -framework,Python option, since I'm using the DMG
version of Python 2.4, installed in the proper location. It was just
the ending of the path that was faulty with:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.5/site-
packages/
instead of:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-
packages/
But I can give the -F option a try to see if it makes things better.
> > Aha. So would that be like an ordinary $PATH setting in my
> > bash .profile?:
> > export PATH="/Library/Frameworks/Python.framework/Versions/Current/bin:
> > ${PATH}"
>
> Yes, but in the envvars file.
OK, thanks, I'll remember that.
> Note that this is only required because you have a secondary version
> of Python installed in a non standard location. I believe if you use
> dmg versions and not MacPorts it installs in standard locations and so
> this isn't required.
OK, but I actually run the DMG version of Python 2.4, installed in the
proper location in /Library/Framworks/Python.framework/ ...
and Apache finds the mod_python in site-packages, once I have moved
the compiled package from the python2.5/site-packages where the
installation puts it to the python2.4/site-packages where Apache
expects it to be.
> Half the problem here is mod_python and the fact that it has two
> parts, the Apache module and the Python modules. If the Apache module
> cant find the Python modules at runtime it will not work. You might
> instead consider looking at mod_wsgi instead. It is totally self
> contained in the Apache module and doesn't need the separate Python
> modules and therefore you cant get this specific problem. You still
> have to deal with the problems related to multiple Python versions,
> but this is explained in the documentation for mod_wsgi.
This seems to be a better solution for the future, I'll consider this.
Thanks,
Ulf
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
