June 2016 - macports-tickets - lists.macosforge.org

[MacPorts] #51419: py27-scipy faols to upgrade/install
by MacPorts 14 Oct '16

14 Oct '16

#51419: py27-scipy faols to upgrade/install ------------------------------+-------------------------------- Reporter: david.w.watson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: py27-scipy ------------------------------+-------------------------------- Using numpy with openblas, get "-rpath=" error. see log -- Ticket URL: <https://trac.macports.org/ticket/51419> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #51250: py-numpy: Build failure updating to version 1.11.0_0
by MacPorts 14 Oct '16

14 Oct '16

#51250: py-numpy: Build failure updating to version 1.11.0_0 --------------------+------------------------- Reporter: mf2k@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: py-numpy --------------------+------------------------- I'm trying to update both py35-numpy and py27-numpy to the latest version 1.11.0_0 but neither build for me. I'm attaching the log for py35-numpy. Here are the variants I am using: {{{ $ port installed py35-numpy The following ports are currently installed: py35-numpy @1.10.4_0+atlas+gcc5 (active) }}} -- Ticket URL: <https://trac.macports.org/ticket/51250> MacPorts <https://www.macports.org/> Ports system for OS X

1 17

[MacPorts] #50881: Using gcj 5.3.0 on Mac OS X 10.6.8, Snow Leopard, on a Java source file leads to an error
by MacPorts 14 Oct '16

14 Oct '16

#50881: Using gcj 5.3.0 on Mac OS X 10.6.8, Snow Leopard, on a Java source file leads to an error -----------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: gcc5, gcc49 -----------------------------+-------------------------------- It's this one: {{{ pete 109 /\ gcj conftest.java --main=conftest -o conftest gcj: error trying to exec 'ecj1': execvp: No such file or directory }}} For me this happens when configure'ing the gettext-tools from gettext-0.19.7. This happens with gcc49 @4.9.3_0 and gcc5 @5.3.0_0, gcc47 @4.7.4_5 works OK. (I do not have gcc48 installed.) See also #22066! -- Ticket URL: <https://trac.macports.org/ticket/50881> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #49144: Error: Failed to install snappy
by MacPorts 14 Oct '16

14 Oct '16

#49144: Error: Failed to install snappy --------------------------------+-------------------------------- Reporter: peter.h.m.brooks@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: --------------------------------+-------------------------------- I've repeated errors doing a: port install updated " # port install outdated ---> Computing dependencies for blosc ---> Dependencies to be installed: snappy ---> Fetching distfiles for snappy ---> Verifying checksums for snappy ---> Extracting snappy ---> Configuring snappy ---> Building snappy Error: org.macports.build for port snappy returned: command execution failed Error: Failed to install snappy Please see the log file for port snappy for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_archivers_snappy/snappy/main.log Error: The following dependencies were not installed: snappy To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port blosc failed " Darwin eve.local 15.0.0 Darwin Kernel Version 15.0.0: Wed Aug 26 16:57:32 PDT 2015; root:xnu-3247.1.106~1/RELEASE_X86_64 x86_64 -- Ticket URL: <https://trac.macports.org/ticket/49144> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #45616: Compile error with g++ 4.8.2
by MacPorts 14 Oct '16

14 Oct '16

#45616: Compile error with g++ 4.8.2 -------------------------+-------------------------------- Reporter: gsteele13@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: boost -------------------------+-------------------------------- I recently reinstalled mac OS on my macbook, and in doing so, have switched from a 10.6 fink system to a 10.9 macports system. I was recently trying to compile some software (code available here http://nsweb.tn.tudelft.nl/~gsteele/spyview/) using the macports environment (primarily linking to librarires fltk and boost). The code compiled fine on my old 10.6 fink installation, but I am now getting the following error in 10.9 with macports: In file included from /opt/local/include/boost/limits.hpp:19:0, from /opt/local/include/boost/integer_fwd.hpp:16, from /opt/local/include/boost/integer.hpp:18, from /opt/local/include/boost/archive/basic_binary_iprimitive.hpp:49, from /opt/local/include/boost/archive/binary_iarchive_impl.hpp:21, from /opt/local/include/boost/archive/binary_iarchive.hpp:20, from myboost.h:5, from ImagePrinter.H:9, from ImageWindow.H:19, from spyview_ui.h:6, from spyview_ui.C:3: /opt/local/include/gcc48/c++/limits:1405:35: error: template argument 1 is invalid struct numeric_limits<__int128> I have also tried the apple-gcc42 compiler, and with this compiler, the code compiles fine, but fails at linking (I guess probably the gcc-4.8 c++ libraries are not linkable with gcc-4.2?). Has anyone else had this problem? Thanks, Gary -- Ticket URL: <https://trac.macports.org/ticket/45616> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #48564: pdfpc: update to version 4.0.0, moved to github
by MacPorts 14 Oct '16

