August 2013 - macports-tickets - lists.macosforge.org

[MacPorts] #40072: unable to install graph-tool on mac OS X lion and mountain lion
by MacPorts 13 Aug '13

13 Aug '13

#40072: unable to install graph-tool on mac OS X lion and mountain lion ----------------------+-------------------------------- Reporter: absima@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: ----------------------+-------------------------------- This is the error I get on Terminal on both of my laptops. $ sudo port install py-graph-tool [[BR]] ---> Computing dependencies for py-graph-tool [[BR]] ---> Dependencies to be installed: py27-graph-tool [[BR]] ---> Configuring py27-graph-tool [[BR]] Error: Failed to configure py27-graph-tool, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-graph-tool/py27-graph-tool/work /graph-tool-2.2.24/config.log Error: org.macports.configure for port py27-graph-tool returned: configure failure: command execution failed Error: Failed to install py27-graph-tool Please see the log file for port py27-graph-tool for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-graph-tool/py27-graph-tool/main.log Error: The following dependencies were not installed: py27-graph-tool To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py-graph-tool failed [[BR]] $ -- Ticket URL: <https://trac.macports.org/ticket/40072> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #40081: py-sympy: update to 0.7.3
by MacPorts 13 Aug '13

13 Aug '13

#40081: py-sympy: update to 0.7.3 --------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-sympy --------------------------+------------------------ 0.7.3 is available: https://github.com/sympy/sympy/releases -- Ticket URL: <https://trac.macports.org/ticket/40081> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #29530: Xorg-server-devel 1.10.1.902 sets fontpath incorrectly
by MacPorts 13 Aug '13

13 Aug '13

#29530: Xorg-server-devel 1.10.1.902 sets fontpath incorrectly --------------------------------------+------------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: --------------------------------------+------------------------------------- The commend 'xset -q' in some ~/.xinitrc.d/<number><what ever>.sh produces, among other output: {{{ 21.05.11 21:54:28 org.macports.startx[28266] Notice /opt/local/share/fonts/misc/,/opt/local/share/fonts/TTF/,/opt/local/share/fonts/OTF/,/opt/local/share/fonts/Type1/,/opt/local/share/fonts/100dpi/,/opt/local/share/fonts/75dpi/,/Library/Fonts,/System/Library/Fonts ,built-ins }}} This == could == be the reason that Console reports: {{{ 21.05.11 21:54:28 org.macports.startx[28266] Notice /opt/local/bin/xset: bad font path element (#8), possible causes are: 21.05.11 21:54:28 org.macports.startx[28266] Notice Directory does not exist or has wrong permissions 21.05.11 21:54:28 org.macports.startx[28266] Notice Directory missing fonts.dir 21.05.11 21:54:28 org.macports.startx[28266] Notice Directory missing fonts.dir 21.05.11 21:54:28 org.macports.startx[28266] Notice Incorrect font server address or syntax }}} and GNU Emacsen 23.3 and 24.0.50 cannot show all text (the latter shows almost == no == text). Xorg-server-devel @1.10.1_0 produces similar reports in Console, but does not disable text rendering in GNU Emacsen. Console also reports: {{{ 21.05.11 21:54:30 [0x0-0x1d91d9].org.macports.X11[28235] Notice X11.app: Launching /opt/local/bin/xterm: 21.05.11 21:54:30 [0x0-0x1d91d9].org.macports.X11[28235] Notice argv[0] = /bin/sh 21.05.11 21:54:30 [0x0-0x1d91d9].org.macports.X11[28235] Notice argv[1] = -c 21.05.11 21:54:30 [0x0-0x1d91d9].org.macports.X11[28235] Notice argv[2] = /opt/local/bin/xterm 21.05.11 21:54:30 [0x0-0x1d91d9].org.macports.X11[28235] Notice /bin/sh: /opt/local/bin/xterm: No such file or directory 21.05.11 21:54:30 [0x0-0x1d91d9].org.macports.X11[28235] Notice /bin/sh: /opt/local/bin/xterm: No such file or directory }}} I only have /usr/X11/bin/xterm... -- Ticket URL: <https://trac.macports.org/ticket/29530> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 21

[MacPorts] #38527: clang-3.3 @3.3-r173279 AddressSanitizer binaries don't work without explicitly setting DYLD_LIBRARY_PATH
by MacPorts 13 Aug '13

