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

[MacPorts] #44636: p5.16-spiffy fails upgrade
by MacPorts 13 Aug '14

13 Aug '14

#44636: p5.16-spiffy fails upgrade ------------------------------+-------------------------------- Reporter: david.w.watson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: p5.16-spiffy ------------------------------+-------------------------------- configure failed. See log -- Ticket URL: <https://trac.macports.org/ticket/44636> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #44633: p5.16-term-readkey upgrade failed
by MacPorts 13 Aug '14

13 Aug '14

#44633: p5.16-term-readkey upgrade failed ------------------------------+-------------------------------- Reporter: david.w.watson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: p5.16-term-readkey ------------------------------+-------------------------------- Error not clear to me from the log. -- Ticket URL: <https://trac.macports.org/ticket/44633> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #44638: doxygen @1.8.7: build fails with old python
by MacPorts 13 Aug '14

13 Aug '14

#44638: doxygen @1.8.7: build fails with old python ---------------------------+--------------------- Reporter: ryandesign@… | Owner: css@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: tiger leopard | Port: doxygen ---------------------------+--------------------- doxygen 1.8.7 fails to build on Leopard: {{{ /usr/bin/python configgen.py -cpp config.xml >../generated_src/doxygen/configoptions.cpp File "configgen.py", line 563 except Exception as inst: ^ SyntaxError: invalid syntax }}} Leopard's python is old: {{{ $ /usr/bin/python --version Python 2.5.1 }}} You may need a build dependency on a newer MacPorts-provided python. I see you already do that in the doc variant but I am not using the doc variant. -- Ticket URL: <https://trac.macports.org/ticket/44638> MacPorts <http://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #44632: p5-panotools-script: update to 0.28
by MacPorts 13 Aug '14

13 Aug '14

#44632: p5-panotools-script: update to 0.28 ----------------------------+-------------------------------- Reporter: seth.berrier@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: ----------------------------+-------------------------------- Just a proposal to bring this up to the latest version which includes several new and useful scripts. All that is needed is a bump in the version number and new checksums. Portfile diff attached. -- Ticket URL: <https://trac.macports.org/ticket/44632> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #44627: ceres-solver @1.9.0 library segfaults
by MacPorts 13 Aug '14

13 Aug '14

#44627: ceres-solver @1.9.0 library segfaults ------------------------------+-------------------------------- Reporter: julian.panetta@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: mavericks | Port: ceres-solver ------------------------------+-------------------------------- Installing Ceres through MacPorts and then compiling the following program with the built-in clang on Mac OS 10.9.{3,4} results in intermittent segfault/errors (it seems Ceres is scribbling over memory): http://julianpanetta.com/macports_bugs/test_ceres.cc {{{ $ /usr/bin/clang++ -g -O0 -std=c++11 -I/opt/local/include -I/opt/local/include/eigen3 test_ceres.cc -L/opt/local/lib -lceres -lglog -lgflags -lcholmod -lcxsparse -framework accelerate -o broken $ ./broken 0 1 [1] 75517 segmentation fault ./broken $ ./broken 0 1 2 3 libc++abi.dylib: terminating with uncaught exception of type std::length_error: vector [1] 75515 abort ./broken }}} Sometimes the program runs to completion, but usually it segfaults in the ceres::Solve call. The std::length_error shown above is much more rare (happens because vectors v1s and v2s are getting scribbled over). This was a very difficult bug to track down, and unfortunately I haven't been able to simplify the test case further. I am filing the bug here rather than upstream because the following setups do not exhibit the problem, leading me to suspect the error is in the MacPorts build: 1) Building ceres-solver manually (both from git repo, and from "latest stable release" link at ceres-solver.org) compiling test_ceres.cc with /usr/bin/clang;[[BR]] 2) Compiling test_ceres.cc with clang-mp-3.{4,5}, linking against MacPorts libceres.a Those made me suspect an ABI incompatibility with the MacPorts binary, but strangely... * Doesn't work: Installing ceres-solver from source MacPorts (using the -s option), compiling test_ceres.cc with /usr/bin/clang * Works: Building ceres-solver manually using /usr/bin/clang, compiling test_ceres.cc with macports clang 3.{4,5} * Works: Building ceres-solver manually using clang-mp-3.4, compiling test_ceres.cc with /usr/bin/clang * Fails to link: Building ceres-solver manually using clang-mp-3.5, compiling test_ceres.cc with with any compiler (including clang-mp-3.5!) In summary, manually building ceres-solver using cmake works in all cases I tested regardless of compiler (except the link failure case), while installing through MacPorts (from either binary or source) only works with clang-mp-3.{4,5} and not /usr/bin/clang. To me this suggests there's something wrong with how MacPorts configures ceres-solver, but if we decide that the bug lies upstream I'm happy to report the issue at https://code.google.com/p/ceres-solver/issues/list For reference, my "built-in" clang is: $ clang++ --version Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.2.0 Thread model: posix -- Ticket URL: <https://trac.macports.org/ticket/44627> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #44192: py-pyobjc-cocoa also needs the change made to py-pyobjc in #43586
by MacPorts 13 Aug '14

