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

[MacPorts] #49569: selfupdate failed on El Capitan
by MacPorts 01 Nov '16

01 Nov '16

#49569: selfupdate failed on El Capitan ----------------------------+-------------------------------- Reporter: axknightroad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ----------------------------+-------------------------------- I installed MacPorts using the OS X package installer today. but it failed when I update using port -v selfupdate. {{{ $ sudo port -v selfupdate ---> Updating MacPorts base sources using rsync Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 1 Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed }}} but the commmand below is worked. {{{ $ sudo /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs }}} -- Ticket URL: <https://trac.macports.org/ticket/49569> MacPorts <https://www.macports.org/> Ports system for OS X

1 12

[MacPorts] #46821: Failed to configure sshfs
by MacPorts 01 Nov '16

01 Nov '16

#46821: Failed to configure sshfs -------------------------+-------------------------------- Reporter: hfyangpku@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -------------------------+-------------------------------- While installing sshfs, I got the following error: {{{ ---> Configuring sshfs Error: Failed to configure sshfs, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_sshfs/sshfs/work /sshfs-fuse-2.5/config.log Error: org.macports.configure for port sshfs returned: configure failure: command execution failed Please see the log file for port sshfs for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_sshfs/sshfs/main.log }}} In the config.log file, there are 20 errors before it complain the number of errors and stop configuring. All of the errors happen in the same file. The very first one is: {{{ configure:3024: /usr/bin/clang -o conftest -pipe -Os -arch x86_64 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 conftest.c >&5 In file included from conftest.c:11: /opt/local/include/stdio.h:252:63: error: expected function body after function declarator int fprintf(FILE * __restrict, const char * __restrict, ...) __DARWIN_LDBL_COMPAT(fprintf) __printflike(2, 3); ^ }}} -- Ticket URL: <https://trac.macports.org/ticket/46821> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #47249: hmake @3.14_3 (devel) Failed to build hmake
by MacPorts 31 Oct '16

31 Oct '16

#47249: hmake @3.14_3 (devel) Failed to build hmake ------------------------------+-------------------------------- Reporter: abigail.lauren@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: hmake, haskell | Port: hmake ------------------------------+-------------------------------- 'hmake' has failed to build, and other closed tickets on this topic haven't given me any solutions. I've attached a copy of the hmake/main.log. Here's what the command line spits out (as a root user): > port install hmake >---> Computing dependencies for hmake >---> Fetching archive for hmake >---> Attempting to fetch hmake-3.14_3+ghc.darwin_14.x86_64.tbz2 from http://packages.macports.org/hmake >---> Attempting to fetch hmake-3.14_3+ghc.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/hmake >---> Attempting to fetch hmake-3.14_3+ghc.darwin_14.x86_64.tbz2 from >http://nue.de.packages.macports.org/macports/packages/hmake >---> Fetching distfiles for hmake >---> Verifying checksums for hmake >---> Extracting hmake >---> Applying patches to hmake >---> Configuring hmake >---> Building hmake >Error: org.macports.build for port hmake returned: command execution failed >Please see the log file for port hmake for details: >/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_hmake/hmake/main.lo g >To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets >Error: Processing of port hmake failed I'm using MacPorts 2.3.3, my ports are up-to-date, and I've tried port clean hmake and then installing again. I need hmake to build scientific software for work. Help please? Thank you! -- Ticket URL: <https://trac.macports.org/ticket/47249> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #45478: Update request: New version of iStumbler available (122 vs 99)
by MacPorts 28 Oct '16

28 Oct '16

#45478: Update request: New version of iStumbler available (122 vs 99) ----------------------+-------------------------------- Reporter: magill@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: ----------------------+-------------------------------- Mac Ports installs iStumbler version 99. When "check for updates" runs, a pop-up with a special yellow box indicates that a new update (122) is available, but that version 99 users need to download it explicitly. Both work. Version 122 has several enhancements. -- Ticket URL: <https://trac.macports.org/ticket/45478> MacPorts <https://www.macports.org/> Ports system for OS X

1 11

