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

[MacPorts] #32428: PortGroup muniversal not documented
by MacPorts 26 Sep '14

26 Sep '14

#32428: PortGroup muniversal not documented --------------------------------+------------------------------------------- Reporter: abarnert@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.0.3 Keywords: | Port: --------------------------------+------------------------------------------- While trying to work around #32427 I ran into the problem that I have no idea what exactly !PortGroup muniversal does, or how or why. While searching this site for muniversal, I found a number of other bugs that were either caused or fixed by changing a port to muniversal, but there's no mention of it in ProblemHotlist. The Guide describes a handful of portgroups (under 5.9): gnustep, haskell, perl5, python, python2, ruby, xcode), but not muniversal. It also has an explanation on how to set up universal builds, with no mention of muniversal. The manpage portgroup(7) describes a different set: gnustep, perl5, python24, python25, python30, ruby, xcode. Looking in $prefix/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/ there are 34 groups, many of which have brief comments explaining their purpose, but muniversal (which seems to be one of the more complex ones) doesn't. The PortfileRecipes page has some information on controlling -arch and related things; I don't know if muniversal is relevant here. A ticket search, a Google site search, a Google web search, etc. turned up lots and lots of discussion about applying muniversal to specific ports, but I couldn't find anything explaining muniversal. From the name, it's pretty obvious that it has something to do with universal builds, and a quick scan of the source confirms that. From what I can tell, just including the portgroup without doing anything else causes +universal builds to be done by building each architecture separately and then merging, instead of attempting a single build with multiple architectures. In summary, I think muniversal needs to be documented in: * Guide section 5.3.7.1 (Configure Universal) * Guide section 5.9 (!PortGroups) * Man page portgroup(7) * PortfileRecipes * ProblemHotlist * Header comments in the group file itself Ideally these should explain what it does, when and why you should (or shouldn't) use it, how to experiment with turning it on and off to resolve common problems with +universal builds, etc. -- Ticket URL: <https://trac.macports.org/ticket/32428> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #32034: snort: libsf_engine.dylib: No such file or directory
by MacPorts 26 Sep '14

26 Sep '14

#32034: snort: libsf_engine.dylib: No such file or directory -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: haspatch | Port: snort -------------------------------------+-------------------------------------- Actually trying to use snort produces the error message: {{{ /opt/local/lib/snort_dynamicengine/libsf_engine.dylib: No such file or directory }}} as [http://lists.macosforge.org/pipermail/macports- users/2011-November/026101.html reported by Fyodor Vassiley with a reproduction recipe on the mailing list]. snort installs the file libsf_engine.so there, but then later looks for libsf_engine.dylib, which isn't there. So it would be best if the libraries were installed with the correct .dylib extension in the first place. [http://lists.macosforge.org/pipermail/macports- users/2011-November/026133.html Jean-Francois Gobin provided a patch on the mailing list], but it must be applied to the Makefile after the configure phase has run. I don't know if there's a way the patch could be done at the normal time, during the patch phase. Perhaps a patch to the configure script. -- Ticket URL: <https://trac.macports.org/ticket/32034> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #31031: net/zabbix
by MacPorts 26 Sep '14

26 Sep '14

#31031: net/zabbix --------------------------------+------------------------------------------- Reporter: kwcheong@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.1 Keywords: | Port: net/zabbix --------------------------------+------------------------------------------- Upgraded to 1.8.6 and included variants proxy for proxy build instead of server. In addition, splitted the zabbix_agentd into another port so that startupitem (for both) can handle correctly. -- Ticket URL: <https://trac.macports.org/ticket/31031> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #25170: PortGroup php5extension documentation
by MacPorts 26 Sep '14

26 Sep '14

#25170: PortGroup php5extension documentation --------------------------------------+------------------------------------- Reporter: rodney.rehm@… | Owner: markd@… Type: request | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.8.2 Keywords: | Port: --------------------------------------+------------------------------------- I just wanted to create a Portfile for igbinary (http://opensource.dynamoid.com/) and figured to use the php5exension PortGroup. But since igbinary is no ordinary PECL, I couldn't just copypaste some other Portfile. Thus I'd have to get some info on how to use that php5extension PortGroup properly. But there's nothing in the Guide. (Not urgent, just for testing at the moment) -- Ticket URL: <http://trac.macports.org/ticket/25170> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #40025: VLC: configure fails when using ffmpeg-devel
by MacPorts 26 Sep '14

