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

[MacPorts] #38238: tktable: build fails on Mountain Lion, error: incomplete definition of type 'struct _XDisplay'
by MacPorts 26 Sep '14

26 Sep '14

#38238: tktable: build fails on Mountain Lion, error: incomplete definition of type 'struct _XDisplay' -----------------------+-------------------------------- Reporter: aronnax@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: tktable -----------------------+-------------------------------- tktable fails to build on Mountain Lion with the following error message: See attached build log. -- Ticket URL: <https://trac.macports.org/ticket/38238> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #38000: ntop @5.0.1 fails to build on 10.5 ppc
by MacPorts 26 Sep '14

26 Sep '14

#38000: ntop @5.0.1 fails to build on 10.5 ppc ----------------------------+-------------------------------- Reporter: jbenninghoff@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ntop ----------------------------+-------------------------------- ntop build fails on 10.5 ppc, possibly due to byte order problems. Log file attached. -- Ticket URL: <https://trac.macports.org/ticket/38000> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #37366: Enhancement : MacPorts Guide : 2.5 Uninstall macports user
by MacPorts 26 Sep '14

26 Sep '14

#37366: Enhancement : MacPorts Guide : 2.5 Uninstall macports user ---------------------------+-------------------------------- Reporter: Kenspratlin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: wiki | Version: 2.1.2 Keywords: Uninstall | Port: ---------------------------+-------------------------------- The MacPorts Guide uninstall section (2.5) does not include instructions to delete the macports user account that is created by MacPorts. Also not sure about this, but does MapPorts also create a user account called "mobilebus". -- Ticket URL: <https://trac.macports.org/ticket/37366> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #36957: "subport" is undocumented
by MacPorts 26 Sep '14

26 Sep '14

#36957: "subport" is undocumented --------------------+--------------------- Reporter: dave@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.1.2 Keywords: | Port: --------------------+--------------------- I find it used in a few of the official ports, but can't find anything about it on the portfile manpage (or any of the others). -- Ticket URL: <https://trac.macports.org/ticket/36957> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #36427: base port five years out-of-date
by MacPorts 26 Sep '14

26 Sep '14

#36427: base port five years out-of-date -------------------------+-------------------------------- Reporter: s.t.smith@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: security | Port: base -------------------------+-------------------------------- The base port (v. 1.3.9) is now five years out of date, and missing a lot of security updates (like plugging a potential SQL injection) and shiny bells and whistles like a world map feature: http://base.secureideas.net/ It would be great, and more secure, if the latest version (1.4.5, itself two years old) could be added to Macports. -- Ticket URL: <https://trac.macports.org/ticket/36427> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #34885: nagios-plugins does not list library dependencies
by MacPorts 26 Sep '14

26 Sep '14

#34885: nagios-plugins does not list library dependencies ------------------------------------------+--------------------------------- Reporter: dirk.schulz@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: missing library dependencies | Port: nagios-plugins ------------------------------------------+--------------------------------- sudo port deps nagios-plugins Full Name: nagios-plugins @1.4.15_4 Build Dependencies: fping, p5.12-net-snmp, p5.12-digest-sha1, p5.12 -digest-hmac, p5.12-crypt-des, openssl This leads to nagios plugins not working due to missing libraries when using port mpkg to package nagios-plugins for installation on macs without macports. -- Ticket URL: <https://trac.macports.org/ticket/34885> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #34702: Failed to install nagios-plugins
by MacPorts 26 Sep '14

26 Sep '14

#34702: Failed to install nagios-plugins -----------------------------+---------------------------------------------- Reporter: devinb@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: -----------------------------+---------------------------------------------- Using: MacPorts 2.1.1 Attempting to get nagios installed via MacPorts and keep running into this problem {{{ $ sudo port install nagios ---> Computing dependencies for nagios ---> Dependencies to be installed: nagios-plugins ---> Building nagios-plugins Error: org.macports.build for port nagios-plugins returned: command execution failed Error: Failed to install nagios-plugins Please see the log file for port nagios-plugins for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_net_nagios-plugins/nagios-plugins/main.log Error: The following dependencies were not installed: nagios-plugins To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port nagios failed }}} -- Ticket URL: <https://trac.macports.org/ticket/34702> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #33697: Incomplete uninstall script
by MacPorts 26 Sep '14

