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

[MacPorts] #40237: cmake 2.8.11.2 fails on install
by MacPorts 27 Aug '13

27 Aug '13

#40237: cmake 2.8.11.2 fails on install ------------------------+-------------------------------- Reporter: rsdancey@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: ------------------------+-------------------------------- Summary: cmake @2.8.11.2 build error Description: OSX Mountain Lion v10.8.4 xcode 4.6.2 :info:configure make: `cmake' is up to date. :info:configure loading initial cache file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/cmake/work/cmake-2.8.10.2-x86_64/Bootstrap.cmk/InitialCacheFlags.cmake :info:configure -- The C compiler identification is Clang 4.2.0 :info:configure -- The CXX compiler identification is Clang 4.2.0 :info:configure CMake Warning at Modules/Platform/Darwin.cmake:158 (message): :info:configure Ignoring CMAKE_OSX_SYSROOT value: :info:configure :info:configure /Developer/SDKs/MacOSX10.8.sdk :info:configure :info:configure because the directory does not exist. :info:configure Call Stack (most recent call first): :info:configure Modules/CMakeSystemSpecificInformation.cmake:36 (include) :info:configure CMakeLists.txt:14 (project) :info:configure :info:configure :info:configure CMake Error at Modules/Platform/Darwin.cmake:190 (message): :info:configure CMAKE_OSX_DEPLOYMENT_TARGET is '10.8' but CMAKE_OSX_SYSROOT: :info:configure :info:configure "" :info:configure :info:configure is not set to a MacOSX SDK with a recognized version. Either set :info:configure CMAKE_OSX_SYSROOT to a valid SDK or set CMAKE_OSX_DEPLOYMENT_TARGET to :info:configure empty. :info:configure Call Stack (most recent call first): :info:configure Modules/CMakeSystemSpecificInformation.cmake:36 (include) :info:configure CMakeLists.txt:14 (project) :info:configure :info:configure :info:configure -- Configuring incomplete, errors occurred! :info:configure --------------------------------------------- :info:configure Error when bootstrapping CMake: :info:configure Problem while running initial CMake :info:configure --------------------------------------------- :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/cmake/work/cmake-2.8.10.2-x86_64" && ./configure --prefix=/opt/local --mandir=/share/man --docdir=/share/doc/cmake --parallel=4 --init=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/cmake/work/cmake-2.8.10.2/macports.cmake :info:configure Exit code: 11 }}} Unique Factors: After installing xcode, I moved it to another volume and placed an alias in the default Applications folder I manually edited the Darwin.cmake file to force CMAKE_OSX_SYSROOT to the proper location (/Volumes/Terabyte/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk) and was able to manually "./config", "make config" and "make" the application. cmake is in /usr/local/bin and does run correctly but MacPorts doesn't know that it has been installed. The proper CMAKE_OSC_SYSROOT shows up when I run the "env" command from the command line. It does not appear when I use the "export" command from the command line. -- Ticket URL: <https://trac.macports.org/ticket/40237> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #40252: octave-devel: undefined symbols
by MacPorts 27 Aug '13

27 Aug '13

#40252: octave-devel: undefined symbols --------------------+-------------------------- Reporter: ram@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: octave-devel --------------------+-------------------------- In building `octave-devel` @3.6.4_7 I'm running into the following build error: {{{ :info:build Undefined symbols for architecture x86_64: :info:build "__gfortran_concat_string", referenced from: :info:build _cgesvd_ in liblapack.a(cgesvd.o) :info:build _dgesvd_ in liblapack.a(dgesvd.o) :info:build _sgesvd_ in liblapack.a(sgesvd.o) :info:build _zgesvd_ in liblapack.a(zgesvd.o) :info:build _chseqr_ in liblapack.a(chseqr.o) :info:build _cunmbr_ in liblapack.a(cunmbr.o) :info:build _cunmlq_ in liblapack.a(cunmlq.o) :info:build ... :info:build "__gfortran_pow_i4_i4", referenced from: :info:build _clalsa_ in liblapack.a(clalsa.o) :info:build _dlalsa_ in liblapack.a(dlalsa.o) :info:build _dlasd0_ in liblapack.a(dlasd0.o) :info:build _dlasda_ in liblapack.a(dlasda.o) :info:build _slalsa_ in liblapack.a(slalsa.o) :info:build _slasd0_ in liblapack.a(slasd0.o) :info:build _slasda_ in liblapack.a(slasda.o) :info:build ... :info:build ld: symbol(s) not found for architecture x86_64 }}} The full build log is attached. -- Ticket URL: <https://trac.macports.org/ticket/40252> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #40251: octave-devel: allow libgcc-devel to satisfy libgcc dependency
by MacPorts 27 Aug '13

