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

[MacPorts] #33822: ghostscript @9.05_0 missing characters in loaded fonts
by MacPorts 25 Sep '13

25 Sep '13

#33822: ghostscript @9.05_0 missing characters in loaded fonts ------------------------------+--------------------------------------------- Reporter: rosgen@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: ghostscript ------------------------------+--------------------------------------------- Since upgrading ghostscript to @9.05_0 certain characters in postscript and pdf files are not displayed. Reverting to @9.04_1 fixes the problem. This is on a system running 10.6.8. Potentially relevant ports installed are: freetype @2.4.9_1+universal fontconfig @2.9.0_1+universal The problem occurs on the attached pdf file (and on other files). The text in the left margin is missing several characters. I've attached two screenshots: the behaviour in 0.94_1.png is the correct behaviour displayed by ghostscript @9.04_1, while the behaviour shown in 0.95_0.png is what ghostscript @9.05_0 displays. Other pdf viewers agree with the output of @9.04_1. The console output of @9.05_0 on this file is: {{{ GPL Ghostscript 9.05 (2012-02-08) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 20. Page 1 Loading NimbusRomNo9L-Regu font from /opt/local/share/ghostscript/9.05/Resource/Font/NimbusRomNo9L-Regu... 3438920 2049811 6310512 5008808 3 done. >>showpage, press <return> to continue<< }}} Whereas in @9.04_1 the output is: {{{ GPL Ghostscript 9.04 (2011-08-05) Copyright (C) 2011 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 20. Page 1 Loading NimbusRomNo9L-Regu font from /opt/local/share/ghostscript/9.04/Resource/Font/NimbusRomNo9L-Regu... 3559648 2160956 6127704 4819707 3 done. >>showpage, press <return> to continue<< }}} The only differences are in the numbers displayed regarding the loaded font. It seems like the font is either corrupt or being loaded incorrectly. -- Ticket URL: <https://trac.macports.org/ticket/33822> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #40575: Error: org.macports.build for port ompl returned: command execution failed
by MacPorts 25 Sep '13

25 Sep '13

#40575: Error: org.macports.build for port ompl returned: command execution failed ------------------------------------------+-------------------------------- Reporter: a0073763@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: ompl command execution error | Port: ompl ------------------------------------------+-------------------------------- Hi, I am trying to install OMPL on my MAC OSX 10.6.8 and I have installed the dependencies required (Boost, CMake, Python, PySide (& Qt4) & PyOpenGL) I executed the code "sudo port sync \; install ompl +app" and let my machine run. Some time later, the installation failed with the following message: {{{ Error: org.macports.build for port ompl returned: command execution failed Please see the log file for port ompl for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_ompl/ompl/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ompl failed }}} I have searched the ticket database and I realize my problem is similar to Ticket #39927. However, even after following through. It still does not work for me. Could you guys guide me as to how I can solve this? Thank you so much. -- Ticket URL: <https://trac.macports.org/ticket/40575> MacPorts <http://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #39096: ruby portgroup: fix universal builds
by MacPorts 25 Sep '13

25 Sep '13

#39096: ruby portgroup: fix universal builds --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: --------------------------+-------------------------------- Building rb-rmagick @2.13.2_1 non-universal works fine, but with the universal variant it fails: {{{ checking for stdint.h... no checking for sys/types.h... no checking for wand/MagickWand.h... no Can't install RMagick 2.13.2. Can't find MagickWand.h. }}} These headers all exist; the problem is how Ruby checks for them. In ext/RMagick/mkmf.log we see the real problem: {{{ have_header: checking for stdint.h... -------------------- no "/usr/bin/clang -E -I. -I/opt/local/lib/ruby/1.8/x86_64-darwin12 -I/opt/local/var/macports/build/_Users_rschmidt_macports_dports_ruby_rb- rmagick/rb-rmagick/work/RMagick-2.13.2/ext/RMagick -I/opt/local/include -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/opt/local/include/ImageMagick-6 -pipe -Os -arch x86_64 -arch i386 -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/opt/local/include/ImageMagick-6 conftest.c -o conftest.i" clang: error: cannot use 'cpp-output' output with multiple -arch options checked program was: /* begin */ 1: #include <stdint.h> /* end */ }}} The compiler is being called with `-E`, meaning pre-processor mode, but for some reason the `-arch` flags, which are not appropriate for use with a pre-processor, are still being supplied, causing the error. RMagick isn't doing anything special; it's using the standard ruby `have_header()` check. According to the Ruby source code, `have_header()` calls `try_cpp()`, which in turn calls `cpp_command()`. And `cpp_command()` runs `Config::expand("$(CPP) #$INCFLAGS #$CPPFLAGS #$CFLAGS #{opt} #{CONFTEST_C} #{outfile}", conf)`—deliberately including `$CFLAGS`, which in MacPorts by default contains `-arch` flags. The developers of Ruby seem to be aware that `-arch` flags should not be passed to the C pre-processor; I found an old discussion about that. But they've taken the unorthodox approach of defining a new environment variable `ARCH_FLAG` which they expect packagers to set, instead of including `-arch` flags in `CFLAGS`, `CXXFLAGS`, `LDFLAGS` etc. I don't know why it's called `ARCH_FLAG` and not `ARCH_FLAGS` or what happens if multiple `-arch` flags are included. In MacPorts we seem to be aware of the `ARCH_FLAG` variable; the ruby port already uses it to build itself, and it ensures only one `-arch` flag is in it by using the muniversal portgroup. But we still need a solution for other Ruby software that uses the ruby-1.0 portgroup. -- Ticket URL: <https://trac.macports.org/ticket/39096> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #38916: ffmpeg-devel: add libavresample support
by MacPorts 25 Sep '13

