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

[MacPorts] #43700: Move back freetds to stableversion
by MacPorts 03 Aug '14

03 Aug '14

#43700: Move back freetds to stableversion -----------------------+-------------------------------- Reporter: stronk7@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: -----------------------+-------------------------------- With https://trac.macports.org/changeset/99639 the freetds port was moved to 0.92.405 0.92 is a development version and 405 is already 1.5y old. More yet, it has some important issues handling LOBs and restrictions about logging/debugging, that seem to be enabled by default, conflicting with any attempt to disable it @ freetds.conf. Also a lot of issues have been fixed since 405 till today, many of them backported to 0.91. So this is a request to move back to 0.91 (stable version) point 103. I've switched here, using it from MSSQL, and it really seems to be quicker and more stable. For your consideration. The change is trivial. The only point is that it implies a "downgrade" (version.wise). Ciao :-) -- Ticket URL: <https://trac.macports.org/ticket/43700> MacPorts <http://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #43144: p5-test-simple: update to 1.001003
by MacPorts 03 Aug '14

03 Aug '14

#43144: p5-test-simple: update to 1.001003 ---------------------+---------------------------- Reporter: mojca@… | Owner: sal@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: p5-test-simple ---------------------+---------------------------- {{{ > port livecheck p5-test-simple p5-test-simple seems to have been updated (port version: 0.98, new version: 1.001003) }}} -- Ticket URL: <https://trac.macports.org/ticket/43144> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #41876: maven-ant-tasks cannot find JAVA_HOME correctly
by MacPorts 03 Aug '14

03 Aug '14

#41876: maven-ant-tasks cannot find JAVA_HOME correctly ---------------------------------------+-------------------------------- Reporter: ritchiecai@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: maven-ant-tasks JAVA_HOME | Port: maven-ant-tasks ---------------------------------------+-------------------------------- Just upgraded to Mavericks, maven-ant-tasks failed while upgrading macport. here is the error: {{{ :debug:build Executing org.macports.build (maven-ant-tasks) :debug:build Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_devel_maven-ant-tasks/maven-ant- tasks/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.9' HOME='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_devel_maven-ant-tasks/maven-ant- tasks/work/home' :debug:build Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_devel_maven-ant-tasks/maven-ant-tasks/work /maven-ant-tasks-2.1.3" && mvn package' :debug:build Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_devel_maven-ant-tasks/maven-ant-tasks/work /maven-ant-tasks-2.1.3" && mvn package :info:build Error: JAVA_HOME is not defined correctly. :info:build We cannot execute /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/java :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_devel_maven-ant-tasks/maven-ant-tasks/work /maven-ant-tasks-2.1.3" && mvn package :info:build Exit code: 1 }}} I tried to clean and rebuild, it gives the same error. JAVE_HOME is defined: {{{ echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk/Contents/Home /usr/libexec/java_home /Library/Java/JavaVirtualMachines/jdk/Contents/Home }}} No idea how macport get /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home as JAVA_HOME, I never defined it anywhere. Also: {{{ mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.7.0_45 Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x" version: "10.9.1" arch: "x86_64" Family: "mac" }}} -- Ticket URL: <https://trac.macports.org/ticket/41876> MacPorts <http://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #44485: Compile Error in Open (GNU) Cobol when compiling in OS 10.9 Mavericks ( New Install )
by MacPorts 03 Aug '14

03 Aug '14

#44485: Compile Error in Open (GNU) Cobol when compiling in OS 10.9 Mavericks ( New Install ) ---------------------------+-------------------------------- Reporter: gregthrower@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: ---------------------------+-------------------------------- macbook-pro:tmp macbook$ cobc -x hello.cob clang: error: unknown argument: '-R/opt/local/lib' [-Wunused-command-line- argument-hard-error-in-future] clang: note: this will be a hard error (cannot be downgraded to a warning) in the future. Hard error. Does not create executable. Should I forget running this on my MAC and just create a Linux partition? -- Ticket URL: <https://trac.macports.org/ticket/44485> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #44342: octave-general @1.3.4_0 Configure error - build failure
by MacPorts 02 Aug '14

02 Aug '14

#44342: octave-general @1.3.4_0 Configure error - build failure ----------------------------+-------------------------------- Reporter: roberthuston@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: octave-general | Port: octave-general ----------------------------+-------------------------------- After upgrading to octave @3.8.1_0, I also needed to upgrade my Octave packages. However, octave-general @1.3.4_0 now fails at configuration because it can't find /opt/local/share/octave/3.8.1/etc/macros.texi. I went to that directory and verified that the file is indeed missing. My previous version of octave-general @1.3.2_0 was fine, but it ran with my installation of octave @3.6.4. It would be nice to play with the new GUI, but I can't be without my Octave packages, so I'm reverting for now. The end of the /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave-general/main.log file contains: {{{ :info:configure /opt/local/bin/mkoctfile-3.8.1 SHA1.cc :info:configure /opt/local/bin/mkoctfile-3.8.1 mark_for_deletion.cc :info:configure /opt/local/bin/mkoctfile-3.8.1 packfields.cc :info:configure /opt/local/bin/mkoctfile-3.8.1 unpackfields.cc :info:configure copyfile /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave-general/work/.tmp /oct-S1fOV6/general/src/SHA1.oct /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave-general/work/.tmp /oct-S1fOV6/general/src/mark_for_deletion.oct /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave-general/work/.tmp /oct-S1fOV6/general/src/packfields.oct /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave-general/work/.tmp /oct-S1fOV6/general/src/unpackfields.oct /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave-general/work/.tmp /oct-S1fOV6/general/inst/x86_64-apple-darwin13.3.0-api-v49+ :info:configure unable to open /opt/local/share/octave/3.8.1/etc/macros.texi for reading :info:configure error: called from '__makeinfo__' in file /opt/local/share/octave/3.8.1/m/help/__makeinfo__.m near line 103, column 5 :info:configure error: called from: :info:configure error: /opt/local/share/octave/3.8.1/m/pkg/private/install.m at line 241, column 5 :info:configure error: /opt/local/share/octave/3.8.1/m/pkg/private/build.m at line 50, column 3 :info:configure error: /opt/local/share/octave/3.8.1/m/pkg/pkg.m at line 516, column 7 :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave- general/work/general" && /opt/local/bin/octave -q -f --eval 'pkg build -verbose -nodeps /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave- general/work/general /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave- general/work/.tmp/general.tar.gz' :info:configure Exit code: 1 :error:configure org.macports.configure for port octave-general 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 octave-general: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port octave-general for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_math_octave-general/octave-general/main.log }}} Things break down after the ":info:configure copyfile" line. -- Ticket URL: <https://trac.macports.org/ticket/44342> MacPorts <http://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #44455: openmpi: Optionally disable hwloc requirement
by MacPorts 02 Aug '14

