On Jul 18, 2015, at 10:29, Wahlstedt Jyrki wrote:
>
> activating wxPython-3.0 leads to this:
> ===
> ---> Activating wxPython-3.0 @3.0.2_4
> Error: Failed to activate wxPython-3.0: Image error: Source file
> /opt/local/var/macports/software/wxPython-3.0/mpextracthReS3feC/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/wxPython/._printfw.h
> does not appear to exist (cannot lstat it). Unable to activate port
> wxPython-3.0.
> Error: See
> /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_wxPython-3.0-3.0.2_4_a394d4d57ce632ad8bc69986734a877ab83d26d48f87d4fe885b727d3c10cc3c-8722/wxPython-3.0/main.log
> for details.
> Warning: Failed to execute portfile from registry for wxPython-3.0 @3.0.2_4
> ---> Activating wxPython-3.0 @3.0.2_4
> Error: port activate failed: Image error: Source file
> /opt/local/var/macports/software/wxPython-3.0/mpextract6B2a0Dk4/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxPython/3.0/include/wx-3.0/wx/wxPython/._printfw.h
> does not appear to exist (cannot lstat it). Unable to activate port
> wxPython-3.0.
> ===
> Has anybody else seen anything like this? Build goes just fine, other ports
> have activated fine, too (I’m on 10.11, hence had to build base from source,
> so if someone says I’m on my own, I’ll accept that:)
So it failed to activate the port because the file ._printfw.h didn't exist.
Files whose names begin with "._" are created when OS X tries to add resource
fork or other extended attribute information to a file on a file system that
does not support those features, in other words a file system other than HFS+.
Is your system using such a filesystem?
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