26 Sep '14

#40025: VLC: configure fails when using ffmpeg-devel ----------------------+------------------------ Reporter: devans@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: ffmpeg | Port: VLC ----------------------+------------------------ When building VLC 2.0.8 using ffmpeg-devel (ffmpeg-2.0), configure fails as follows: {{{ checking if linker supports -Bsymbolic... no checking for AVCODEC... yes configure: error: libavcodec versions 55 and later are not supported yet. Command failed: cd "/opt/local/var/macports/build/_opt_macports_trunk_dports_multimedia_VLC/VLC/work/vlc-2.0.8" && ./configure --prefix=/opt/local --with-macosx-version-min=10.8 --with- contrib=/opt/local/var/macports/build/_opt_macports_trunk_dports_multimedia_VLC/VLC/work/vlc-2.0.8/contrib --disable-debug --disable-update-check --enable-gnutls --disable-notify --disable-telepathy --disable-dbus --disable-growl --enable-libproxy --enable-lua --enable-dvdnav --enable-dvdread --disable-smb --disable-vcdx --disable-macosx-eyetv --disable-realrtsp --enable-sftp --disable-dvbpsi --enable-ogg --enable-mux_ogg --enable-mkv --disable-shout --enable-a52 --enable-faad --enable-flac --disable-live555 --enable-opus --enable- vorbis --enable-ogg --enable-mad --disable-libass --enable-dca --enable- png --disable-quicktime --enable-twolame --disable-speex --enable-theora --enable-x264 --enable-postproc --enable-avcodec --enable-avformat --enable-swscale --enable-fluidsynth --disable-caca --disable-sdl --without-x --disable-xcb --disable-xvideo --disable-glx --disable-fribidi --disable-svg --disable-jack --enable-samplerate --disable-qt4 --enable- ncurses --disable-skins2 --disable-goom --enable-bonjour --enable-upnp --enable-macosx-vout --enable-macosx-audio --with-macosx-sdk=/ --enable- macosx-vlc-app --enable-macosx-qtkit --enable-mod --enable-mpc --enable- freetype --enable-fontconfig --enable-macosx --enable-macosx-dialog- provider Exit code: 1 }}} Build log attached -- Ticket URL: <https://trac.macports.org/ticket/40025> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #29963: smokeping @2.4.2 +Prototype mismatch: sub SNMP_Session::AF_INET6
by MacPorts 25 Sep '14

25 Sep '14

#29963: smokeping @2.4.2 +Prototype mismatch: sub SNMP_Session::AF_INET6 --------------------------------------+------------------------------------- Reporter: filter@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: --------------------------------------+------------------------------------- I installed smokeping on OS X 10.6.7. Experienced the following error when loading smokeping: {{{ Constant subroutine SNMP_Session::AF_INET6 redefined at /opt/local/lib/perl5/5.12.3/Exporter.pm line 64. at /opt/local/lib/smokeping/SNMP_Session.pm line 129 Prototype mismatch: sub SNMP_Session::AF_INET6 () vs none at /opt/local/lib/perl5/5.12.3/Exporter.pm line 64. at /opt/local/lib/smokeping/SNMP_Session.pm line 582 Prototype mismatch: sub SNMPv1_Session::AF_INET6 () vs none at /opt/local/lib/perl5/5.12.3/Exporter.pm line 64. at /opt/local/lib/smokeping/SNMP_Session.pm line 582 Constant subroutine SNMPv1_Session::PF_INET6 redefined at /opt/local/lib/perl5/5.12.3/Exporter.pm line 64. }}} I forced manual update of Socket6 and NET::SNMP with: {{{ cpan> install U/UM/UMEMOTO/Socket6-0.23.tar.gz cpan> install Crypt::Rijndael (a NET::SNMP dependency) cpan> install D/DT/DTOWN/Net-SNMP-v6.0.1.tar.gz }}} Reloaded smokeping, and everything works perfectly. Next, I attempted to install smokeping on an older host running 10.5.x. Experienced the same error when starting smokeping. However, this time, updating Socket6 and NET::SNMP did nothing to resolve the errors. System details:[[BR]] OS X 10.5[[BR]] [[BR]] PERL v.5.12.3[[BR]] CPAN v1.9600[[BR]] Relevant installed perl packages:[[BR]] IO::Socket v.1.31[[BR]] IO::Socket::INET6 v.2.67[[BR]] Socket6 v.0.23[[BR]] Exporter.pm line 64 reads: {{{ sub import { ..... 63 # shortcut for the common case of no type character 64 *{"$callpkg\::$_"} = \&{"$pkg\::$_"} foreach @_; 65 } }}} /opt/local/lib/smokeping/SNMP_Session.pm line 129 reads: {{{ 123 BEGIN { 124 $ipv6_addr_len = undef; 125 $SNMP_Session::ipv6available = 0; 126 127 if (eval {require Socket6;} && 128 eval {require IO::Socket::INET6; IO::Socket::INET6->VERSION("1.26");}) { 129 import Socket6; 130 $ipv6_addr_len = length(pack_sockaddr_in6(161, inet_pton(AF_INET6(), "::1"))); 131 $SNMP_Session::ipv6available = 1; 132 } 133 } }}} /opt/local/lib/smokeping/SNMP_Session.pm line line 582 reads: {{{ 579 BEGIN { 580 if($SNMP_Session::ipv6available) { 581 import IO::Socket::INET6; 582 import Socket6; 583 } 584 } }}} Seems like this has something to do with Socket6 naming, but I'll defer to the experts here. If this requires upstream inclusion, please assist, as I am not certain whose shoulder to tap on. -- Ticket URL: <https://trac.macports.org/ticket/29963> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #28923: rancid: universal variant fails
by MacPorts 25 Sep '14