25 Sep '13

#38916: ffmpeg-devel: add libavresample support -------------------------+-------------------------------- Reporter: coax@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ffmpeg-devel -------------------------+-------------------------------- Please add the configure option --enable-avresample, or at least make it a variant. I've built it using a local portfile and had no problems. -- Ticket URL: <https://trac.macports.org/ticket/38916> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #39126: Requesting libvpx_vp9 for ffmpeg
by MacPorts 25 Sep '13

25 Sep '13

#39126: Requesting libvpx_vp9 for ffmpeg -------------------------+-------------------------------- Reporter: scott@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.1.3 Keywords: | Port: ffmpeg -------------------------+-------------------------------- http://news.cnet.com/8301-1023_3-57584706-93/google-urges-fast-adoption- of-vp9-video-compression/ http://ffmpeg.org/pipermail/ffmpeg-cvslog/2013-January/059366.html VP8 was great, but VP9 will be fine -- Ticket URL: <https://trac.macports.org/ticket/39126> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #40582: Sleuthkit to 4.1.1
by MacPorts 25 Sep '13

25 Sep '13

#40582: Sleuthkit to 4.1.1 ---------------------------------+-------------------------------- Reporter: jessekornblum@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: haspatch maintainer | Port: sleuthkit ---------------------------------+-------------------------------- Please update Sleuthkit to version 4.1.1 using the attached diff. -- Ticket URL: <https://trac.macports.org/ticket/40582> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #40414: phpmyadmin-4.06 has been released
by MacPorts 25 Sep '13

25 Sep '13

#40414: phpmyadmin-4.06 has been released -------------------------+-------------------------------- Reporter: drjesacco@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: phpmyadmin -------------------------+-------------------------------- Version 4.06 of phpmyadmin has been released. I tweaked the Portfile for version 4.05: * bumped version to 4.06 * updated checksums * added php55 to the foreach loop * added && ![variant_isset php55] to the default_variants check I built the package using the php55 variant. Seems OK. -Joseph -- Ticket URL: <https://trac.macports.org/ticket/40414> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #40578: GNU Radio Companion will not run
by MacPorts 25 Sep '13

25 Sep '13

#40578: GNU Radio Companion will not run --------------------------+-------------------------------- Reporter: j_molineux@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: gnuradio --------------------------+-------------------------------- I installed gnuradio on a macbook pro running mountainlion. This install seemed to be successful. However, when i try to start gnuradio-companion --> sh: gnuradio-companion, I get the errors shown in the attached file. -- Ticket URL: <https://trac.macports.org/ticket/40578> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #40573: ffmpeg-2.0.1 should force opencv to rebuild
by MacPorts 24 Sep '13

24 Sep '13

