September 2012 - macports-tickets - lists.macosforge.org

[MacPorts] #36103: octave-devel build: Undefined symbols for architecture x86_64
by MacPorts 14 Sep '12

14 Sep '12

#36103: octave-devel build: Undefined symbols for architecture x86_64 --------------------+-------------------------------- Reporter: vic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: --------------------+-------------------------------- Running OSX 10.8.1. I had "octave-devel +docs +fltk" @3.6.2 installed earlier, but an "upgrade outdated" killed it. My latest attempt at a clean installation failed well into the build stage with the messages {{{ :info:build Undefined symbols for architecture x86_64: :info:build "std::_List_node_base::_M_transfer(std::_List_node_base*, std::_List_node_base*)", referenced from: :info:build std::list<regexp::match_element, std::allocator<regexp::match_element> >::operator=(std::list<regexp::match_element, std::allocator<regexp::match_element> > const&) in liboctave_la-regexp.o :info:build "std::_List_node_base::_M_hook(std::_List_node_base*)", referenced from: :info:build dir_entry::read() in liboctave_la-dir-ops.o :info:build regexp::match(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) in liboctave_la- regexp.o :info:build std::list<regexp::match_element, std::allocator<regexp::match_element> >::operator=(std::list<regexp::match_element, std::allocator<regexp::match_element> > const&) in liboctave_la-regexp.o :info:build "std::_List_node_base::_M_unhook()", referenced from: :info:build std::list<regexp::match_element, std::allocator<regexp::match_element> >::operator=(std::list<regexp::match_element, std::allocator<regexp::match_element> > const&) in liboctave_la-regexp.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build collect2: ld returned 1 exit status :info:build make[3]: *** [liboctave.la] Error 1 }}} I am attaching the log file -- Ticket URL: <https://trac.macports.org/ticket/36103> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 30

[MacPorts] #36137: Option to mark a port for installation when the port is fixed
by MacPorts 14 Sep '12

14 Sep '12

#36137: Option to mark a port for installation when the port is fixed -------------------------+-------------------------------- Reporter: dylanryan@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Keywords: | Port: -------------------------+-------------------------------- This is a request for a feature that I think might be useful. First, some background. Both when installing Lion, and more recently Mountain Lion, after finding a bunch of broken ports, I decided it would be easier to do a clean re- install (to clear out any old cruft that had accumulated). However, after both system upgrades, I (naturally) found several ports I wanted that would not install on the new system. I then had to keep track of what ports I still needed to install, and periodically check to see if they had been fixed yet. Other times, ports have broken on me, and after wrestling with them a while, I tend to uninstall them and wait for them to get fixed, so that I can get that port with a clean install later. I know I could just deactivate them, but I prefer knowing I have a clean start, that it isn't some left over configuration file somewhere that is messing up the build. Anyway, in both cases, I have to manually keep track of a list of ports (and variants) that I want to install later, and then watch for changes, and then go install them when the ports are updated. What would be nice is if port could do this automatically. I am thinking something along the lines of port watch someBrokenPort +someVariant (where "watch" is just a placeholder name for the command, it could probably be renamed something better) The idea is, this would tell MacPorts to record the current-at-the-time- that-is-executed version of that port in it's database somewhere (along with any variants that were specified), and then watch it. On subsequent self-updates, it would check the new version of that port, and if it is later, tell the user something like "The watched port someBrokenPort has been updated. To install, run port install someBrokenPort +someVariant". Then, when successfully installing any port, clear any watches on that port automatically. If any install fails, and the port is being watched, update the watched version to this version (so that this version doesn't get tried again). (this might get tricky if a watched port only fails because a dependency fails, so it might be best to make the watch command itself automatically watch any broken dependencies) This way, after an OS update or whatever breaks some ports (lets face it, this is likely going to be a yearly issue just on the OS side, plus GCC updates sometimes break other ports, etc), users can just tell the system to watch ports for them (even though they are not currently installed), and it will alert them when a new version is ready to try. If the next install also fails, it will still be watched and the NEXT update will remind the user. Basically - if a port breaks on a system install, the user is probably thinking about it then, so knows what variants they want, etc, whereas on a subsequent self-update a week or 2 later, they might not be thinking as clearly (they might just remember "Oh, yeah, I wanted to install somePort" but they might not remember what variants off hand). So, by letting the user specify things like variants when they watch it, port can remind them of that, as well. It reduces the user's book keeping needs. ( There would also have to be a port unwatch command to manually remove from the list, of course. And maybe options to the watch command to automatically try and install when the port is updated ) -- Ticket URL: <https://trac.macports.org/ticket/36137> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #36030: license information of msgpack
by MacPorts 14 Sep '12