25 Sep '14

#28923: rancid: universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: rancid -------------------------------------+-------------------------------------- rancid's universal variant fails: {{{ ccache /usr/bin/gcc-4.2 -DHAVE_CONFIG_H -I. -I../include -I/opt/local/include -g -O0 -c hpuifilter.c ccache /usr/bin/gcc-4.2 -g -O0 -L/opt/local/lib -arch x86_64 -arch i386 -o hpuifilter hpuifilter.o ld: warning: in hpuifilter.o, file was built for unsupported file format which is not the architecture being linked (i386) Undefined symbols for architecture i386: "_main", referenced from: start in crt1.10.6.o ld: symbol(s) not found for architecture i386 collect2: ld returned 1 exit status }}} Note the lack of -arch flags on the first line. I expect this means non- default-build_arch builds would fail too. -- Ticket URL: <https://trac.macports.org/ticket/28923> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #24897: document test.dir in guide
by MacPorts 25 Sep '14

25 Sep '14

#24897: document test.dir in guide -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: guide | Version: Keywords: | Port: -------------------------------------+-------------------------------------- The guide talks about other test phase variables but not test.dir -- Ticket URL: <http://trac.macports.org/ticket/24897> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #24318: assign variable value in variant
by MacPorts 25 Sep '14

25 Sep '14

#24318: assign variable value in variant -------------------------------------------+-------------------------------- Reporter: mattiafrancescomoro@… | Owner: markd@… Type: request | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.8.2 Keywords: | Port: -------------------------------------------+-------------------------------- Please add a guide wich explain how i can add in a variant box a code execution ie: {{{ variant python description {Builds port with python support} { pythonincdir=`python-config --includes | sed -e 's/-I//' | awk '{print \$1}'` configure.args-delete --disable-python` configure.args-append --enable-python \ --with-python-incdir=pythonincdir \ --with-python- libdir="${prefix}/lib" } }}} Thank you! -- Ticket URL: <http://trac.macports.org/ticket/24318> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #23837: Missing test.args keyword in the MacPorts Guide
by MacPorts 25 Sep '14

25 Sep '14

#23837: Missing test.args keyword in the MacPorts Guide ----------------------------------+----------------------------------------- Reporter: macosx12345@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.8.2 Keywords: test.args | Port: ----------------------------------+----------------------------------------- In the current version of the MacPorts Guide, the "test.args" keyword is not mentioned in Section 5.3.9, "Test Phase Keywords", but this keyword does exist (I have tested it with MacPorts 1.8.2) and proves useful. Actually, this keyword is mentioned nowhere in the Guide. I suspect that the keywords test.pre_args and test.post_args also exist, although I have not checked this. I suggest that they get mentioned in Section 5.3.9 of the Guide. Thank you! -- Ticket URL: <http://trac.macports.org/ticket/23837> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1