#40573: ffmpeg-2.0.1 should force opencv to rebuild ---------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: ffmpeg ---------------------+-------------------------------- After installing ffmpeg... if opencv is installed... opencv does not recompile, so opencv continues to point to... ldd *dylib | grep 54 /opt/local/lib/libavcodec.54.dylib (compatibility version 54.0.0, current version 54.92.100) /opt/local/lib/libavformat.54.dylib (compatibility version 54.0.0, current version 54.63.104) /opt/local/lib/libavcodec.54.dylib (compatibility version 54.0.0, current version 54.92.100) /opt/local/lib/libavformat.54.dylib (compatibility version 54.0.0, current version 54.63.104) /opt/local/lib/libavcodec.54.dylib (compatibility version 54.0.0, current version 54.92.100) /opt/local/lib/libavformat.54.dylib (compatibility version 54.0.0, current version 54.63.104) After ffmpeg-2.0.1 installs, all these are removed + version is bumped to .55 so all manner of havoc ensues... Tried to fix via - port upgrade -n --force opencv - which now throws some sort of build error in lib-xine, no doubt do to something munged by skipping rebuild of all dependencies. Unsure of temp fix... best for port maintainer to just fix the Portfile to correctly rebuild opencv. Hum... wonder if this has something to do with XCode-5.0 which seems to have been working correctly. I'll remove entire MacPorts + rebuild + update this ticket as to whether this works or fails. -- Ticket URL: <https://trac.macports.org/ticket/40573> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #40574: ld64 @136 upgrade failure
by MacPorts 24 Sep '13

24 Sep '13

#40574: ld64 @136 upgrade failure ----------------------+-------------------------------- Reporter: karel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: tar ld64 | Port: ld64 ----------------------+-------------------------------- When run as root, port upgrade ld64 fails. Port clean doesn't help and AFAIK the directory settings are OK, other upgrades succeed without a problem. {{{ ---> Computing dependencies for ld64 ---> Extracting ld64 Error: org.macports.extract for port ld64 returned: command execution failed Please see the log file for port ld64 for details: /opt/local/var/macports/logs/_Volumes_HD_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ld64/ld64/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets }}} The log is attached. This is somehow due to incorrect directory settings; tar extraction barfs. Abbreviated output when -d flag is given follows: {{{ DEBUG: egid changed to: 501 DEBUG: euid changed to: 502 DEBUG: Skipping completed org.macports.archivefetch (ld64) DEBUG: Privilege de-escalation not attempted as not running as root. DEBUG: Skipping completed org.macports.fetch (ld64) DEBUG: Privilege de-escalation not attempted as not running as root. DEBUG: Skipping completed org.macports.checksum (ld64) DEBUG: Privilege de-escalation not attempted as not running as root. DEBUG: extract phase started at Tue Sep 24 17:28:20 CEST 2013 ---> Extracting ld64 DEBUG: Executing org.macports.extract (ld64) ---> Extracting ld64-136.tar.gz DEBUG: setting option extract.args to '/opt/local/var/macports/distfiles/ld64/ld64-136.tar.gz' DEBUG: Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_Volumes_HD_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ld64/ld64/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.8' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_Volumes_HD_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ld64/ld64/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/ld64/ld64-136.tar.gz' | /usr/bin/gnutar --no-same-owner -xf -' DEBUG: Executing command line: cd "/opt/local/var/macports/build/_Volumes_HD_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ld64/ld64/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/ld64/ld64-136.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - /usr/bin/gnutar: ld64-136: Cannot mkdir: Operation not permitted /usr/bin/gnutar: ld64-136/APPLE_LICENSE: Cannot open: No such file or directory /usr/bin/gnutar: ld64-136/doc: Cannot mkdir: No such file or directory /usr/bin/gnutar: ld64-136/doc/design: Cannot mkdir: No such file or directory /usr/bin/gnutar: ld64-136/doc/design/linker.html: Cannot open: No such file or directory . . . usr/bin/gnutar: ld64-136/src/other/machochecker.cpp: Cannot open: No such file or directory /usr/bin/gnutar: ld64-136/src/abstraction: Cannot mkdir: No such file or directory /usr/bin/gnutar: ld64-136/src/abstraction/MachOTrie.hpp: Cannot open: No such file or directory /usr/bin/gnutar: ld64-136/src/abstraction/FileAbstraction.hpp: Cannot open: No such file or directory /usr/bin/gnutar: ld64-136/src/abstraction/MachOFileAbstraction.hpp: Cannot open: No such file or directory /usr/bin/gnutar: Error exit delayed from previous errors Command failed: cd "/opt/local/var/macports/build/_Volumes_HD_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ld64/ld64/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/ld64/ld64-136.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - Exit code: 2 Error: org.macports.extract for port ld64 returned: command execution failed DEBUG: Error code: NONE DEBUG: Backtrace: command execution failed while executing "$procedure $targetname" Warning: targets not executed for ld64: org.macports.install org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot Please see the log file for port ld64 for details: /opt/local/var/macports/logs/_Volumes_HD_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ld64/ld64/main.log DEBUG: couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory while executing "open [file join $dir tclIndex]" 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/40574> MacPorts <http://www.macports.org/> Ports system for OS X

1 3