On Mon, Apr 13, 2009 at 11:35:36AM -0400, Randall Perry said: > Bryan Blackburn wrote: > > On Mon, Mar 30, 2009 at 07:37:15PM -0500, Bill Hernandez said: > > [...] > >> ---> Activating mod_python25 @3.3.1_2 > >> > >> Error: Target org.macports.activate returned: Image error: /opt/local/ > >> apache2/modules/mod_python.so already exists and does not belong to a > >> registered port. Unable to activate port mod_python25. > >> Error: Status 1 encountered during processing. > > > > That's the bad issue with the 'not a directory' problem, when the old one is > > uninstalled/deactivated, the files aren't actually removed (the error occurs > > before the file list is added to the file map, so port thinks it has no > > files). This means you have to force the activation of the port, and of > > course deal with the annoying saved '*.mp_*' files. > > > Having problems getting mod_python working and saw this thread. > > Error I'm getting: > ---> Activating mod_python25 @3.3.1_1 > Error: Target org.macports.activate returned: Not a directory > Error: Status 1 encountered during processing.
The 'not a directory' error is the issue mentioned above. Your problems with it linking with the wrong python should be fixed if you upgrade mod_python25 to 3.3.1_3, which was improved [1] to link properly with MacPorts' python. Bryan [1] - <http://trac.macports.org/changeset/49191> [...] > > -- > Randall Perry > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