[MacPorts] #46660: Proposal: Update rmtrash
by MacPorts 28 Oct '16

28 Oct '16

#46660: Proposal: Update rmtrash --------------------------+-------------------------------- Reporter: sebikeller@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: rmtrash | Port: rmtrash --------------------------+-------------------------------- The rmtrash port has not been updated since 2005, so I updated the utility and also corrected a nasty naming problem ("filename Copy10" became "filename copy 111" became "filename Copy1112" etc.) u can find the updated code here: https://github.com/beatjunky99/rmtrash- for-Mac-OS-X Still needs some testing on older Mac OS X versions. So would be glad to hear from people reading this if they find a problem. -- Ticket URL: <https://trac.macports.org/ticket/46660> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #49498: Switching to a mirror causes a complete rebuild of the port index
by MacPorts 27 Oct '16

27 Oct '16

#49498: Switching to a mirror causes a complete rebuild of the port index ----------------------------+--------------------- Reporter: lpancescu@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+--------------------- I switched to a local mirror as a workaround to the network problems described in bug #49452. The rsync-ing was very fast, but the lack of an index made mirror switching pretty annoying: the first "port selfupdate" thinks that every single port is new, and rebuilds the entire index. So mirror users have to wait 30+ minutes for the index to build (see bug #49050) not once, but //two times//. I was curious why that happens, so I base.tar from three different mirrors (sea.us.rsync.macports.org, lil.fr.rsync.macports.org and nue.de.rsync.macports.org) Since MacPorts 2.3.4 was released some time ago, I expected the archives to be identical. They aren't, although the file size is the same: diff reports every archive as binary different from the other two. The timestamps also differ: 20:02, 23:02, respectively 22:02 - all from today. After unpacking the archives into different directories, I used FileMerge to directly compare the directories: every single file is identical, but the tar archives aren't. So I redirected the output of "ls -lR" in each directory to a different file, then ran "diff -u" to compare them. Here's a part of the result: {{{ -rw-r--r-- 1 laur staff 1922 May 24 2014 pkg_mkindex.sh.in -drwxr-xr-x 8 laur staff 272 Oct 28 19:31 port -drwxr-xr-x 35 laur staff 1190 Oct 28 19:31 port1.0 -drwxr-xr-x 4 laur staff 136 Oct 28 19:31 programs -drwxr-xr-x 36 laur staff 1224 Oct 28 19:31 registry2.0 +drwxr-xr-x 8 laur staff 272 Oct 28 22:31 port +drwxr-xr-x 35 laur staff 1190 Oct 28 22:31 port1.0 +drwxr-xr-x 4 laur staff 136 Oct 28 22:31 programs +drwxr-xr-x 36 laur staff 1224 Oct 28 22:31 registry2.0 drwxr-xr-x 11 laur staff 374 May 24 2014 tclobjc1.0 drwxr-xr-x 19 laur staff 646 May 24 2014 thread2.6 --rwxr-xr-x 1 laur staff 4311 Oct 28 19:30 upgrade_sources_conf_default.tcl +-rwxr-xr-x 1 laur staff 4311 Oct 28 22:30 upgrade_sources_conf_default.tcl -rwxr-xr-x 1 laur staff 4265 May 24 2014 upgrade_sources_conf_default.tcl.in }}} It seems that the timestamps of //every single directory// and of the few generated files (files like Makefile probably generated from Makefile.in) are set to the timestamp of the archive on the mirror. Perhaps the "fresh" directory timestamps are the reason for the index being rebuilt, and that each mirror runs some sort of build locally, at least daily, even when nothing has actually changed? I should have downloaded ports.tar.gz, to be sure, but it's quite big. -- Ticket URL: <https://trac.macports.org/ticket/49498> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #50218: Error: Failed to install doxygen
by MacPorts 26 Oct '16

26 Oct '16

