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

[MacPorts] #46239: qca and qca-ossl adaptations to qt4-mac +concurrent
by MacPorts 31 Jan '16

31 Jan '16

#46239: qca and qca-ossl adaptations to qt4-mac +concurrent -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: qca, qca-ossl -------------------------+-------------------------------- port:qca and port:qca-ossl use hard-coded paths to Qt4 install locations, instead of using the variables provided by the qt4 PortGroup. That breaks installation when qt4-mac is installed +concurrent. Patches are attached to this ticket. -- Ticket URL: <https://trac.macports.org/ticket/46239> MacPorts <https://www.macports.org/> Ports system for OS X

1 21

[MacPorts] #45915: qt5-creator-mac @3.2.2_0 fails to build
by MacPorts 31 Jan '16

31 Jan '16

#45915: qt5-creator-mac @3.2.2_0 fails to build -------------------------+-------------------------------- Reporter: starkhalo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: qt5-creator-mac -------------------------+-------------------------------- log file attached -- Ticket URL: <https://trac.macports.org/ticket/45915> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #48562: Update qwt to 6.1.2
by MacPorts 31 Jan '16

31 Jan '16

#48562: Update qwt to 6.1.2 -----------------------+-------------------------------- Reporter: ghweber@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: qwt -----------------------+-------------------------------- Hi, The attached Portfile adds a qwt61 variant (replacing the qwt-devel variant that installs an outdated release 6.1 release candidate), which installs the current Qwt 6.1.2 The following changes are necessary: - Update Portfile according to attached patch - Remove: files/patch-designer_designer.pro.610rc3.diff files/patch- qwtbuild.pri.610rc3.diff files/patch-qwtconfig.pri.610rc3.diff files /patch-qwtfunctions.pri.610rc3.diff - Add attached: files/patch-designer_designer.pro.61.diff files/patch- qwtbuild.pri.61.diff files/patch-qwtconfig.pri.61.diff A few comments: - When trying to update patch-qwtfunctions.pri.61.diff from the old release candidate build, linking failed. Omitting the patch seems to do the right thing. - I am not sure if I need to add something to ensure that existing installations of qwt-devel get upgraded to qwt61. - If I am not mistaken, the variants "debug" and "examples" do not do anything and could be removed. Gunther -- Ticket URL: <https://trac.macports.org/ticket/48562> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #47560: meld: version bump to @3.12.3 (Portfile attached)
by MacPorts 30 Jan '16

30 Jan '16

#47560: meld: version bump to @3.12.3 (Portfile attached) -----------------------+-------------------------------- Reporter: khepler@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: meld -----------------------+-------------------------------- Stable version of Meld is v3.12.3, but current port is v1.8.6. The attached Portfile for v3.12.3 is the result of trial and error. Someone more competent than myself needs to review it. Also, without a GTK3 icon set most of the icons are the generic missing icon image. I solved that by installing adwaita-icon-theme (as a dependency of gnome-themes-standard). I don't like the idea of forcing a specific theme. What's the best way to resolve the missing icons? -- Ticket URL: <https://trac.macports.org/ticket/47560> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #46238: co-installable qt4-mac and qt5-mac step1 : qt4-mac +concurrent
by MacPorts 30 Jan '16

30 Jan '16

