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

[MacPorts] #40998: libgcc @4.8.1 Compile error on Mavericks macports 2.2.1 package (Error: conflicting declaration 'typedef enum pointer_t pointer_t')
by MacPorts 26 Nov '13

26 Nov '13

#40998: libgcc @4.8.1 Compile error on Mavericks macports 2.2.1 package (Error: conflicting declaration 'typedef enum pointer_t pointer_t') -----------------------------------------+-------------------------------- Reporter: William.Capehart@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: Mavericks libgcc pointer_t | Port: libgcc @4.8.1 -----------------------------------------+-------------------------------- Macports' Mavericks 2.2.1 package has been removed and reinstalled several times. Xcode license has been accepted several times. xcode-select --install has been installed. I've also done the normal selfupdate step. From what I've seen I've covered most of what other people who have reported simpler problems with libgcc and gcc4x compile errors have done. From what I can see, this does not resemble the error in 40857 or 40810, for example. Attempts to install GCC 4.8 and 4.7 have been blocked by the same error each time with the following error in the libgcc build. (each attempt has been preceded by a clean of gcc48/gcc47 and libgcc) The same error emerges when installing ONLY libgcc. The error message for the libgcc build is below and log is attached. Note that fortran is a critical requirement for me. I should not disable this. Additionally installing gcc48 on macports a month ago met with no error. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/gcc-4.8.1/gcc/fortran/module.c:110:1: error: conflicting declaration 'typedef enum pointer_t pointer_t' pointer_t; ^ In file included from /usr/include/mach/memory_object_types.h:77:0, from /usr/include/mach/mach_types.h:85, from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build /prev-gcc/include-fixed/malloc.h:37, from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/gcc-4.8.1/gcc/system.h:460, from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/gcc-4.8.1/gcc/fortran/module.c:68: /usr/include/mach/vm_types.h:40:26: error: 'pointer_t' has a previous declaration as 'typedef vm_offset_t pointer_t' typedef vm_offset_t pointer_t; ^ make[3]: *** [fortran/module.o] Error 1 -- Ticket URL: <https://trac.macports.org/ticket/40998> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #41452: Fetching distfiles will inexplicably hang in Mavericks
by MacPorts 26 Nov '13

26 Nov '13

#41452: Fetching distfiles will inexplicably hang in Mavericks ---------------------------+-------------------------------- Reporter: elfprince13@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: ---------------------------+-------------------------------- Since upgrading to Mavericks, I've noticed that fetching distfiles from certain servers (notably GNU, but some others as well) seems to just hang (not even any network traffic on the Activity Monitor). I've done a complete reinstall of MacPorts and all of my installed ports, and had to manually download a good 60 or so distfile packages in the process. As I'm typing this, I've watched the fetching process for gstreamer hang for a good 30 minutes with no evidence of activity (including any network traffic at all). -- Ticket URL: <https://trac.macports.org/ticket/41452> MacPorts <http://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #41481: webkit-gtk @2.0.4 build error ./autotoolsconfig.h:242:10: fatal error
by MacPorts 26 Nov '13

26 Nov '13

#41481: webkit-gtk @2.0.4 build error ./autotoolsconfig.h:242:10: fatal error ------------------------------------------------+-------------------------- Reporter: tim.daley@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Keywords: autotoolsconfig.h WebKitFeatures.h | Version: 2.2.1 | Port: webkit-gtk ------------------------------------------------+-------------------------- port install webkit-gtk :info:build libtool: compile: /usr/bin/clang++ -DHAVE_CONFIG_H -I. -Wall -W -Wcast-align -Wchar-subscripts -Wreturn-type -Wformat -Wformat-security -Wno-format-y2k -Wundef -Wmissing-format-attribute -Wpointer-arith -Wwrite-strings -Wno-unused-parameter -Wno-parentheses -fno-exceptions -DBUILDING_CAIRO__ -DBUILDING_GTK__ -I./Source -I./Source/WTF -I./Source/WTF/wtf -DGTEST_USE_OWN_TR1_TUPLE=1 -fno-rtti -fstrict-aliasing -O3 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/include -pipe -Os -Wno-c++11-extensions -arch x86_64 -Wno-c++11-compat -O2 -MT Source/WTF/wtf/libWTF_la-ArrayBuffer.lo -MD -MP -MF Source/WTF/wtf/.deps/libWTF_la-ArrayBuffer.Tpo -c Source/WTF/wtf/ArrayBuffer.cpp -fno-common -DPIC -o Source/WTF/wtf/.libs /libWTF_la-ArrayBuffer.o :info:build In file included from Source/JavaScriptCore/llint/LLIntOffsetsExtractor.cppIn file included from Source/WTF/wtf/ArrayBuffer.cpp:26:26: :info:build In file included from : :info:build In file included from ./Source/WTF/config.h:26: :info:build ./Source/JavaScriptCore/config.h:26: :info:build ./autotoolsconfig.h:242:10: fatal error: 'WebKitFeatures.h' file not found :info:build ./autotoolsconfig.h:242:10: fatal error: 'WebKitFeatures.h' file not found :info:build #include "WebKitFeatures.h" :info:build ^ :info:build #include "WebKitFeatures.h" :info:build ^ -- Ticket URL: <https://trac.macports.org/ticket/41481> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #41383: llvm-gcc42 executables link with /usr/lib/libstdc++ on Mavericks
by MacPorts 26 Nov '13