#50218: Error: Failed to install doxygen ----------------------+-------------------------------- Reporter: justin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ----------------------+-------------------------------- I'm new to mac and linux- any help would be appreciated. My OS isEl Capitan Here is the error I get Error: org.macports.configure for port doxygen returned: configure failure: command execution failed Error: Failed to install doxygen Please see the log file for port doxygen for details: Here is the log. version:1 :debug:main Attempting ln -sf /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/textproc/doxygen/work :debug:main changing euid/egid - current euid: 0 - current egid: 0 :debug:main egid changed to: 501 :debug:main euid changed to: 502 :debug:main Executing org.macports.main (doxygen) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.archivefetch (doxygen) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.fetch (doxygen) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.checksum (doxygen) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.extract (doxygen) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.patch (doxygen) :debug:main Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Mon Jan 4 20:28:44 EST 2016 :notice:configure ---> Configuring doxygen :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Executing proc-pre-org.macports.configure-configure-1 :debug:configure Executing proc-pre-org.macports.configure-configure-2 :debug:configure Executing org.macports.configure (doxygen) :debug:configure Environment: CC='/usr/bin/clang' CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/.CC_PRINT_OPTIONS' CFLAGS='-pipe -Os' CPATH='/opt/local/include' CPPFLAGS='-I/opt/local/include' CXX='/usr/bin/clang++' CXXFLAGS='-pipe -Os -stdlib=libc++' F77FLAGS='-m64' F90FLAGS='-pipe -Os -m64' FCFLAGS='-pipe -Os -m64' FFLAGS='-pipe -Os' INSTALL='/usr/bin/install -c' LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.11' OBJC='/usr/bin/clang' OBJCFLAGS='-pipe -Os' OBJCXX='/usr/bin/clang++' OBJCXXFLAGS='-pipe -Os -stdlib=libc++' :debug:configure Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10" && /opt/local/bin/cmake -DCMAKE_INSTALL_PREFIX=/opt/local -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON -DCMAKE_INSTALL_RPATH=/opt/local/lib -DCMAKE_INSTALL_NAME_DIR=/opt/local/lib -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_MODULE_PATH=/opt/local/share/cmake/Modules -DCMAKE_FIND_FRAMEWORK=LAST -Wno-dev -DCMAKE_C_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.11" -DCMAKE_OSX_SYSROOT="/" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10' :debug:configure Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10" && /opt/local/bin/cmake -DCMAKE_INSTALL_PREFIX=/opt/local -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON -DCMAKE_INSTALL_RPATH=/opt/local/lib -DCMAKE_INSTALL_NAME_DIR=/opt/local/lib -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_MODULE_PATH=/opt/local/share/cmake/Modules -DCMAKE_FIND_FRAMEWORK=LAST -Wno-dev -DCMAKE_C_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.11" -DCMAKE_OSX_SYSROOT="/" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10 :info:configure -- Could NOT find Threads (missing: Threads_FOUND) :info:configure CMake Error at cmake/FindIconv.cmake:121 (MESSAGE): :info:configure Unable to determine iconv() signature :info:configure Call Stack (most recent call first): :info:configure CMakeLists.txt:64 (find_package) :info:configure :info:configure :info:configure -- Configuring incomplete, errors occurred! :info:configure See also "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/CMakeFiles/CMakeOutput.log". :info:configure See also "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/CMakeFiles/CMakeError.log". :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10" && /opt/local/bin/cmake -DCMAKE_INSTALL_PREFIX=/opt/local -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON -DCMAKE_INSTALL_RPATH=/opt/local/lib -DCMAKE_INSTALL_NAME_DIR=/opt/local/lib -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_MODULE_PATH=/opt/local/share/cmake/Modules -DCMAKE_FIND_FRAMEWORK=LAST -Wno-dev -DCMAKE_C_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.11" -DCMAKE_OSX_SYSROOT="/" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10 :info:configure Exit code: 1 :error:configure org.macports.configure for port doxygen returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "portconfigure::configure_main org.macports.configure" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:configure Warning: targets not executed for doxygen: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :error:configure Failed to install doxygen :debug:configure Registry error: getopt not registered as installed & active. invoked from within "registry_active $subport" invoked from within "$workername eval registry_active \$subport" :notice:configure Please see the log file for port doxygen for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/main.log -- Ticket URL: <https://trac.macports.org/ticket/50218> MacPorts <https://www.macports.org/> Ports system for OS X