14 Oct '16

#48564: pdfpc: update to version 4.0.0, moved to github ----------------------+------------------- Reporter: devans@… | Owner: cal@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: pdfpc ----------------------+------------------- pdfpc repository has now moved to https://github.com/pdfpc/pdfpc/ where the latest version of the port is 4.0.0. Updates include the use of gstreamer-1.0 and libgee-0.8. Port libgee06 is no longer necessary. -- Ticket URL: <https://trac.macports.org/ticket/48564> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #48577: subversion 1.9.0+ causes port lint Portfile property checks to fail
by MacPorts 14 Oct '16

14 Oct '16

#48577: subversion 1.9.0+ causes port lint Portfile property checks to fail ----------------------+-------------------------------- Reporter: devans@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.3 Keywords: | Port: ----------------------+-------------------------------- This concerns the behavior of the '''port lint''' command when the standard svn properties have not been set on a given Portfile. Using subversion 1.8.14 and earlier, failure to set these properties on the Portfile results in the useful message: {{{ ---> Verifying Portfile for argyll Error: Missing subversion property on Portfile, please execute: svn ps svn:keywords Id Portfile ---> 1 errors and 0 warnings found. }}} However, after upgrading to subversion 1.9.0, the message is less helpful: {{{ $ port lint ---> Verifying Portfile for argyll Warning: Unable to check for svn:keywords property: svn: warning: W200017: Property 'svn:keywords' not found on '/opt/macports/trunk/dports/graphics/argyll/Portfile' svn: E200000: A problem occurred; see other errors for details child process exited abnormally ---> 0 errors and 0 warnings found. }}} The cause is due to the fact that, in 1.9.0, subversion now considers it an error if propget is executed on a file when the target property does not exist. In the earlier subversion versions, subversion does not generate an error and just returns with null output. The current code depends on this latter behavior to identify when a property has not been set. If subversion returns an error, the error is printed as shown in the 1.9.0 case. The new 1.9.0 behavior in this situation needs to be accommodated as well as that of the older versions. Tested in MacPorts 2.3.3 but examination of current subversion HEAD shows that the problem has not yet been dealt with. -- Ticket URL: <https://trac.macports.org/ticket/48577> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #50631: py26-clnum: build fails during linking, 'internal error: atom not found in symbolIndex(__ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv) for architecture x86_64'
by MacPorts 13 Oct '16

13 Oct '16

#50631: py26-clnum: build fails during linking, 'internal error: atom not found in symbolIndex(__ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv) for architecture x86_64' ----------------------+-------------------------- Reporter: devans@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: py26-clnum ----------------------+-------------------------- On Yosemite 10.5.5 Xcode 7.2.1 {{{ /usr/bin/clang++ -L/opt/local/lib -Wl,-headerpad_max_install_names -bundle -undefined dynamic_lookup -arch x86_64 -arch x86_64 -I/opt/local/include build/temp.macosx-10.10-x86_64-2.6/clnum/src/clnum.o -lcln -lgmp -o build/lib.macosx-10.10-x86_64-2.6/clnum/clnum.so -s ld: warning: option -s is obsolete and being ignored ld: internal error: atom not found in symbolIndex(__ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv) for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) error: command '/usr/bin/clang++' failed with exit status 1 Command failed: cd "/opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-clnum/py26-clnum/work/clnum-1.6" && /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 setup.py --no-user-cfg build Exit code: 1 }}} Build log attached -- Ticket URL: <https://trac.macports.org/ticket/50631> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #49317: python34 @3.4.3 Allow loading SQLite extensions
by MacPorts 12 Oct '16