13 Aug '13

#38527: clang-3.3 @3.3-r173279 AddressSanitizer binaries don't work without explicitly setting DYLD_LIBRARY_PATH -------------------------------+-------------------------------- Reporter: andrew.c.morrow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: clang-3.3 -------------------------------+-------------------------------- I'm using clang-3.3 @3.3-r173279: {{{ > /opt/local/bin/clang-mp-3.3 --version clang version 3.3 (trunk 173279) Target: x86_64-apple-darwin12.3.0 Thread model: posix }}} Given a simple hello world C++ program compiled with -fsanitize=address, the resulting binary cannot execute. {{{ > cat ./hello_world.cpp #include <cstdlib> #include <iostream> int main(int argc, char* argv[]) { std::cout << "Hello, World!\n"; return EXIT_SUCCESS; } > /opt/local/bin/clang-mp-3.3 ./hello_world.cpp -fsanitize=address -o ./hello_world > ./hello_world dyld: Library not loaded: /opt/local/var/macports/build/_opt_mports_dports_lang_llvm-3.3/clang-3.3/work/trunk/Release+Debug+Asserts/lib/clang/3.3/lib/darwin/libclang_rt.asan_osx_dynamic.dylib Referenced from: hello_world/./hello_world Reason: image not found [1] 62828 trace trap ./hello_world }}} It looks as if it is looking for the asan support library in the original build path, not the install path. But we do find that library in the install for the port: {{{ > mdfind -name libclang_rt.asan_osx_dynamic.dylib /opt/local/libexec/llvm-3.3/lib/clang/3.3/lib/darwin/libclang_rt.asan_osx_dynamic.dylib }}} Adding the containing directory to the DYLD_LIBRARY_PATH fixes things: the binary now runs: {{{ > DYLD_LIBRARY_PATH=/opt/local/libexec/llvm-3.3/lib/clang/3.3/lib/darwin ./hello_world Hello, World! }}} AddressSanitizer is super useful, it would be great if it worked out of the box for macports clang. -- Ticket URL: <https://trac.macports.org/ticket/38527> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #37190: install issue in py27-webkitgtk
by MacPorts 13 Aug '13

13 Aug '13

#37190: install issue in py27-webkitgtk ----------------------------------+-------------------------------- Reporter: guillaume.bonfante@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: ----------------------------------+-------------------------------- I'm working with OS X 10.6, When installing py27-webkitgtk +universal, I got the message: :info:build In file included from /opt/local/include/webkitgtk-1.0/webkit/webkitdom.h:135, :info:build from /opt/local/include/webkitgtk-1.0/webkit/webkit.h:27, :info:build from ./webkit/webkit.override:29: :info:build /opt/local/include/webkitgtk-1.0/webkit/WebKitDOMNavigator.h:81: error: expected '=', ',', ';', 'asm' or '__attribute__' before ':' token After I removed the two comments at lines 81 and 133 in /opt/local/include/webkitgtk-1.0/webkit/WebKitDOMNavigator.h the installation ended smoothly. All right. ************************************* After the complete installation, I tried #!/usr/bin/env python import gtk import webkit which does not work: emma:$ python Python 2.7.3 (default, Nov 30 2012, 14:00:47) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import gtk Xlib: extension "RANDR" missing on display "/tmp/launch-IVuuun/org.x:0". >>> import webkit Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/webkit/__init__.py", line 21, in <module> import webkit ImportError: dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/webkit/webkit.so, 2): Symbol not found: _aglGetCurrentContext Referenced from: /opt/local/lib/libwebkitgtk-1.0.0.dylib Expected in: flat namespace in /opt/local/lib/libwebkitgtk-1.0.0.dylib Any idea? -- Ticket URL: <https://trac.macports.org/ticket/37190> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 18

[MacPorts] #39804: autoconf-archive @2012.09.08: update to 2013.06.09
by MacPorts 13 Aug '13

13 Aug '13