02 Aug '14

#44455: openmpi: Optionally disable hwloc requirement -----------------------------+-------------------------------- Reporter: michael-lists@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: openmpi -----------------------------+-------------------------------- I'd like to be able to disable the hwloc dependencies of openmpi. Some code I have does not properly work with hwloc-enabled OpenMPI for some reason. Below is a patch that adds a variant ''nohwloc'' {{{ --- /Users/admin/Desktop/openmpi 2014-07-23 04:30:14.000000000 +0200 +++ /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/science/openmpi/Portfile 2014-07-27 11:30:19.000000000 +0200 @@ -309,6 +309,11 @@ depends_lib-append path:${prefix}/lib/pkgconfig/valgrind.pc:valgrind configure.args-append --enable-debug --enable-memchecker --with- valgrind=${prefix} } + + variant nohwloc description {disable hwloc requirement} { + configure.args-append --without-hwloc + depends_lib-delete port:hwloc + } } else { depends_lib-append port:$name-default }}} -- Ticket URL: <https://trac.macports.org/ticket/44455> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #43381: openmpi-default @1.7.5_1+gcc48 does not work with hwloc @1.9_0
by MacPorts 02 Aug '14

02 Aug '14

#43381: openmpi-default @1.7.5_1+gcc48 does not work with hwloc @1.9_0 ------------------------+------------------------------------ Reporter: dstrubbe@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: openmpi-default, hwloc ------------------------+------------------------------------ I get the error below for a simple test program. It does work if I downgrade to hwloc @1.8.1_0 and rebuild openmpi though. (Activating hwloc 1.9_0 without rebuilding openmpi makes the error come again.) I have OSX 10.8.5, XCode 5.1. It did work fine on my other computer, with openmpi- default @1.7.5_1+gcc45, OSX 10.6.8, XCode 3.2.6. {{{ $ mpif90-openmpi-mp test_new.f90 $[mpiexec-openmpi-mp -n 1 ./a.out [[38689,1],0] ORTE_ERROR_LOG: Error in file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_openmpi /openmpi-default/work/openmpi-1.7.5/orte/util/nidmap.c at line 106 [[38689,1],0] ORTE_ERROR_LOG: Error in file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_openmpi /openmpi-default/work/openmpi-1.7.5/orte/mca/ess/env/ess_env_module.c at line 154 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_util_nidmap_init failed --> Returned value Error (-1) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value Error (-1) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relev------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code.. Per user-direction, the job has been aborted. ------------------------------------------------------- *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** and potentially your MPI job) Local abort before MPI_INIT completed successfully; not able to aggregate error messages, and not able to guarantee that all other processes were killed! -------------------------------------------------------------------------- mpiexec-openmpi-mp detected that one or more processes exited with non- zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[38689,1],0] Exit code: 1 -------------------------------------------------------------------------- }}} A couple of threads describing a similar situation on Fedora suggests it is related to some conflict between different versions of OpenMPI, which inspired me to try swapping the hwloc version: http://www.open-mpi.org/community/lists/users/2013/07/22346.php https://lists.fedoraproject.org/pipermail/users/2013-July/438349.html -- Ticket URL: <https://trac.macports.org/ticket/43381> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #44506: petsc installation fails
by MacPorts 02 Aug '14

02 Aug '14

#44506: petsc installation fails ------------------------+-------------------------------- Reporter: cpraveen@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: petsc ------------------------+-------------------------------- I am trying to upgrade dolfin and in the process petsc needs to be upgraded. But it fails with some error related to cholmod/suitesparse. Log file is attached. -- Ticket URL: <https://trac.macports.org/ticket/44506> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #44492: slepc 3.4.4 fails to build
by MacPorts 02 Aug '14

02 Aug '14

#44492: slepc 3.4.4 fails to build --------------------------+-------------------------------- Reporter: cpraveen@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: petsc, slepc | Port: slepc --------------------------+-------------------------------- Log file is attached. -- Ticket URL: <https://trac.macports.org/ticket/44492> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #44350: Add port phonon-backend-gstreamer
by MacPorts 02 Aug '14

02 Aug '14

#44350: Add port phonon-backend-gstreamer ---------------------------+-------------------------------- Reporter: springermac@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: ---------------------------+-------------------------------- Add port phonon-backend-gstreamer Requires phonon and gstreamer010-gst-plugins-base -- Ticket URL: <https://trac.macports.org/ticket/44350> MacPorts <http://www.macports.org/> Ports system for OS X

1 4