26 Sep '14

#33697: Incomplete uninstall script --------------------------------+------------------------------------------- Reporter: neville@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 2.0.5 Component: ports | Version: 2.0.4 Keywords: | Port: --------------------------------+------------------------------------------- The uninstall script at http://guide.macports.org/chunked/installing.macports.uninstalling.html fails to remove /private/var/db/dslocal/nodes/Default/users/macports.plist /private/var/db/dslocal/nodes/Default/groups/macports.plist which leaves user-name (macports), group (macports) and ID (typically 503) on the database causing confusion and minor inconvenience. Users become aware of this when changing permissions in Get Info or using AppleJack etc. Removing these 2 plist files works with Leopard and probably works with later OSs. Correcting and testing the script should be relatively easy. -- Ticket URL: <https://trac.macports.org/ticket/33697> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #33479: p5.12-cgi-speedycgi fails to build with clang
by MacPorts 26 Sep '14

26 Sep '14

#33479: p5.12-cgi-speedycgi fails to build with clang ------------------------------------+--------------------------------------- Reporter: arno.barbier@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: p5.12-cgi-speedycgi ------------------------------------+--------------------------------------- Hello, I couldn't build p5.12-cgi-speedycgi due to the following error: {{{ :info:build /usr/bin/clang -o speedy_backend speedy_backend_main.o speedy_perl.o speedy_util.o speedy_sig.o speedy_frontend.o speedy_backend.o speedy_file.o speedy_slot.o speedy_poll.o speedy_ipc.o speedy_group.o speedy_script.o speedy_opt.o speedy_optdefs.o xsinit.o -L/opt/local/lib -fstack-protector -L/opt/local/lib/perl5/5.12.3/darwin- multi-2level/CORE -lperl -ldl -lm -lutil -lc :info:build Undefined symbols for architecture x86_64: :info:build "_speedy_file_set_state", referenced from: :info:build _main in speedy_backend_main.o :info:build _start_child in speedy_backend_main.o :info:build _cleanup_after_perl in speedy_perl.o :info:build _speedy_perl_run in speedy_perl.o :info:build _speedy_file_fork_child in speedy_file.o :info:build _speedy_group_lock in speedy_group.o :info:build "_speedy_util_getpid", referenced from: :info:build _main in speedy_backend_main.o :info:build _start_child in speedy_backend_main.o :info:build _cleanup_after_perl in speedy_perl.o :info:build _speedy_perl_run in speedy_perl.o :info:build _file_lock in speedy_file.o :info:build "_speedy_util_stat_devino", referenced from: :info:build _speedy_perl_init in speedy_perl.o :info:build _quick_cd in speedy_perl.o :info:build _chdir_path in speedy_perl.o :info:build "_speedy_opt_script_fname", referenced from: :info:build _speedy_perl_init in speedy_perl.o :info:build _speedy_script_open_failure in speedy_script.o :info:build _speedy_script_open in speedy_script.o :info:build _speedy_script_getstat in speedy_script.o :info:build _speedy_script_find in speedy_script.o :info:build _speedy_script_mmap in speedy_script.o :info:build "_speedy_file_fd_is_suspect", referenced from: :info:build _cleanup_after_perl in speedy_perl.o :info:build "_speedy_util_open_stat", referenced from: :info:build _load_script in speedy_perl.o :info:build _speedy_script_open_failure in speedy_script.o :info:build "_speedy_util_time", referenced from: :info:build _file_lock in speedy_file.o :info:build _speedy_script_open_failure in speedy_script.o :info:build (maybe you meant: _speedy_util_time_invalidate) :info:build "_speedy_util_gettimeofday", referenced from: :info:build _file_lock in speedy_file.o :info:build "_speedy_util_geteuid", referenced from: :info:build _speedy_ipc_listen in speedy_ipc.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[1]: *** [speedy_backend] Error 1 }}} The package source name is p5.12-cgi- speedycgi-2.220.0_11.darwin_11.x86_64.tbz2 Thanks for your help -- Ticket URL: <https://trac.macports.org/ticket/33479> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[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