27 Aug '13

#40251: octave-devel: allow libgcc-devel to satisfy libgcc dependency --------------------+-------------------------- Reporter: ram@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: octave-devel --------------------+-------------------------- Current `octave-devel` depends on `libgcc` specifically and does not allow `libgcc-devel` to satisfy this dependency, can the following be used as the dependency for `libgcc` be used so that `libgcc-devel` can satisfy the dependency: {{{ path:lib/libgcc/libgcc_s.1.dylib:libgcc }}} -- Ticket URL: <https://trac.macports.org/ticket/40251> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #40253: mapserver @6.2.1_0 requires gd @2.0 instead of @2.1?
by MacPorts 26 Aug '13

26 Aug '13

#40253: mapserver @6.2.1_0 requires gd @2.0 instead of @2.1? --------------------+-------------------------------- Reporter: jea@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: mapserver gd2 --------------------+-------------------------------- When trying to make the new version of mapserver @6.2.1_0 it wouldn't configure unless I activated the old @2.0.35_14 version of gd2, instead of the newer d2 @2.1.0_3+x11 Has it been tested with gd(a)2.1? Is this just a dependency checking problem? There's probably a way in the macports system to require the backport of gd2 if necessary, or to allow the most recent version otherwise. -- Ticket URL: <https://trac.macports.org/ticket/40253> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #40254: mapserver @6.2.1_0 +apache2 installs script in /opt/local/apache2/cgi-bin
by MacPorts 26 Aug '13

26 Aug '13

#40254: mapserver @6.2.1_0 +apache2 installs script in /opt/local/apache2/cgi-bin --------------------+-------------------------------- Reporter: jea@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: mapserver --------------------+-------------------------------- The mapserver install copies a bash script into the /opt/local/apache2 /cgi-bin directory, and then apache complains {{{ [Mon Aug 26 13:58:58 2013] [error] [client 127.0.0.1] /opt/local/apache2 /cgi-bin/mapserv: error: `/opt/local/apache2/cgi-bin/.libs/mapserv' does not exist [Mon Aug 26 13:58:58 2013] [error] [client 127.0.0.1] This script is just a wrapper for mapserv. [Mon Aug 26 13:58:58 2013] [error] [client 127.0.0.1] See the libtool documentation for more information. [Mon Aug 26 13:58:58 2013] [error] [client 127.0.0.1] Premature end of script headers: mapserv }}} I've been able to get macports @6.2.1_0 working with macports apache 2 if I copy the binary to the cgi-bin directory sudo cp /opt/local/bin/mapserv /opt/local/apache2/cgi-bin/mapserv but the installer should probably do that somehow. PS The script clearly states # This wrapper script should never be moved out of the build directory. # If it is, it will not operate correctly. -- Ticket URL: <https://trac.macports.org/ticket/40254> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #40246: jabber @1.4.2_5 (net) command execution failed
by MacPorts 26 Aug '13

26 Aug '13