26 Nov '13

#41383: llvm-gcc42 executables link with /usr/lib/libstdc++ on Mavericks -------------------------+------------------------ Reporter: michaelld@… | Owner: erickt@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.99 Keywords: | Port: llvm-gcc42 -------------------------+------------------------ For whatever reason, llvm-gcc42 was installed on my Mavericks boot disk. rev-upgrade returns a few warnings such as: {{{ Warning: /opt/local/bin/i686-apple-darwin13-llvm-cpp-4.2 uses /usr/lib/libstdc++.6.dylib as C++ standard library although macports::cxx_stdlib is set to libc++. }}} The targets are of these warnings are: {{{ /opt/local/bin/i686-apple-darwin13-llvm-cpp-4.2 /opt/local/bin/i686-apple-darwin13-llvm-g++-4.2 /opt/local/bin/i686-apple-darwin13-llvm-gcc-4.2 /opt/local/bin/llvm-gcov-4.2 /opt/local/libexec/llvm-gcc42/gcc/i686-apple-darwin13/4.2.1/cc1 /opt/local/libexec/llvm-gcc42/gcc/i686-apple-darwin13/4.2.1/cc1obj /opt/local/libexec/llvm-gcc42/gcc/i686-apple-darwin13/4.2.1/cc1objplus /opt/local/libexec/llvm-gcc42/gcc/i686-apple-darwin13/4.2.1/cc1plus /opt/local/libexec/llvm-gcc42/gcc/i686-apple-darwin13/4.2.1/collect2 /opt/local/libexec/llvm-gcc42/gcc/i686-apple- darwin13/4.2.1/libllvmgcc.dylib }}} I know these warnings are not critical; just reporting them. -- Ticket URL: <https://trac.macports.org/ticket/41383> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #40758: ld64 @136_2 Build error under Mavericks
by MacPorts 26 Nov '13

26 Nov '13

#40758: ld64 @136_2 Build error under Mavericks -------------------------+-------------------------------- Reporter: panayotis@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: ld64 -------------------------+-------------------------------- I am trying to use some packages depending on ld64, but it seems to have some issues. # port clean ld64 ---> Cleaning ld64 root@temp2:/opt/local/var/macports/sources/rsync.macports.org/release/tarballs# port install ld64 ---> Computing dependencies for ld64 ---> Fetching archive for ld64 ---> Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/ld64 ---> Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ld64 ---> Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://packages.macports.org/ld64 ---> Fetching distfiles for ld64 ---> Verifying checksums for ld64 ---> Extracting ld64 ---> Applying patches to ld64 ---> Configuring ld64 ---> Building ld64 Error: org.macports.build for port ld64 returned: command execution failed Please see the log file for port ld64 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ld64 failed -- Ticket URL: <https://trac.macports.org/ticket/40758> MacPorts <http://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #28365: boost-jam @3.1.18 bootstrap.jam not installed
by MacPorts 26 Nov '13

26 Nov '13

#28365: boost-jam @3.1.18 bootstrap.jam not installed -------------------------------+-------------------------------------------- Reporter: wichert@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: -------------------------------+-------------------------------------------- As far as I can see the bjam data files are not installed. As a quick test I tried compiling the Boost.Python example: {{{ bash-3.2$ cd /opt/local/share/doc/boost/libs/python/example/quickstart bash-3.2$ bjam Unable to load Boost.Build: could not find build system. --------------------------------------------------------- /opt/local/share/doc/boost/libs/python/example/quickstart/boost-build.jam attempted to load the build system by invoking 'boost-build ../../../../tools/build/v2 ;' but we were unable to find "bootstrap.jam" in the specified directory or in BOOST_BUILD_PATH (searching /opt/local/share/doc/boost/libs/python/example/quickstart/../../../../tools/build/v2, /opt/local/share/boost-build). Please consult the documentation at 'http://www.boost.org'. }}} -- Ticket URL: <https://trac.macports.org/ticket/28365> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #41512: pidgin: missing dependency on gtk2, links with gstreamer, farstream/farsight2
by MacPorts 26 Nov '13