13 Aug '14

#44192: py-pyobjc-cocoa also needs the change made to py-pyobjc in #43586 -------------------------------+-------------------------------- Reporter: gnwiii@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: python setuptools | Port: py-pyobjc-cocoa -------------------------------+-------------------------------- A change needed to use setuptools 3.6 has not been applied by upstream, so a patch is required for macports installs. -- Ticket URL: <https://trac.macports.org/ticket/44192> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #36054: Feature request: reload action
by MacPorts 13 Aug '14

13 Aug '14

#36054: Feature request: reload action ----------------------------------+----------------------------------------- Reporter: mailtoarlo@… | Owner: macports-tickets@… Type: request | Status: new Priority: Low | Milestone: Component: base | Version: Keywords: | Port: ----------------------------------+----------------------------------------- When using ports that are started using launchd (e.g. apache2, mysql, php- fpm) the combination of {{{port unload}}} and {{{port load}}} is used to test configuration changes. Sadly typing this is long and cumbersome: {{{ sudo port unload apache2 && sudo port load apache2 }}} I suggest the {{{port reload}}} action that reduces the above to: {{{ sudo port reload apache2 }}} This is a common practice of "similar" commands like [http://manpages.ubuntu.com/manpages/hardy/en/man1/service.1.html service]. -- Ticket URL: <https://trac.macports.org/ticket/36054> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 13

[MacPorts] #37921: RFE: binutils's "notes" entry should specify which ports exactly it causes to fail to build
by MacPorts 13 Aug '14

13 Aug '14

#37921: RFE: binutils's "notes" entry should specify which ports exactly it causes to fail to build -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: binutils -------------------------+-------------------------------- Right now binutils comes with the following "notes" entry in its portfile: {{{ "Having ${name} installed will cause some other ports to\ fail to build. Consider uninstalling ${name}." }}} I'd like to know which ports exactly these are, or at least have a link to a Trac ticket or something, so I can be better informed about whether I should actually follow this advice to uninstall it or not. -- Ticket URL: <https://trac.macports.org/ticket/37921> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #44589: gstreamer{010, 1}-gst-plugins-good: make pulseaudio optional
by MacPorts 13 Aug '14

13 Aug '14

#44589: gstreamer{010,1}-gst-plugins-good: make pulseaudio optional -------------------------+------------------------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: gstreamer1-gst-plugins-good | gstreamer1-gst-plugins-good -------------------------+------------------------------------------------- Make `pulseaudio` support optional by disabling it, creating a new "`pulseaudio`" variant which turns on `PA` and adds the correct dependency and turning that on by default. -- Ticket URL: <https://trac.macports.org/ticket/44589> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #39065: Unable to upgrade Atlas on Snow Leopard 10.6.8
by MacPorts 13 Aug '14

13 Aug '14

#39065: Unable to upgrade Atlas on Snow Leopard 10.6.8 -------------------------+-------------------------------- Reporter: atif.azad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- Since I am behind a proxy, I ran the following commands (I am running OS X 10.6.8, and Xcode 3.2.6, macport 2.1.3: sudo port -d sync sudo port upgrade outdated ---> Computing dependencies for atlas ---> Building atlas Error: org.macports.build for port atlas returned: command execution failed Please see the log file for port atlas for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_math_atlas/atlas/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets -- Ticket URL: <https://trac.macports.org/ticket/39065> MacPorts <http://www.macports.org/> Ports system for OS X

1 39