#40246: jabber @1.4.2_5 (net) command execution failed ------------------------+-------------------------------- Reporter: wcsantos@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: jabber | Port: jabber ------------------------+-------------------------------- Compile of Jabber failed on system: # uname -a Darwin MacBookPro15.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64' # port version Version: 2.2.0 === Xcode 4.4 === * '''Xcode''': Build version 4F250 * '''llvm-gcc''': i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) * '''clang''': Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn) Significant error messages: {{{ 3 warnings and 3 errors generated. gnumake[2]: *** [base_accept.o] Error 1 gnumake[2]: *** Waiting for unfinished jobs.... In file included from base_file.c:42: In file included from ../jabberd.h:41: ../lib/lib.h:62:9: warning: 'snprintf' macro redefined #define snprintf ap_snprintf ^ /usr/include/secure/_stdio.h:57:9: note: previous definition is here #define snprintf(str, len, ...) \ ^ In file included from base_file.c:42: In file included from ../jabberd.h:41: ../lib/lib.h:67:9: warning: 'vsnprintf' macro redefined #define vsnprintf ap_vsnprintf ^ /usr/include/secure/_stdio.h:71:9: note: previous definition is here #define vsnprintf(str, len, format, ap) \ ^ 2 warnings generated. gnumake[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_jabber/jabber/work/jabber-1.4.2/jabberd/base' gnumake[1]: *** [all-recursive] Error 1 gnumake[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_jabber/jabber/work/jabber-1.4.2/jabberd' gnumake: *** [all-recursive] Error 1 gnumake: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_jabber/jabber/work/jabber-1.4.2' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_jabber/jabber/work/jabber-1.4.2" && /usr/bin/gnumake -j2 -w all Exit code: 2 Error: org.macports.build for port jabber returned: command execution failed Warning: targets not executed for jabber: org.macports.activate org.macports.build org.macports.destroot org.macports.install Please see the log file for port jabber for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_jabber/jabber/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port jabber failed }}} The entire compile log may be found at: http://pastebin.com/0W3A40Uk -- Ticket URL: <https://trac.macports.org/ticket/40246> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #39207: vim @7.3.762_2+cscope+huge+perl+python27+python33+tcl is broken after upgrading MacPorts python27 from 2.7.3 to 2.7.5
by MacPorts 26 Aug '13

26 Aug '13

#39207: vim @7.3.762_2+cscope+huge+perl+python27+python33+tcl is broken after upgrading MacPorts python27 from 2.7.3 to 2.7.5 --------------------------+-------------------------------- Reporter: swordangel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: python | Port: vim --------------------------+-------------------------------- 1. Upgrade python27 in MacPorts to version 2.7.5 2. Open a existing Python source file in vim; e.g. vim helloworld.py 3. Get a Python 2.7 traceback and see vim crash. The traceback is as follows: Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py", line 548, in <module> main() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py", line 530, in main known_paths = addusersitepackages(known_paths) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py", line 266, in addusersitepackages user_site = getusersitepackages() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py", line 241, in getusersitepackages user_base = getuserbase() # this will also set USER_BASE File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py", line 231, in getuserbase USER_BASE = get_config_var('userbase') File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sysconfig.py", line 516, in get_config_var return get_config_vars().get(name) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sysconfig.py", line 449, in get_config_vars import re File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/re.py", line 105, in <module> import sre_compile File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_compile.py", line 14, in <module> import sre_parse File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_parse.py", line 17, in <module> from sre_constants import * File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_constants.py", line 18, in <module> from _sre import MAXREPEAT ImportError: cannot import name MAXREPEAT This StackOverflow QA seems to be relevant: [http://stackoverflow.com/questions/16301735/importerror-cannot-import- name-maxrepeat-with-cx-freeze] -- Ticket URL: <https://trac.macports.org/ticket/39207> MacPorts <http://www.macports.org/> Ports system for OS X

1 11

[MacPorts] #40249: py-obspy: update compiler variants
by MacPorts 26 Aug '13

26 Aug '13

