#49370: An error when activate for wxPython-3.0 ------------------------------+------------------- Reporter: tungyuanhsiao@… | Owner: jwa@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: wxPython-3.0 | ------------------------------+------------------- Changes (by ryandesign@…): * cc: ryandesign@…, mojca@… (added) * owner: macports-tickets@… => jwa@… * port: => wxPython-3.0 Old description:
Error: org.macports.activate for port wxPython-3.0 returned: Image error: Source file /opt/local/var/macports/software/wxPython-3.0/mpextractkTiaNAbK/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. Please see the log file for port wxPython-3.0 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_distfiles.macports.org_ports_graphics_wxWidgets-3.0/wxPython-3.0/main.log Error: Problem while installing wxPython-3.0 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets
New description: {{{ Error: org.macports.activate for port wxPython-3.0 returned: Image error: Source file /opt/local/var/macports/software/wxPython-3.0/mpextractkTiaNAbK/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. Please see the log file for port wxPython-3.0 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_distfiles.macports.org_ports_graphics_wxWidgets-3.0/wxPython-3.0/main.log Error: Problem while installing wxPython-3.0 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets }}} -- Comment: This is a curious error. It seems that the file "._printfw.h" (and others) was added to the archive, but at extract time, it couldn't be found. Files whose names begin with "._" are created by OS X when a file with extended attributes is created on a filesystem that does not support extended attributes. Is the filesystem MacPorts is installed on formatted as HFS+ (Journaled), or as something else? Are there other volumes involved (for example, have you symlinked the build or software directories or other parts of the MacPorts prefix onto other volumes), and if so, how are those volumes formatted? -- Ticket URL: <https://trac.macports.org/ticket/49370#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X