Re: Meaning of Not a directory
Uldis Bojars wrote:
On Mon, Jul 14, 2008 at 4:35 PM, Rainer Müller [EMAIL PROTECTED] wrote:
Rainer Müller wrote:
I think there is some problem with the python25 framework port. I can
reproduce the message here and will see if I can find a solution.
I am still trying to figure out where graphviz or swig pick up the path
to the framework directory, but I can't find it. It needs to be changed
to point to ${prefix}/lib/python25 instead there. Any help appreciated.
Perhaps we should file a ticket for this bug (especially if we do not
solve it right away), but what port should it be filed against?
Python, SWIG or every individual port which has problems with
SWIG-generated Python bindings?
Was a ticket ever filed for this? I gather that the problem is that
activation doesn't follow directory symlinks - I wonder if making it do
so would break anything?
Fixing the problem in the ports may be preferable though, given our
current release rate.
- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of Not a directory
On Aug 7, 2008, at 14:56, Joshua Root wrote:
Uldis Bojars wrote:
On Mon, Jul 14, 2008 at 4:35 PM, Rainer Müller wrote:
Rainer Müller wrote:
I think there is some problem with the python25 framework port.
I can
reproduce the message here and will see if I can find a solution.
I am still trying to figure out where graphviz or swig pick up
the path
to the framework directory, but I can't find it. It needs to be
changed
to point to ${prefix}/lib/python25 instead there. Any help
appreciated.
Perhaps we should file a ticket for this bug (especially if we do not
solve it right away), but what port should it be filed against?
Python, SWIG or every individual port which has problems with
SWIG-generated Python bindings?
Was a ticket ever filed for this?
I don't think so. But I was able to reproduce the problem too.
I gather that the problem is that
activation doesn't follow directory symlinks - I wonder if making
it do
so would break anything?
It's worth a try to change it.
Fixing the problem in the ports may be preferable though, given our
current release rate.
Oh, we *will* release 1.7.0 before too much longer. Heck, I'll do it
if nobody else does.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of Not a directory
Joshua Root wrote: Was a ticket ever filed for this? I gather that the problem is that activation doesn't follow directory symlinks - I wonder if making it do so would break anything? Symlinks are owned by a specific port, directories are not. So if we follow the symlinks, stuff will end up at places it was not meant to be. If the port owning the symlink is deactivated/uninstalled, other ports could break as they are probably expecting stuff under the symlink. This wouldn't be a good idea. But we could need a better error message than what we currently have. Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of Not a directory
Rainer Müller wrote: Joshua Root wrote: Was a ticket ever filed for this? I gather that the problem is that activation doesn't follow directory symlinks - I wonder if making it do so would break anything? Symlinks are owned by a specific port, directories are not. So if we follow the symlinks, stuff will end up at places it was not meant to be. If I'm understanding correctly, stuff installed by the affected py-* ports would end up where it *is* meant to be. No? If the port owning the symlink is deactivated/uninstalled, other ports could break as they are probably expecting stuff under the symlink. Could be a problem in some cases, but python modules already break by definition if you remove python. This wouldn't be a good idea. But we could need a better error message than what we currently have. Rainer - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of Not a directory
On Mon, Jul 14, 2008 at 4:35 PM, Rainer Müller [EMAIL PROTECTED] wrote:
Rainer Müller wrote:
I think there is some problem with the python25 framework port. I can
reproduce the message here and will see if I can find a solution.
I am still trying to figure out where graphviz or swig pick up the path
to the framework directory, but I can't find it. It needs to be changed
to point to ${prefix}/lib/python25 instead there. Any help appreciated.
Does anyone know how to fix this or where ./configure or the linker
picks up the path to Leopard's built-in Python?
I can not find where the wrong path comes from either. The path
returned by the Python snippet in the ./configure points to the
correct Python location (/opt/local/...) and yet the library gets
linked against the system Python. Here is the path returned by Python:
print sys.prefix
/opt/local/Library/Frameworks/Python.framework/Versions/2.5
Perhaps we should file a ticket for this bug (especially if we do not
solve it right away), but what port should it be filed against?
Python, SWIG or every individual port which has problems with
SWIG-generated Python bindings?
Uldis
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of Not a directory
Rainer Müller wrote:
I think there is some problem with the python25 framework port. I can
reproduce the message here and will see if I can find a solution.
I am still trying to figure out where graphviz or swig pick up the path
to the framework directory, but I can't find it. It needs to be changed
to point to ${prefix}/lib/python25 instead there. Any help appreciated.
If nothing else works, I would have to change the default path of the
site-packages to be inside the framework and add the symlink at
${prefix}/lib/python25. But that means, everyone would be forced to
reinstall any port using python25. And the same change would be needed
for python24 and python30 as it could appear there, too.
My plan with the symlink in the direction framework - lib was to avoid
unnecessary reinstalls.
Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of Not a directory
Marcus Calhoun-Lopez wrote: I am experimenting with a local version of graphviz. During the activation phase, I get the error: Error: Target org.macports.activate returned: Not a directory Does anyone know the meaning of this error? This happens when 'port activate' finds something unexpected. For example, assume /opt/local/foo is a symlink to another directory. Now port tries to activate the file /opt/local/foo/bar, but it can't do that because /opt/local/foo is not a directory. I think there is some problem with the python25 framework port. I can reproduce the message here and will see if I can find a solution. Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of Not a directory
On Jul 8, 2008, at 09:30, Marcus Calhoun-Lopez wrote: I am experimenting with a local version of graphviz. During the activation phase, I get the error: Error: Target org.macports.activate returned: Not a directory Does anyone know the meaning of this error? The previous message is DEBUG: Adding link to file_map: /opt/local/Library/Frameworks/ Python.framework/Versions/2.5/lib/python2.5/site-packages/gv.py for: graphviz The file gv.py is the problem. I have arranged it so that gv.py is the only python file to be installed. When I prevent it from being installed, there is no problem Strangely enough, the file gv.py does in fact get installed (and then the activation phase dies). The directory /opt/local/Library/Frameworks/Python.framework/ Versions/ 2.5/lib/python2.5 is not a directory. It is a link to /opt/local/lib/python2.5. I am the maintainer of the graphviz port but I do not use the language bindings or Python in general so if something isn't working right I'll need your help. How are you installing graphviz? With the +python variant? I see that this variant is coded to use the python24 port. What do you mean a local version of graphviz? Do you mean outside of MacPorts? If so, is there something broken in the graphviz port that I need to fix? ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