12 Oct '16

#49317: python34 @3.4.3 Allow loading SQLite extensions -------------------------+-------------------------------- Reporter: m3drano@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: python34 -------------------------+-------------------------------- This patch adds the flag --enable-loadable-sqlite-extensions to the Python build, which allows to load extensions in SQLite databases natively. There is more information on the subject in the Python's documentation: https://docs.python.org/3.4/library/sqlite3.html#f1 This setting is enabled on other OSes as default too, such as Linux distributions (Debian, Arch) at least. This patch applies to the port python34, but we can certainly extend it to other Python versions too if it is deemed appropriate. Other option would be to make this a port variant. -- Ticket URL: <https://trac.macports.org/ticket/49317> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #51689: preserve_runtime_libraries convenience PortGroup
by MacPorts 12 Oct '16

12 Oct '16

#51689: preserve_runtime_libraries convenience PortGroup -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: contrib | Version: Keywords: | Port: -------------------------+-------------------------------- This is mostly for reference though I'd love to see a similar feature in MacPorts: Many if not most Linux distributions have one way or another to keep older versions of shared libraries installed if the newer versions introduce ABI incompatibilities. Advantages are less and typically smaller upgrades for the users, less stress on the build bots and as a result, a more reliable upgrade process. That latter claim may need explanation (and may not be totally relevant for MacPorts): building binary packages takes time, and while those builds are in process users starting an upgrade may find themselves in a situation where the new packages aren't yet available. In extreme cases that may lead to uninstallation of numerous packages for which dependency criteria are no longer met. I've experienced that personally with Kubuntu during a KDE version update; I was lucky to have taken a ZFS snapshot before starting the update. To return closer to home: I was still running a 0.4 port:webp and thought I'd update it since it's could be a dependency for QtWebEngine (if that package allowed to build against the system webp on OS X). Webp 0.5 changes the library versioning, so a number of ports broke, including a few that are quite (very) expensive to build: ``` ---> Found 11 broken files, matching files to ports ---> Found 7 broken ports: graphviz @2.38.0 +pangocairo+universal+x11 /opt/local/bin/dot_builtins /opt/local/lib/graphviz/libgvplugin_webp.6.dylib ImageMagick @6.9.0-0 +x11 /opt/local/lib/ImageMagick-6.9.0/modules-Q16/coders/webp.so kde4-runtime @4.16.03.80.6 +docs /opt/local/lib/kde4/plugins/imageformats/kimg_webp.so opencv @3.1.0 +contrib+eigen+python27+qt5+tbb /opt/local/lib/libopencv_imgcodecs.3.1.0.dylib webkit-gtk @2.4.7 +video /opt/local/lib/libwebkitgtk-1.0.0.dylib webkit-gtk3 @2.4.7 +video /opt/local/lib/libwebkitgtk-3.0.0.dylib qt5-kde-devel @5.6.1 +harfbuzz+langselect+qt5kde /opt/local/libexec/qt5/Library/Frameworks/QtWebKit.framework/Versions/5/QtWebKit /opt/local/share/qt5/plugins/imageformats/libqwebp.dylib ``` The attached PortGroup provides an easy first-approach/PoC solution to this issue: it copies the specified runtime libraries from ${prefix} to ${destroot} during the post-destroot, if they do not already exist in the destroot. For instance, in a personal port:webp I used for testing I only needed to include the PortGroup and then add the line ``` preserve_libraries [glob -nocomplain ${prefix}/lib/libwebp*.*.dylib] ``` This simply allows currently installed ports to remain functional using their current dependencies and alleviates the need to revbump all dependents. They'll just move to using the new dependency version when they're rebuilt for other reasons (upgrade, reinstall, ...). I'm aware that this kind of practice may lead to runtime weirdness esp. with C++ libraries if different versions cannot coexist in a single application's runtime image. Easy enough to avoid and apart from that I see only one true issue: it won't be trivial to limit the number of old versions that will be preserved via a generic mechanism. -- Ticket URL: <https://trac.macports.org/ticket/51689> MacPorts <https://www.macports.org/> Ports system for OS X

1 5