#46238: co-installable qt4-mac and qt5-mac step1 : qt4-mac +concurrent -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: qt4-mac -------------------------+-------------------------------- Lots has been said about this on the users and dev MLs, but here it is finally, a draft Portfile that explores a way to make qt4-mac and qt5-mac co-installable, starting with qt4-mac . At the moment this is done as a non-optional variant, +concurrent, but the goal would of course be to merge that variant into the port's default behaviour. My intention is to tackle qt5-mac after we have reached some form of consensus about qt4-mac. The basic logic could have been very simple: instead of setting the Qt root directory `qt_dir` to ${prefix}, we set it to `${prefix}/libexec/qt4`. However, since the current version already installs a good number of components in Qt-version-specific places that approach would have been overkill. I'm thus proposing to keep those paths identical, to reduce the amount of breakage in dependent ports that for some unfathomable reason do not use the variables defined in the qt4 PortGroup. Changes to the PortGroup file, qt4-1.0.tcl: Where we had {{{ set qt_dir ${prefix} set qt_docs_dir ${qt_dir}/share/doc/${qt_name} set qt_plugins_dir ${qt_dir}/share/${qt_name}/plugins set qt_mkspecs_dir ${qt_dir}/share/${qt_name}/mkspecs set qt_imports_dir ${qt_dir}/share/${qt_name}/imports set qt_includes_dir ${qt_dir}/include set qt_libs_dir ${qt_dir}/lib set qt_frameworks_dir ${qt_dir}/Library/Frameworks set qt_bins_dir ${qt_dir}/bin set qt_data_dir ${qt_dir}/share/${qt_name} set qt_translations_dir ${qt_dir}/share/${qt_name}/translations set qt_sysconf_dir ${qt_dir}/etc/${qt_name} set qt_examples_dir ${qt_dir}/share/${qt_name}/examples set qt_demos_dir ${qt_dir}/share/${qt_name}/demos set qt_cmake_module_dir ${qt_dir}/share/cmake/Modules set qt_qmake_cmd ${qt_dir}/bin/qmake set qt_moc_cmd ${qt_dir}/bin/moc set qt_uic_cmd ${qt_dir}/bin/uic set qt_lrelease_cmd ${qt_dir}/bin/lrelease }}} We get {{{ set qt_dir ${prefix}/libexec/${qt_name} set qt_docs_dir ${prefix}/share/doc/${qt_name} set qt_plugins_dir ${prefix}/share/${qt_name}/plugins set qt_mkspecs_dir ${prefix}/share/${qt_name}/mkspecs set qt_imports_dir ${prefix}/share/${qt_name}/imports set qt_includes_dir ${prefix}/include/${qt_name} set qt_libs_dir ${qt_dir}/lib set qt_frameworks_dir ${qt_dir}/Library/Frameworks set qt_bins_dir ${qt_dir}/bin set qt_data_dir ${prefix}/share/${qt_name} set qt_translations_dir ${prefix}/share/${qt_name}/translations set qt_sysconf_dir ${prefix}/etc/${qt_name} set qt_examples_dir ${prefix}/share/${qt_name}/examples set qt_demos_dir ${prefix}/share/${qt_name}/demos # no need to change the cmake_module_dir, though I'd have preferred to # put it into ${prefix}/lib/cmake as qt5-mac also does, and which is the place Linux uses set qt_cmake_module_dir ${prefix}/share/cmake/Modules set qt_qmake_cmd ${qt_dir}/bin/qmake set qt_moc_cmd ${qt_dir}/bin/moc set qt_uic_cmd ${qt_dir}/bin/uic set qt_lrelease_cmd ${qt_dir}/bin/lrelease }}} `qt_apps_dir` remains the same, of course, as does `qt_pkg_config_dir` for obvious reasons (but we'll put a symlink to ${prefix/lib/pkgconfig into ${qt_libs_dir} because that's where installers will try to put their `.pc` files). We'll also put symlinks to `qt_qmake_cmd`, `qt_moc_cmd` etc. into ${prefix}/bin (qmake4.8, moc4.8 etc) ... and if port:qtchooser is installed there will also be ${prefix}/bin/qmake (etc) that will resolve the appropriate qmake (etc) version depending on the options it is invoked with and/or the configured defaults. Qt client ports will of course need to see the correct values for the above variables, so the variant is declared in the PortGroup file, and a bit of logic introduced that will check for ${prefix}/libexec/${qt_name}/bin/qmake to set a global state variable even if a port is not installed explicitly as +concurrent. This is a convenience feature so that we don't have to specify the variant during testing (and then reinstall everything without once +concurrent becomes the default). A note is printed about this (which should happen only once, but I must not understand something about the scope of global variables). Changes to the Portfile itself When I started I thought I'd do good to separate a few base definitions from the brunt of the Portfile, making Portfile a tiny skeleton that included the much larger Portfile.qt4 payload. There no longer is any reason to do so, but I kept this for now because it allows to modify the main file at will without change to the Portfile hash tag which determines if an automatic `port clean` has to be done. The main points of interest in Portfile(.qt4) are: - conflicts declarations are made only when concurrent isn't set - a symlink is made so that client ports installing a pkgconfig file do so in the proper location and not under the new ${qt_libs_dir} - links are made to expose qmake (moc, ...) in ${prefix}/bin (qmake4.8, moc4.8, ...) - A subport qt4-mac-transitional is defined. This is a pure convenience construct that only creates a number of symlinks in the destroot phase. Those symlinks make the qt4-mac+concurrent frameworks and shared libraries appear where they used to be, in order to remove the need to rebuild all Qt client ports (including all of KDE4) immediately after installing +concurrent. Indeed, the post-install rev-upgrade phase reports 0 broken ports when the install is done correctly. This subport of course introduces conflicts with other qt ports. Out-commented bits remain of the older +libsymlinks variant that did the same thing as the subport. - I introduced an optional +htmldocs variant that has to be set to install the html documentation. Since that amounts to almost 220Mb of lots of smallish files, they are in fact deleted from the source directory in the pre-destroot phase in order to speed up the destroot phase. Not the nicest approach, but since the official dogma is to do a port clean before installing a port with a different variants selection it shouldn't be too problematic. - I'm still working on another variant, +noexceptions, which build Qt with -fno-exceptions. This is supposed to be ABI compatible, and reduce memory overhead for a feature that is mostly unused. KDE apparently requires exceptions support in QtConcurrent, so I have to figure out if it's possible to reintroduce it there and not in the rest of QtCore. How to install: I'd advise to - port -v configure qt4-mac +concurrent check if everything looks fine - port -v destroot qt4-mac +concurrent (some time later...) check if everything looks fine in the destroot dir If all went well, do - sudo port -v -k install qt4-mac +concurrent [qt4-mac-transitional] qt4-mac-transitional ought not install when qt4-mac has not been installed with +concurrent, but can best be installed in the same command that installs qt4-mac+concurrent, to avoid issues during rev-upgrade. -- Ticket URL: <https://trac.macports.org/ticket/46238> MacPorts <https://www.macports.org/> Ports system for OS X