14 Sep '12

#36030: license information of msgpack ------------------------------+--------------------------------------------- Reporter: hum@… | Owner: naoya.n@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: license | Port: msgpack ------------------------------+--------------------------------------------- msgpack port lacks license information and its binary package is not stored on the build server. The absence of the license information prevents from storing binary packages of dependent ports. The Portfile should include the following line: {{{ license Apache-2 }}} Can I join the maintainers of the msgpack port? -- Ticket URL: <https://trac.macports.org/ticket/36030> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #31171: building gcc46 on osx lion fails
by MacPorts 14 Sep '12

14 Sep '12

#31171: building gcc46 on osx lion fails ------------------------------+--------------------------------------------- Reporter: okpail@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: ------------------------------+--------------------------------------------- ---> Computing dependencies for gcc46 ---> Building gcc46 Error: Target org.macports.build returned: shell command failed (see log for details) Log for gcc46 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> -- Ticket URL: <https://trac.macports.org/ticket/31171> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 35

[MacPorts] #25205: gcc45 should use --enable-fully-dynamic-string
by MacPorts 14 Sep '12

14 Sep '12

#25205: gcc45 should use --enable-fully-dynamic-string --------------------------------+------------------------------------------- Reporter: jwiegley@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 1.9.1 Component: ports | Version: 1.9.0 Keywords: | Port: --------------------------------+------------------------------------------- This fix was already made for gcc44 (https://trac.macports.org/ticket/22234) now it needs to be made for gcc45. Without it, C++ applications which use the Boost libraries (among other) will SIGABRT mysteriously. -- Ticket URL: <http://trac.macports.org/ticket/25205> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #36136: sudo port install ImageMagick failes
by MacPorts 14 Sep '12

14 Sep '12

#36136: sudo port install ImageMagick failes ----------------------+-------------------------------- Reporter: joshua@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: ----------------------+-------------------------------- [persephone:~/Desktop] jpaul% sudo port install ImageMagick ---> Computing dependencies for ImageMagick ---> Building ImageMagick Error: org.macports.build for port ImageMagick returned: command execution failed Please see the log file for port ImageMagick for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ImageMagick/ImageMagick/main.log error is: make: *** No rule to make target `all'. Stop. [persephone:~/Desktop] jpaul% cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ImageMagick/ImageMagick/work/ImageMagick-6.7.9-0" && /usr/bin/make -j8 -w all make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ImageMagick/ImageMagick/work/ImageMagick-6.7.9-0' make: *** No rule to make target `all'. Stop. make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_ImageMagick/ImageMagick/work/ImageMagick-6.7.9-0' -- Ticket URL: <https://trac.macports.org/ticket/36136> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #35222: php5 5.3.12 horrible slow cli
by MacPorts 14 Sep '12

14 Sep '12

