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

[MacPorts] #44568: s3fs requires new osxfuse
by MacPorts 07 Aug '14

07 Aug '14

#44568: s3fs requires new osxfuse ----------------------+-------------------------------- Reporter: jeremy@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: s3fs ----------------------+-------------------------------- I have the latest osxfuse installed, which appears to be 2.7.3: Jeremys-MacBook-Pro-3:~ jeremy$ pkg-config --modversion osxfuse 2.7.3 However, s3fs seems to require a newer version of osxfuse: Jeremys-MacBook-Pro-3:~ jeremy$ sudo port install s3fs ---> Computing dependencies for s3fs ---> Configuring s3fs Error: Failed to configure s3fs, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_s3fs/s3fs/work/s3fs-1.61/config.log Error: org.macports.configure for port s3fs returned: configure failure: command execution failed Please see the log file for port s3fs for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_s3fs/s3fs/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port s3fs failed From the config log file: configure:3230: $PKG_CONFIG --exists --print-errors "fuse >= 2.8.4 libcurl >= 7.0 libxml-2.0 >= 2.6 libcrypto >= 0.9" Requested 'fuse >= 2.8.4' but version of fuse is 2.7.3 configure:3233: $? = 1 configure:3246: $PKG_CONFIG --exists --print-errors "fuse >= 2.8.4 libcurl >= 7.0 libxml-2.0 >= 2.6 libcrypto >= 0.9" Requested 'fuse >= 2.8.4' but version of fuse is 2.7.3 configure:3249: $? = 1 configure:3262: result: no Requested 'fuse >= 2.8.4' but version of fuse is 2.7.3 configure:3278: error: Package requirements (fuse >= 2.8.4 libcurl >= 7.0 libxml-2.0 >= 2.6 libcrypto >= 0.9) were not met: Requested 'fuse >= 2.8.4' but version of fuse is 2.7.3 -- Ticket URL: <https://trac.macports.org/ticket/44568> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #44562: error when building dubs
by MacPorts 07 Aug '14

07 Aug '14

#44562: error when building dubs --------------------------+-------------------------------- Reporter: ac.russell@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: --------------------------+-------------------------------- I am doing an upgrade of several ports and am getting this error when it gets to dbus ---> Building dbus Error: org.macports.build for port dbus returned: command execution failed Please see the log file for port dbus for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_dbus/dbus/main.log Error: Unable to upgrade port: 1 Error rebuilding dbus-glib while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 395) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_upgrade" line 25) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 93) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 5254) dbus/main.log is attached Any advice on how to get through this? Thanks! -- Ticket URL: <https://trac.macports.org/ticket/44562> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #41241: vxl fails to build on OS X 10.9 Maverick
by MacPorts 07 Aug '14

07 Aug '14

#41241: vxl fails to build on OS X 10.9 Maverick --------------------------------------+-------------------------------- Reporter: andreas.schuh.84@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: vxl, maverick, os x 10.9 | Port: vxl --------------------------------------+-------------------------------- {{{ :info:build /Applications/Xcode.app/Contents/Developer/usr/bin/make -f core/vbl/tests/CMakeFiles/vbl_test_all.dir/build.make core/vbl/tests/CMakeFiles/vbl_test_all.dir/depend :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0/core/vul/vul_psfile.cxx:2: :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0/core/vul/vul_psfile.h:40:28: error: cannot cast from type 'std::ofstream' (aka 'basic_ofstream<char>') to pointer type 'void *' :info:build operator bool() { return (void*)output_filestream!=(void*)0; } :info:build ^~~~~~~~~~~~~~~~~~~~~~~~ }}} When I change this line to {{{ // or should this be !output_filestream.bad() && !output_filestream.fail() ? return output_filestream.good() }}} it continues past this point but then I get the following error: {{{ cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0/core/vbl/io/tests && /usr/bin/clang++ -DVXL_LEGACY_ERROR_REPORTING -DVXL_WARN_DEPRECATED -DVXL_WARN_DEPRECATED_ONCE -pipe -Os -Werror=gnu -Wno-error=vla -I/opt/local/include -arch x86_64 -DNDEBUG -arch x86_64 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0/vcl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0/core -o CMakeFiles/vbl_io_test_all.dir/test_smart_ptr_io.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0/core/vbl/io/tests/test_smart_ptr_io.cxx :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0/core/vil/file_formats/vil_openjpeg.cxx:107:3: error: unknown type name 'opj_codec_t'; did you mean 'opj_poc_t'? :info:build opj_codec_t *codec_; :info:build ^~~~~~~~~~~ }}} -- Ticket URL: <https://trac.macports.org/ticket/41241> MacPorts <http://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #44539: VXL installation on OSX 10.9.4
by MacPorts 07 Aug '14

07 Aug '14

