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

[MacPorts] #47181: Enabled java support in octave
by MacPorts 18 Mar '15

18 Mar '15

#47181: Enabled java support in octave -------------------------+-------------------------------- Reporter: mguthaus@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: octave,java | Port: octave -------------------------+-------------------------------- The portfile had --disable-java option during configuration, but it compiles fine without this. I also tested with a package that uses the java extensions and it worked fine. -- Ticket URL: <https://trac.macports.org/ticket/47181> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #16792: Request for new port: rkhunter
by MacPorts 18 Mar '15

18 Mar '15

#16792: Request for new port: rkhunter -------------------------+-------------------------------- Reporter: ralph@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rkhunter | -------------------------+-------------------------------- Comment (by mschamschula@…): Updated Portfile and rkhunter.conf.local.sample to not hard code ${prefix}. Also edited rkhunter.conf.local.sample to list files not present in OS X 10.5 and 10.10. These files as well as MacPorts files are now commented out. -- Ticket URL: <https://trac.macports.org/ticket/16792#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #34750: py32-numpy fails to build on snow leopard/XCode4.2
by MacPorts 18 Mar '15

18 Mar '15

#34750: py32-numpy fails to build on snow leopard/XCode4.2 -----------------------------+-------------------- Reporter: miguel.barao@… | Owner: dh@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: fixed | Keywords: Port: py-numpy | -----------------------------+-------------------- Changes (by michaelld@…): * status: new => closed * resolution: => fixed Comment: Works for me. -- Ticket URL: <https://trac.macports.org/ticket/34750#comment:15> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #47188: Cannot build cmake 3.2.1
by MacPorts 18 Mar '15

18 Mar '15

#47188: Cannot build cmake 3.2.1 -----------------------------+-------------------------------- Reporter: charlie.clark@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: cmake -----------------------------+-------------------------------- cmake failed to build after syncing the repo. Log enclosed -- Ticket URL: <https://trac.macports.org/ticket/47188> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #47149: frescobaldi @2.17.2_1: update to 2.18
by MacPorts 18 Mar '15

18 Mar '15

#47149: frescobaldi @2.17.2_1: update to 2.18 ---------------------------------+-------------------------------- Reporter: davide.liessi@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch maintainer | Port: frescobaldi ---------------------------------+-------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/47149> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #46623: procmail on OS X Yosemite hits "Abort trap: 6" if variable assignment uses backticks
by MacPorts 18 Mar '15

18 Mar '15

#46623: procmail on OS X Yosemite hits "Abort trap: 6" if variable assignment uses backticks ------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: procmail | Port: mail/procmail ------------------------+-------------------------------- If my `.procmailrc` file contains a variable assignment like this {{{ FROM=`sed 1d | formail -I reply-to: -I resent-from: -I return-path: | \ formail -rzxTo:` }}} then procmail hits an "Abort trap: 6" as follows: {{{ mini1:~ collin$ cat Mail/backup/92862 | formail -imessage-id: | /opt/local/bin/procmail .procmailrc.1.18 Abort trap: 6 mini1:~ collin$ }}} /usr/bin/procmail displays the same symptom. Both binaries are version 3.22 (they display the same version string as in `procmail -v` string), though they have some different attributes: {{{ mini1:~ collin$ ls -l /usr/bin/procmail /opt/local/bin/procmail -rwsr-sr-x 1 root mail 97612 Dec 7 01:23 /opt/local/bin/procmail -rwxr-sr-x 1 root mail 84576 Sep 9 15:57 /usr/bin/procmail mini1:~ collin$ file /usr/bin/procmail /opt/local/bin/procmail /usr/bin/procmail: setgid Mach-O 64-bit executable x86_64 /opt/local/bin/procmail: setuid setgid Mach-O 64-bit executable x86_64 mini1:~ collin$ }}} Removing the `FROM=...` line makes the problem go away--i.e., procmail does what I expect (and indeed what it does do on Linux, and what /usr/bin/procmail formerly did on Mac OS X 10.6.8). The same .procmailrc script has worked OK for a few years on a mac mini. Until 2 days back, this mac mini had been running 10.6.8 (not sure when the last OS upgrade was, but it has been months). I was hoping for a coredump so I naively tried "`ulimit -c unlimited`" but no coredump appeared after the abort. The backtick sequence inside a recipe doesn't provoke an abort; the following works just fine: {{{ :0 ic | cd backup && rm -f dummy `ls -t | sed -e 1,128d` }}} It seems to be only a line of the form {{{ VAR=`cmd` }}} that the current procmail (both /usr/bin/procmail and the port) hates. Also: I tried replacing the long "FROM=" line above by {{{ FROM=`cat` }}} which also proved disappointing -- Ticket URL: <https://trac.macports.org/ticket/46623> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #47176: [mongodb] Update to 3.0.1
by MacPorts 18 Mar '15

18 Mar '15

#47176: [mongodb] Update to 3.0.1 --------------------+-------------------------------- Reporter: mark@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: mongodb --------------------+-------------------------------- As is usual with x.0.0 releases, there is already an update. Looks like this does include at least one [https://jira.mongodb.org/browse/SERVER-14166 OS X-specific fix] amongst about [https://jira.mongodb.org/browse/SERVER-17521?jql=project%20%3D%20server%20a… four dozen total fixes]. Thanks! -- Ticket URL: <https://trac.macports.org/ticket/47176> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #47116: Unable to upgrade port ffmpeg
by MacPorts 18 Mar '15