#40249: py-obspy: update compiler variants -----------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: py-obspy -----------------------------+-------------------------------- I updated compiler variant handling according to recipe: https://trac.macports.org/wiki/PortfileRecipes#fortran This update should solves the following issues: 1. Commit r110107 broke this port as the port requires Fortran; I personally was not able to build with that commit. But even if it installs somewhere, it is very probably not functional. 2. The new compiler handling seems to have resolved some subtile issue/incompatibility for specific combinations of `python26` and various `gcc` versions. I therefore bump the revision number as well, because (a) it may have been installed from the nonfunctional version, (b) it solves the issue 2 and therefore should be updated/rebuild. I tested under Mountain Lion with for Python 2.6 and 2.7, with all compilers except `gcc49`, which I cannot install due to conflicting `libgcc`. **Some doubt:** Before the variants were available only for the subports. It was inside the `if {${subport} != ${name}}` block. However, it probably would make sense to have variants for the "superport" as well. This would than pass the variant to the default subport. Now, this constrain probably is present. So how would this be implemented correctly? -- Ticket URL: <https://trac.macports.org/ticket/40249> MacPorts <http://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #40245: py27-docutils fails checksum verification
by MacPorts 26 Aug '13

26 Aug '13

#40245: py27-docutils fails checksum verification --------------------+-------------------------------- Reporter: mail@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: py27-docutils --------------------+-------------------------------- Build result: ---> Attempting to fetch py27-docutils-0.11_0.darwin_12.noarch.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/py27-docuti… ---> Fetching distfiles for py27-docutils ---> Verifying checksums for py27-docutils Error: Checksum (md5) mismatch for docutils-0.11.tar.gz Error: Checksum (sha1) mismatch for docutils-0.11.tar.gz Error: Checksum (rmd160) mismatch for docutils-0.11.tar.gz Error: org.macports.checksum for port py27-docutils returned: Unable to verify file checksums Log: :debug:checksum checksum phase started at Sun Aug 25 13:10:02 PDT 2013 :notice:checksum ---> Verifying checksums for py27-docutils :debug:checksum Executing org.macports.checksum (py27-docutils) :info:checksum ---> Checksumming docutils-0.11.tar.gz :error:checksum Checksum (md5) mismatch for docutils-0.11.tar.gz :info:checksum Portfile checksum: docutils-0.11.tar.gz md5 20ac380a18b369824276864d98ec0ad6 :info:checksum Distfile checksum: docutils-0.11.tar.gz md5 86395e5eb5c5804dbb40f8a1ac847e44 :error:checksum Checksum (sha1) mismatch for docutils-0.11.tar.gz :info:checksum Portfile checksum: docutils-0.11.tar.gz sha1 3894ebcbcbf8aa54ce7c3d2c8f05460544912d67 :info:checksum Distfile checksum: docutils-0.11.tar.gz sha1 e68f308245dd9a61a1964d02dfd7d80333abb163 :error:checksum Checksum (rmd160) mismatch for docutils-0.11.tar.gz :info:checksum Portfile checksum: docutils-0.11.tar.gz rmd160 73fa71348388f4c47c70d8894e7c154d48e0c1b2 :info:checksum Distfile checksum: docutils-0.11.tar.gz rmd160 0404ede2ea66b21c205ceaa7862826115c541bce :info:checksum The correct checksum line may be: :info:checksum checksums md5 86395e5eb5c5804dbb40f8a1ac847e44 \ sha1 e68f308245dd9a61a1964d02dfd7d80333abb163 \ rmd160 0404ede2ea66b21c205ceaa7862826115c541bce :error:checksum org.macports.checksum for port py27-docutils returned: Unable to verify file checksums -- Ticket URL: <https://trac.macports.org/ticket/40245> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #40238: ROOT Update to fix C++11 and gfortran issues
by MacPorts 25 Aug '13

25 Aug '13

#40238: ROOT Update to fix C++11 and gfortran issues ---------------------------------+-------------------------------- Reporter: jonesc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: haspatch maintainer | Port: root ---------------------------------+-------------------------------- Small update that fixes a couple of issues ticket:40226 ticket:39975 Chris -- Ticket URL: <https://trac.macports.org/ticket/40238> MacPorts <http://www.macports.org/> Ports system for OS X

1 7