#44539: VXL installation on OSX 10.9.4 ---------------------+-------------------------------- Reporter: garry@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: VXL ---------------------+-------------------------------- Repeated errors. Sorry I'm a noob at this but I have spent the night banging at it repeatedly to no avail.. log file extract as follows.... :info:build [ 25%] Built target vnl :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_vxl/vxl/work/vxl-1.17.0" && /usr/bin/make -j8 -w all :info:build Exit code: 2 :error:build org.macports.build for port vxl returned: command execution failed :debug:build Error code: CHILDSTATUS 41200 2 :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 "portbuild::build_main org.macports.build" ("eval" body line 1) invoked from within "eval $procedure $targetname" -- Ticket URL: <https://trac.macports.org/ticket/44539> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #44563: ansible: update to 1.7
by MacPorts 07 Aug '14

07 Aug '14

#44563: ansible: update to 1.7 ----------------------+-------------------------------- Reporter: zdw@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: haspatch | Port: ansible ----------------------+-------------------------------- Update Ansible to 1.7 Was at 1.6.6. Also, fixes security issues per the release notes: http://www.ansible.com/blog/ansible-1.7-is-released-windows-beta-and-more -- Ticket URL: <https://trac.macports.org/ticket/44563> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #44408: libgcrypt 1.6.1 fails to build on PPC
by MacPorts 07 Aug '14

07 Aug '14

#44408: libgcrypt 1.6.1 fails to build on PPC -------------------------+-------------------------------- Reporter: drjesacco@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: libgcrypt -------------------------+-------------------------------- libgcrypt 1.6.1 fails to build on a PPC. The problem is with ./mpi/config.links, which is used to detect which MPI ASM to use. I did a web search and found a solution that works https://github.com/mistydemeo/tigerbrew/issues/171 I have created a patch. -Joseph -- Ticket URL: <https://trac.macports.org/ticket/44408> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #44554: build of libgcrypt 1.6.1 fails on ppc
by MacPorts 07 Aug '14

07 Aug '14

#44554: build of libgcrypt 1.6.1 fails on ppc ---------------------------------------+-------------------------------- Reporter: mail_commercial@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: libgcrypt patch configure | Port: ---------------------------------------+-------------------------------- There's a bug into the configuration script of libgcrypt 1.6.1 for the the powerpc-darwin platform. This bug leads to the build of x386 binaries instead of ppc binaries. I followed the instructions of this thread to patch the mpi/config.links file : https://github.com/mistydemeo/tigerbrew/issues/171 Is it possible to introduce this patch into the libgcrypt port ? Regards Patrice Fontaine -- Ticket URL: <https://trac.macports.org/ticket/44554> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #44470: signify @1.1 - File signing and verification utility from OpenBSD
by MacPorts 07 Aug '14

07 Aug '14

#44470: signify @1.1 - File signing and verification utility from OpenBSD ------------------------+-------------------------------- Reporter: jpo@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: maintainer | Port: signify ------------------------+-------------------------------- This is an OS X port of OpenBSD's [signify](http://www.openbsd.org/cgi- bin/man.cgi/OpenBSD-current/man1/signify.1) utility. -- Ticket URL: <https://trac.macports.org/ticket/44470> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #39881: html-xml-utils @6.3_0 Odd --program-prefix
by MacPorts 07 Aug '14

07 Aug '14

#39881: html-xml-utils @6.3_0 Odd --program-prefix ------------------------+-------------------------------- Reporter: smurfair@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Low | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: html-xml-utils ------------------------+-------------------------------- I just noticed that this Portfile contains the peculiar: {{{ configure.args --program-prefix=w3 }}} This builds the executables, prefixing their names so that ''hxselect'', for instance, becomes ''w3hxselect''. This could cause confusion, with shared scripts for example, since that naming convention doesn't seem to exist anywhere beyond MacPorts. I pruned that line from my Portfile and did a custom build, but I wouldn't presume to submit it as a replacement since that would then potentially mess up the workflow of anybody using the existing version. Would it be possible for the port to be installed with the addition of "properly" named symlinks pointing to executables or vice versa? -- Ticket URL: <https://trac.macports.org/ticket/39881> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #42735: SWFTools install failure on Mac OS 10.9.2
by MacPorts 07 Aug '14

07 Aug '14

#42735: SWFTools install failure on Mac OS 10.9.2 ------------------------------+-------------------------------- Reporter: gregoryhansell@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: SWFTools ------------------------------+-------------------------------- Downloaded Macports today for the first time and was able to do other installs successfully. Tried to port SWFTools but failed. Did a clean on this port, same errors. Thanks for any help you could give me! I looked around through Search and FAQ and couldn't work this out myself. Thank you again! Error log attached. -- Ticket URL: <https://trac.macports.org/ticket/42735> MacPorts <http://www.macports.org/> Ports system for OS X

1 9