#39804: autoconf-archive @2012.09.08: update to 2013.06.09 ---------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: autoconf-archive ---------------------+-------------------------------- {{{ Local-Admins-MacBook-Pro:~ ericgallager$ port -v livecheck autoconf- archive autoconf-archive seems to have been updated (port version: 2012.09.08, new version: 2013.06.09) }}} Announcement: http://lists.gnu.org/archive/html/autoconf-archive- announce/2013-06/msg00000.html Summary of News: - `AX_PROG_FLEX` has been updated to be more liberal about the name of the flex executable (perhaps it works with "`reflex`" now? idk...) - `AX_LIB_HDF5` has been updated to support the variables `HDF5_CC`, `HDF5_FC`, and `HDF5_LIBS`. - `AX_XSDCXX` has been added; a macro to find the CodeSynthesis XSD executable and the corresponding headers. - `AX_PYTHON_DEVEL` no longer overrides `LOCALMODLIBS` (might address #39223? idk...) - `AX_CHECK_GLU` and `AX_CHECK_GLUT` have been re-added. -- Ticket URL: <https://trac.macports.org/ticket/39804> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #40070: py-ipython 1.0.0: Unable to verify file checksums
by MacPorts 12 Aug '13

12 Aug '13

#40070: py-ipython 1.0.0: Unable to verify file checksums --------------------+-------------------------------- Reporter: nad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: py-ipython --------------------+-------------------------------- Stealth update perhaps? {{{ :info:checksum ---> Checksumming ipython-1.0.0.tar.gz :error:checksum Checksum (rmd160) mismatch for ipython-1.0.0.tar.gz :info:checksum Portfile checksum: ipython-1.0.0.tar.gz rmd160 eb4a1e4e21296674083dbe4a60ce5fee12008d36 :info:checksum Distfile checksum: ipython-1.0.0.tar.gz rmd160 6dfd209010548ec3d65e5ce607ca11713a1eba4a :error:checksum Checksum (sha256) mismatch for ipython-1.0.0.tar.gz :info:checksum Portfile checksum: ipython-1.0.0.tar.gz sha256 0d07521b4784e1b1f676b4b32c1f708a026cf398a0e6c3f095fce41f1402911c :info:checksum Distfile checksum: ipython-1.0.0.tar.gz sha256 ce0b57c61f9909f9475d44c913524fbb2e945053877c2f0c0bb18f06e63f7972 :info:checksum The correct checksum line may be: :info:checksum checksums rmd160 6dfd209010548ec3d65e5ce607ca11713a1eba4a \ sha256 ce0b57c61f9909f9475d44c913524fbb2e945053877c2f0c0bb18f06e63f7972 :error:checksum org.macports.checksum for port py27-ipython returned: Unable to verify file checksums }}} -- Ticket URL: <https://trac.macports.org/ticket/40070> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #40075: ola @0.8.30: update to 0.8.31
by MacPorts 12 Aug '13

12 Aug '13

#40075: ola @0.8.30: update to 0.8.31 ---------------------------------+-------------------------------- Reporter: nomis52@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: haspatch maintainer | Port: ola ---------------------------------+-------------------------------- Update to reflect the new upstream release. -- Ticket URL: <https://trac.macports.org/ticket/40075> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #40063: Snow Leopard buildbot stuck at deploy archives
by MacPorts 12 Aug '13

12 Aug '13

#40063: Snow Leopard buildbot stuck at deploy archives ----------------------------+------------------------- Reporter: cal@… | Owner: wsiegrist@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.2.0 Keywords: buildbots | Port: ----------------------------+------------------------- It seems the SL buildbot is currently stuck at the "deploy archives" step (and has been for quite a while). Can you take a look? -- Ticket URL: <https://trac.macports.org/ticket/40063> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #40074: Create a global 'off' switch for startupitem.autostart
by MacPorts 12 Aug '13

12 Aug '13

#40074: Create a global 'off' switch for startupitem.autostart -------------------------+--------------------- Reporter: dluke@… | Owner: dluke@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.0 Keywords: | Port: -------------------------+--------------------- Thread [https://lists.macosforge.org/pipermail/macports- dev/2013-August/023788.html here]. I would like to be able to globally disable startupitem.autostart (with a conf setting) just to protect against the possibility that someone has it enabled for something that gets installed as a dependency that I don't actually want running [it would be cool if the implementation of the global 'off' switch for this automatically added a note (or at least a ui_msg) that says what would have been run, or what needs to be run to 'complete' the install]. -- Ticket URL: <https://trac.macports.org/ticket/40074> MacPorts <http://www.macports.org/> Ports system for OS X

1 3