26 Nov '13

#41512: pidgin: missing dependency on gtk2, links with gstreamer, farstream/farsight2 ----------------------+--------------------- Reporter: devans@… | Owner: nefar@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: pidgin ----------------------+--------------------- After the recent upgrade of gconf to version 3.2.6, pidgin now needs to declare an explicit dependency on gtk2. gconf now depends on gtk3 but pidgin does not. In addition, although the intent of the port is to disable voice and video support using gstreamer and farstream/farsight2, the port still links to these ports if they are installed. Looks like this is due to a change in configure options from previous versions. Port attached that adds the gtk2 dependency and adjusts the configuration arguments to ensure that gstreamer and farstream are not used. Let me know if this is OK to commit since this can break the pidgin build. -- Ticket URL: <https://trac.macports.org/ticket/41512> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #41541: py33-logilab-common installation failure
by MacPorts 26 Nov '13

26 Nov '13

#41541: py33-logilab-common installation failure ----------------------------+--------------------------------- Reporter: benoit.rivet@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: py33-logilab-common ----------------------------+--------------------------------- As explained in the title : on a Mac OS X.5 PPC machine, py33-logilab- common fails to build. Lines 373 and 374 of the main.log file read : {{{ :info:build running 2to3 on build/lib/logilab/common/test/data :info:build error: No such file or directory: '2to3' }}} The command {{{ls /opt/local/bin/2*}}} gives : {{{ /opt/local/bin/2to3-2.7 /opt/local/bin/2to3-3.3 }}} The command {{{locate 2to3}}} gives a bunch of results, including : {{{ /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/2to3 /opt/local/Library/Frameworks/Python.framework/Versions/3.3/bin/2to3 }}} Any workaround ? For further detail : starting from line 373, the log file reads : {{{ :info:build running 2to3 on build/lib/logilab/common/test/data :info:build error: No such file or directory: '2to3' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-logilab-common/py33-logilab- common/work/logilab-common-0.60.0" && /opt/local/Library/Frameworks/Python.framework/Versions/3.3/bin/python3.3 setup.py --no-user-cfg build :info:build Exit code: 1 :error:build org.macports.build for port py33-logilab-common returned: command execution failed :debug:build Error code: CHILDSTATUS 68495 1 :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 "$procedure $targetname" :info:build Warning: targets not executed for py33-logilab-common: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port py33-logilab-common for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-logilab-common/py33-logilab- common/main.log }}} -- Ticket URL: <https://trac.macports.org/ticket/41541> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #40479: https://trac.macports.org loads MacPorts.png over http
by MacPorts 26 Nov '13

26 Nov '13

#40479: https://trac.macports.org loads MacPorts.png over http ---------------------+-------------------- Reporter: s@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Component: website | Version: 2.2.0 Keywords: | Port: ---------------------+-------------------- When trac.macports.org is loaded over https, it loads the MacPorts.png image at the top of the page over http: `<img alt="project logo" src="http://www.macosforge.org/files/logos/MacPorts.png">` This can be fixed by replacing the "http://" with "//": `<img alt="project logo" src="//www.macosforge.org/files/logos/MacPorts.png">` or by using the same mechanism the MacOS forge logo uses. -- Ticket URL: <https://trac.macports.org/ticket/40479> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #41553: opencv @2.4.7_1 + enable cuda + configure error - build failure
by MacPorts 26 Nov '13

26 Nov '13

#41553: opencv @2.4.7_1 + enable cuda + configure error - build failure -----------------------+-------------------------------- Reporter: cmv.ict@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: -----------------------+-------------------------------- Step 1: #sudo port edit --editor nano opencv => change -DWITH_CUDA=OFF to -DWITH_CUDA=ON Step 2: #sudo port install opencv Error: org.macports.configure for port opencv returned: configure failure: command execution failed -- Ticket URL: <https://trac.macports.org/ticket/41553> MacPorts <http://www.macports.org/> Ports system for OS X

1 1