1 15

[MacPorts] #46251: jack @0.121.3_1: Update needed
by MacPorts 29 Jan '16

29 Jan '16

#46251: jack @0.121.3_1: Update needed -------------------------+-------------------------------- Reporter: keybounce@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: jack -------------------------+-------------------------------- Jack is currently at 0.124.1 upstream. Jack 2 is not currently in macports; it's at version 1.9.10. -- Ticket URL: <https://trac.macports.org/ticket/46251> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47987: djview @4.10 fails to build on PPC 10.5
by MacPorts 28 Jan '16

28 Jan '16

#47987: djview @4.10 fails to build on PPC 10.5 ----------------------+-------------------------------- Reporter: reeskm@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: djview ----------------------+-------------------------------- I can't get djview 4.10 to build. I have 4.9 installed and working great. It fails when linking djview.app/Contents/MacOS/djview with a no such file and "invalid arch name : -o" Attached is the log output with -v -- Ticket URL: <https://trac.macports.org/ticket/47987> MacPorts <https://www.macports.org/> Ports system for OS X

1 32

[MacPorts] #47226: darktable
by MacPorts 28 Jan '16

28 Jan '16

#47226: darktable ------------------------+-------------------------------- Reporter: elatllat@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: darktable | Port: darktable ------------------------+-------------------------------- {{{ sudo port install darktable sudo port clean darktable sudo port install darktable }}} {{{ :debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found :debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found :debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found :info:configure CMake Error at /opt/local/share/cmake-3.1/Modules/FindPackageHandleStandardArgs.cmake:138 (message): :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_graphics_darktable/darktable/work/darktable-1.1.2/build/CMakeFiles/CMakeError.log". :info:configure ./build.sh: line 242: syntax error near unexpected token `&&' :error:configure org.macports.configure for port darktable returned: configure failure: command execution failed :debug:configure Error code: NONE }}} {{{ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_darktable/darktable/work/darktable-1.1.2/build/CMakeFiles/CMakeTmp/src.c:2:10: fatal error: 'omp.h' file not found 1 error generated. gmake[1]: *** [CMakeFiles/cmTryCompileExec1708053017.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec1708053017/fast] Error 2 clang: error: no such file or directory: '/openmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec47210223.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec47210223/fast] Error 2 clang: error: unknown argument: '-Qopenmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec1456542323.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec1456542323/fast] Error 2 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_darktable/darktable/work/darktable-1.1.2/build/CMakeFiles/CMakeTmp/src.c:2:10: fatal error: 'omp.h' file not found 1 error generated. gmake[1]: *** [CMakeFiles/cmTryCompileExec3973531929.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec3973531929/fast] Error 2 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_darktable/darktable/work/darktable-1.1.2/build/CMakeFiles/CMakeTmp/src.c:2:10: fatal error: 'omp.h' file not found 1 error generated. gmake[1]: *** [CMakeFiles/cmTryCompileExec3382979230.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec3382979230/fast] Error 2 clang: error: language not recognized: 'openmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec2096644810.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec2096644810/fast] Error 2 clang: error: no such file or directory: '+Oopenmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec1889606406.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec1889606406/fast] Error 2 clang: error: unknown argument: '-qsmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec326856919.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec326856919/fast] Error 2 clang: error: unknown argument: '-mp' gmake[1]: *** [CMakeFiles/cmTryCompileExec3779605840.dir/src.c.o] Error 1 gmake: *** [cmTryCompileExec3779605840/fast] Error 2 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_darktable/darktable/work/darktable-1.1.2/build/CMakeFiles/CMakeTmp/src.cxx:2:10: fatal error: 'omp.h' file not found 1 error generated. gmake[1]: *** [CMakeFiles/cmTryCompileExec3201640476.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec3201640476/fast] Error 2 clang: error: no such file or directory: '/openmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec2420210185.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec2420210185/fast] Error 2 clang: error: unknown argument: '-Qopenmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec883615533.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec883615533/fast] Error 2 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_darktable/darktable/work/darktable-1.1.2/build/CMakeFiles/CMakeTmp/src.cxx:2:10: fatal error: 'omp.h' file not found 1 error generated. gmake[1]: *** [CMakeFiles/cmTryCompileExec4285343452.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec4285343452/fast] Error 2 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_darktable/darktable/work/darktable-1.1.2/build/CMakeFiles/CMakeTmp/src.cxx:2:10: fatal error: 'omp.h' file not found 1 error generated. gmake[1]: *** [CMakeFiles/cmTryCompileExec2125455150.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec2125455150/fast] Error 2 clang: error: language not recognized: 'openmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec2465517248.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec2465517248/fast] Error 2 clang: error: no such file or directory: '+Oopenmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec3673817509.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec3673817509/fast] Error 2 clang: error: unknown argument: '-qsmp' gmake[1]: *** [CMakeFiles/cmTryCompileExec2396883352.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec2396883352/fast] Error 2 clang: error: unknown argument: '-mp' gmake[1]: *** [CMakeFiles/cmTryCompileExec1244608828.dir/src.cxx.o] Error 1 gmake: *** [cmTryCompileExec1244608828/fast] Error 2 }}} -- Ticket URL: <https://trac.macports.org/ticket/47226> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #46683: afsctool sites need to be updated
by MacPorts 27 Jan '16