18 Mar '15

#47116: Unable to upgrade port ffmpeg ---------------------------------+-------------------------------- Reporter: rafael.ruiz.munoz@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: ffmpeg opencv | Port: ffmpeg ---------------------------------+-------------------------------- Hello. I've tried everything on this web, StackOverflow and OpenCV support. My OS is Yosemite and current OpenCV is 2.4.9 I'm trying to install OpenCV with TBB, but when I do it by {{{ sudo port install opencv +debug +python27 +qt4 +tbb }}} (through this SO question - http://stackoverflow.com/questions/13424305 /how-to-get-all-available-install-options-for-a-port): {{{ Rafaels-iMac:y3PQFyQhUG rafaelruizmunoz$ sudo port install opencv +debug +python27 +qt4 +tbb Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build. Warning: Install them by running 'xcode-select --install'. Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build. Warning: Install them by running xcode-select --install'. ---> Computing dependencies for ffmpeg ---> Configuring ffmpeg Error: Failed to configure ffmpeg, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-2.6/config.log Error: org.macports.configure for port ffmpeg returned: configure failure: command execution failed Please see the log file for port ffmpeg for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade ffmpeg failed }}} And there are not any logs on those paths. I've tried (support from SO and MacPorts). - port selfupdate - port upgrade ffmpeg - port clean x264 - port upgrade outdated - port -f selfupdate but nothing happened. Does anyone have a clue? Thank you in advance. EDIT: Doing xcode-select --install doesn't resolve anything. -- Ticket URL: <https://trac.macports.org/ticket/47116> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #47173: getopt-1.1.6 fails to build on 10.4 PPC
by MacPorts 18 Mar '15

18 Mar '15

#47173: getopt-1.1.6 fails to build on 10.4 PPC --------------------+-------------------------------- Reporter: nad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: getopt --------------------+-------------------------------- That `-arch x86_64` doesn't belong there. r134016 looks suspicious. {{{ CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/macports/var/macports/build/_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_getopt/getopt/work/.CC_ PRINT_OPTIONS' CPATH='/macports/include' LIBRARY_PATH='/macports/lib' MACOSX_DEPLOYMENT_TARGET='10.4' :debug:build Assembled command: 'cd "/macports/var/macports/build/_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_getopt/ge topt/work/getopt-1.1.6" && /usr/bin/make -w all CC=/macports/bin/gcc- apple-4.2 LIBCGETOPT=0 mandir=/macports/share/man prefix=/macports' :debug:build Executing command line: cd "/macports/var/macports/build/_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_geto pt/getopt/work/getopt-1.1.6" && /usr/bin/make -w all CC=/macports/bin/gcc- apple-4.2 LIBCGETOPT=0 mandir=/macports/share/man prefix=/macports :info:build make: Entering directory `/macports/var/macports/build/_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_getopt/g etopt/work/getopt-1.1.6' :info:build /macports/bin/gcc-apple-4.2 -c -DLIBCGETOPT=0 -DWITHOUT_GETTEXT=0 -DLOCALEDIR=\"/macports/share/locale\" -DNOT_UTIL_LINUX -Dprogram_invocation_sh ort_name=\"getopt\" -Dprogram_version=\"1.1.6\" -I/macports/include -I./gnu -Wall -W -Wshadow -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Wwrite-strings -Wstrict-prototypes -Wmissing- prototypes -Wnested-externs -Winline -O3 -fno-strength-reduce -arch x86_64 -arch ppc get opt.c -o getopt.o :info:build gcc-apple-4.2: error trying to exec '/macports/bin/i686-apple- darwin8-gcc-apple-4.2.1': execvp: No such file or directory }}} -- Ticket URL: <https://trac.macports.org/ticket/47173> MacPorts <https://www.macports.org/> Ports system for OS X

1 7

Re: [MacPorts] #41600: bison: update to 3.0.2
by MacPorts 18 Mar '15

18 Mar '15

#41600: bison: update to 3.0.2 ------------------------------+---------------------- Reporter: akim.demaille@… | Owner: larryv@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: bison | ------------------------------+---------------------- Comment (by larryv@…): Replying to [comment:54 akim.demaille@…]: > Thanks! It depends on a skip-runtime.patch file though. Oops, [[attachment:skip-runtime-po.patch|here it is]]. > Wow, this stuff is incredibly old... I have tons of warnings I had > not seen in years (e.g., storing constant string in char* without > const). Is it still used? No idea, to be honest. > I have attached a patch, but could not finish the compilation for > other reasons, not related to Bison. If the package is still alive, > it should probably be forwarded, other distros must face the same > issues I guess. I adapted your patch manually, combining it with the [[ticket:46260|already existing patches]], and it builds successfully. I’ve opened #47184 for it. -- Ticket URL: <https://trac.macports.org/ticket/41600#comment:55> MacPorts <https://www.macports.org/> Ports system for OS X

1 0