1 14

[MacPorts] #49764: babl @0.1.14 should not require clang-3.4
by MacPorts 25 Oct '16

25 Oct '16

#49764: babl @0.1.14 should not require clang-3.4 -------------------------+-------------------------------- Reporter: braumann@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: PPC | Port: babl -------------------------+-------------------------------- {{{ $ sudo port info --pretty --depends babl Build Dependencies: clang-3.4 }}} As you may know, {{{clang-3.4}}} is not functional on PPC platforms. So I wonder if instead {{{gcc5}}} could be generally used, as {{{ $ sudo port -s install babl configure.compiler=macports-gcc-5 }}} successfully works even on PPC? -- Ticket URL: <https://trac.macports.org/ticket/49764> MacPorts <https://www.macports.org/> Ports system for OS X

1 39

[MacPorts] #45712: xorg-libXt-1.1.4_0 links shared libs with -flat_namespace on Yosemite
by MacPorts 24 Oct '16

24 Oct '16

#45712: xorg-libXt-1.1.4_0 links shared libs with -flat_namespace on Yosemite ------------------------+-------------------------------- Reporter: jhowarth@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: xorg-libXt ------------------------+-------------------------------- otool -hv /opt/local/lib/libXt.6.dylib /opt/local/lib/libXt.6.dylib: Mach header magic cputype cpusubtype caps filetype ncmds sizeofcmds flags MH_MAGIC_64 X86_64 ALL 0x00 DYLIB 17 1872 DYLDLINK NO_REEXPORTED_DYLIBS reveals that xorg-libXt-1.1.4_0 built on Yosemite is linking its shared libraries with "-flat_namespace" as seen from the missing TWOLEVEL flag expected from "-undefined dynamic_lookup". -- Ticket URL: <https://trac.macports.org/ticket/45712> MacPorts <https://www.macports.org/> Ports system for OS X

1 28

[MacPorts] #50463: DDD 3.3.12 (i386-apple-darwin15.2.0) gets Xt error
by MacPorts 24 Oct '16

24 Oct '16

#50463: DDD 3.3.12 (i386-apple-darwin15.2.0) gets Xt error ---------------------------------------------+----------------------------- Reporter: ewout+keyword+macports.8d331b@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Keywords: xorg-libXt xorg-libXaw | Version: 2.3.4 | Port: DDD ---------------------------------------------+----------------------------- Hi, after upgrading to El Capitan recently, I got this error in a previously working DDD setup, after upgrading a few X11 ports: ---- Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Warning: No type converter registered for 'String' to 'Orientation' conversion. Error: Unresolved inheritance operation Xt error (Unresolved inheritance operation). Oops! You have found a bug in DDD. If you can reproduce this bug, please send a bug report to <ddd(a)gnu.org>, giving a subject like DDD 3.3.12 (i386-apple-darwin15.2.0) gets Xt error To enable us to fix the bug, you should include the following information: * What you were doing to get this message. Report all the facts. * The contents of the `~/.ddd/log' file as generated by this session. Please read also the section "Reporting Bugs" in the DDD manual. We thank you for your support. ddd: Cannot save options ---- I searched through trac.macports.org and found out this error was last detected in 2009 on OS X Tiger. Previously I was running Snow Leopard and I didn't have any problems there. A little research showed that the culprit for this error most likely is xorg-libXaw, because that after upgrading that port, DDD would not execute properly anymore. However, I am no expert in X11 so I could not find out exactly what dependency was missing. The DDD code itself is archaic, but the program is very useful - I use it as a GUI frontend to arm-none-eabi-gdb for embedded software development. I can confirm that DDD3.3.12 works on other X11 platforms without a problem (FreeBSD 10.2 and CentOS Linux). -- Ticket URL: <https://trac.macports.org/ticket/50463> MacPorts <https://www.macports.org/> Ports system for OS X

1 5