#35222: php5 5.3.12 horrible slow cli --------------------------------+------------------------------------------- Reporter: localgod@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: php5 --------------------------------+------------------------------------------- After I updated macports a few days ago my php cli has become horribly slow: {{{ $ time /opt/local/bin/php --version PHP 5.3.12 with Suhosin-Patch (cli) (built: Jul 16 2012 15:19:53) Copyright (c) 1997-2012 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies with Xdebug v2.2.0, Copyright (c) 2002-2012, by Derick Rethans with Suhosin v0.9.33, Copyright (c) 2007-2012, by SektionEins GmbH real 0m35.056s user 0m0.032s sys 0m0.018s }}} When I run the osx supplied version: {{{ $ time /usr/bin/php --version PHP 5.3.10 with Suhosin-Patch (cli) (built: Feb 20 2012 22:55:53) Copyright (c) 1997-2012 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies real 0m0.598s user 0m0.048s sys 0m0.128s }}} I tried uninstalling all php related ports and do a fresh install with the following ports: {{{ php5 +apache2 +pear +suhosin ZendFramework php5-solr php5-gearman php5-http php5-imagick php5-mongo php5-redis php5-suhosin php5-xdebug }}} ...but the problem persists. I have another machine without php5-gearman, php5-http, php5-imagick, php5-mongo, php5-redis and php5-suhosin installed that works fine, so I tried uninstalling these, but this has no effect, cli is still extremely slow. Running php scripts thru apache works fine. Im running Xcode Version 4.3.2 on OSX 10.7.4 -- Ticket URL: <https://trac.macports.org/ticket/35222> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #36131: Error while building apple-gcc42 on OSX 1.8.2
by MacPorts 13 Sep '12

13 Sep '12

#36131: Error while building apple-gcc42 on OSX 1.8.2 --------------------+-------------------------------- Reporter: news@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: apple-gcc42 --------------------+-------------------------------- Hello, I saw this has been discussed multiple times (e.g. #34828) and marked as closed. But looks like the bug has surfaced once again. maddler@lamorte ~> sudo port upgrade outdated ---> Computing dependencies for apple-gcc42 ---> Fetching archive for apple-gcc42 ---> Attempting to fetch apple-gcc42-5666.3_8.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/apple- gcc42 ---> Attempting to fetch apple-gcc42-5666.3_8.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/apple-gcc42 ---> Attempting to fetch apple-gcc42-5666.3_8.darwin_12.x86_64.tbz2 from http://packages.macports.org/apple-gcc42 ---> Fetching distfiles for apple-gcc42 ---> Verifying checksum(s) for apple-gcc42 ---> Extracting apple-gcc42 ---> Applying patches to apple-gcc42 ---> Configuring apple-gcc42 ---> Building apple-gcc42 Error: org.macports.build for port apple-gcc42 returned: command execution failed Please see the log file for port apple-gcc42 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_apple-gcc42/apple-gcc42/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets -- Ticket URL: <https://trac.macports.org/ticket/36131> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #36122: libstdcxx failed to build
by MacPorts 13 Sep '12

13 Sep '12

#36122: libstdcxx failed to build -----------------------+-------------------------------- Reporter: jstrane@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: -----------------------+-------------------------------- OS X 10.8.1 -- Ticket URL: <https://trac.macports.org/ticket/36122> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #34378: Building kdelibs4 with Clang 3.2 fails
by MacPorts 13 Sep '12

13 Sep '12

#34378: Building kdelibs4 with Clang 3.2 fails -------------------------------------------+-------------------------------- Reporter: fraser.hutchison@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: -------------------------------------------+-------------------------------- From main.log after a failed attempt to install Kdevelop: {{{ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdelibs4/kdelibs4/work/kdelibs-4.8.2/kjs/wtf/HashSet.h:184:23: error: use 'template' keyword to treat 'find' as a dependent template name :info:build return m_impl.find<T, Adapter>(value); :info:build ^ :info:build template :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdelibs4/kdelibs4/work/kdelibs-4.8.2/kjs/wtf/HashSet.h:193:23: error: use 'template' keyword to treat 'find' as a dependent template name :info:build return m_impl.find<T, Adapter>(value); :info:build ^ :info:build template :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdelibs4/kdelibs4/work/kdelibs-4.8.2/kjs/wtf/HashSet.h:201:23: error: use 'template' keyword to treat 'contains' as a dependent template name :info:build return m_impl.contains<T, Adapter>(value); :info:build ^ :info:build template :info:build 3 errors generated. }}} The issue can be fixed easily by modifying ..../kdelibs-4.8.2/kjs/wtf/HashSet.h at the indicated points by adding "template" e.g. changing to: {{{ return m_impl.template find<T, Adapter>(value); }}} -- Ticket URL: <https://trac.macports.org/ticket/34378> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 16