27 Jan '16

#46683: afsctool sites need to be updated --------------------+-------------------------------- Reporter: arno@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: afsctool --------------------+-------------------------------- A previous commit removed the livecheck for afsctool, but the master_site didn't change. I haven't checked, but I presume the source package is mirrored by MacPorts. The site is available at a new URL: https://brkirch.wordpress.com/afsctool/ The download is currently hosted through GoogleDocs. Is there an existing handler for those? Or would this be a special case? -- Ticket URL: <https://trac.macports.org/ticket/46683> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #46597: Serf1
by MacPorts 25 Jan '16

25 Jan '16

#46597: Serf1 ----------------------+-------------------------------- Reporter: saab99@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: serf1 | Port: ----------------------+-------------------------------- Hi ! Those ports not build under Mac OS Tigger 10.4.11 mikhail-vlasovs-power-mac-g5:/ root# port install serf1 ---> Computing dependencies for serf1 ---> Building serf1 Error: org.macports.build for port serf1 returned: command execution failed Please see the log file for port serf1 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_serf1/serf1/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port serf1 failed mikhail-vlasovs-power-mac-g5:/ root# In log i see :info:build scons: `serf-1.pc' is up to date. :info:build /usr/bin/ld: -i argument: nstall_name must have a ':' between its symbol names :info:build collect2: ld returned 1 exit status :info:build scons: *** [libserf-1.1.3.4.dylib] Error 1 :info:build scons: building terminated because of errors. :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_r elease_tarballs_ports_www_serf1/serf1/work/serf-1.3.4" && /opt/local/bin/scons -j2 APR=/opt/local APU=/opt/local OP ENSSL=/opt/local PREFIX=/opt/local CC=/opt/local/bin/gcc-apple-4.2 CPPFLAGS="-I/opt/local/include" CFLAGS="-Os -arc h ppc" LINKFLAGS="-L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc" CC="MACOSX_DEPLOYMENT_TARGET=10.4 /o pt/local/bin/gcc-apple-4.2" :info:build Exit code: 2 :error:build org.macports.build for port serf1 returned: command execution failed :debug:build Error code: CHILDSTATUS 17320 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "portbuild::build_main org.macports.build" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:build Warning: targets not executed for serf1: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port serf1 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_serf 1/serf1/main.log -- Ticket URL: <https://trac.macports.org/ticket/46597> MacPorts <https://www.macports.org/> Ports system for OS X

1 2