Re: Port Diagnose Issue - [FAILED] - dylib

On Feb 1, 2017, at 08:48, Christopher Stone wrote: > > Here's the warning/failure notice: > > --- > Warning: found dylibs in your /usr/local/lib directory. These are known to > cause problems. We'd recommend

Re: Problem doing self update on MacPorts version 2.3.4

On Feb 1, 2017, at 23:42, list_em...@icloud.com wrote: > > Trying to do selfupdate and had the following problem. Using Version 2.3.4, > hoping to upgrade. > > Is this a permissions problem on /opt? If so, what should the permissions be? > I prefer changing permissions with Finder or Path

Re: Port diagnose - symlinks

> On Jan 30, 2017, at 20:34, Arno Hautala wrote: > > I ran 'port diagnose' and I think there's an issue with how it handles > symlinks. > > Specifically: > >> Checking for file '/opt/local/libexec/texlive/binaries/a2ping' on disk... >> [FAILED] >> Checking for file

Re: Prevent MacPorts editing .bash_profile over and over again...

> On Jan 31, 2017, at 07:50, Bachsau wrote: > > Am 28.01.2017 um 17:31 schrieb Barry Scott: >> I want to be able to stop MacPorts Installation from editing my >> .bash_profile. >> As it happens I already set all the env var that are needed my self. >> >> Is there a “do-not-edit-bash-profile”

Re: emacs-app fails to start under 10.12.14 beta 1

> On Jan 31, 2017, at 15:42, Artemio González López wrote: > > Emacs-app crashes after launch under the first Developer beta of 10.2.4, with > the following error: > > 2017-01-25 23:50:19.458 Emacs-x86_64-10_9[864:21038] Error - > planarGetBytes count (65536) is not a

Re: pear-PEAR fails to install with checksum error

> On Feb 7, 2017, at 01:43, Horst Simon wrote: > > Hi, > > I tried to install pear and it failed on dependency pear-Archive_Tar install > with checksum error. > > sudo port -N install pear-PEAR > Password: > ---> Computing dependencies for pear-PEAR > --->

Re: Prevent MacPorts editing .bash_profile over and over again...

> On Feb 1, 2017, at 08:20, Bachsau <w...@bachsau.name> wrote: > > Am 01.02.2017 um 07:38 schrieb Ryan Schmidt: >> Sorry. Repeated modifications of the profile when the modifications were >> already there was a bug. It looks like a fix was committed, so hopefu

Re: Port Diagnose Issue - [FAILED] - dylib

> On Feb 2, 2017, at 12:38, Christopher Stone <listmeis...@thestoneforge.com> > wrote: > > On Feb 01, 2017, at 16:20, Ryan Schmidt <ryandes...@macports.org> wrote: >>> The thing I find most odd about this are all the symlinks. >> >

Re: override local port

On Feb 3, 2017, at 07:14, db wrote: > > I guess I could use a git checkout for everything. I wonder how would that > work with the rsync tarball, as it seems not to be documented in the guide. If you are using a git checkout of the complete ports tree (like I am), then you

Re: older lib for port

> On Jan 28, 2017, at 09:54, db wrote: > > Is it feasible to maintain an older lib to compile a certain port? > > I wanted to update ngrep 1.45 (sourceforge) to 1.46 (github) and tried > compiling in a system that had an older version of libpcap, 1.7.4 (current is >

Re: set port not to upgrade

On Feb 17, 2017, at 10:13, db wrote: > I get your point, but wouldn't a warning during build phase suffice? Be it a > leaf or node the port marked to not be upgraded. As of now, if port A, a > leaf, doesn't compile due to a bug in my system version, the only feasible > solution is to move the

Re: pear-PEAR compatibility issue with PHP7

On Feb 22, 2017, at 22:24, Horst Simon wrote: > I tried to use the macports pear with macports php70 and when running pear -V > it throws following error: > PHP Parse error: syntax error, unexpected 'new' (T_NEW) in > /opt/local/lib/php/pear/PEAR/Frontend.php on line 91 > > After searching

Re: avahi 0.6.32 fails to build on Snow Leopard

On Feb 11, 2017, at 18:24, Richard L. Hamilton wrote: > Looks like it's trying to use O_CLOEXEC, which does not appear to exist on > Snow Leopard. (the alternative being to open the file, and then use fctl(fd, > F_SETFD, FD_CLOEXEC) ) > > Yes, I saw that on the buildbot. avahi has no

Re: Inkscape @0.92.0_3+x11 does not work under macOS Sierra 10.12.3!

On Feb 11, 2017, at 13:59, Murray Eisenberg wrote: > The current version, Inkscape @0.92.0_3+x11 current, does not work under > macOS Sierra 10.12.3. > > After starting it from the command line, I see the XQuartz icon appear in the > Dock, then repeatedly disappear and reappear there. And I

Re: README vs installed documentation

On Feb 11, 2017, at 13:15, db wrote: > Sometimes the README files from tarballs is better (re completeness/clarity) > than the installed documentation. Is there any way to include them by default? If a project's build system does not automatically install the readme and other documentation

Re: XQuartz issues [was: Re: Inkscape @0.92.0_3+x11 does not work under macOS Sierra]

On Feb 13, 2017, at 15:14, Murray Eisenberg wrote: > I wrote too hastily about how I fixed XQuartz to cooperate with Inkscape (and > RStudio’s Rcmdr). > > I think I’ve tracked down the source of the XQuartz trouble to file > > ~/.xinitrc.d/90-gnome.sh > > which has contents: > > #

Re: Inkscape @0.92.0_3+x11 does not work under macOS Sierra 10.12.3!

On Feb 12, 2017, at 11:42, Murray Eisenberg wrote: > > I did install port inkscape-app and I get the same behavior — the incessant > appearance and disappearance of the XQuartz icon in the Dock, and NO Inscape > window or items in the menu bar — as when I tried running inkscape from > command

Re: cannot download distfile for libressl

> On Feb 10, 2017, at 18:04, Kastus Shchuka <kas...@tprfct.net> wrote: > > On Fri, Feb 10, 2017 at 10:13:35AM -0600, Ryan Schmidt wrote: >> >>> On Feb 10, 2017, at 08:05, Rainer Müller <rai...@macports.org> wrote: >>> >>> On 2017-02-10 03

Re: cannot download distfile for libressl

> On Feb 10, 2017, at 08:05, Rainer Müller wrote: > > On 2017-02-10 03:18, Kastus Shchuka wrote: >> I am trying to upgrade libressl (2.4.5), and as binary package is not >> available yet, port command attempts to build from source but fails >> to retrieve distfile. I am

Re: Error in reading /opt/local/bin/tesseract

On Feb 8, 2017, at 22:41, Ali Kozlu wrote: > I have (mistakenly) deleted the tesseract.exe file that came within > opt/local/bin when I downloaded Macport. Now I am trying to download > tesseract from Macport but it gives the error: > Warning: Error parsing file /opt/local/bin/tesseract: Error

Re: missing dependency for py26-setuptools

On Feb 8, 2017, at 22:46, Richard L. Hamilton wrote: > Error: Dependency 'py26-certifi' not found. https://trac.macports.org/ticket/53521

Re: p5*-getopt-euclid have no build for recent perl

> On Jan 18, 2017, at 22:06, S P Arif Sahari Wibowo via macports-users > wrote: > > Hi! > > I found out that the latest p5*-getopt-euclid available is > p5.22-getopt-euclid, while perl was updated to 5.24. I was forced to manually > reactivate 5.22 to

Re: French Error Messages in BBEdit from Bash 4 on Sierra

> On Jan 16, 2017, at 23:48, Christopher Stone > wrote: > > [While writing this up I solved the immediate problem – but failed to > discover the why.] > > > Hey Folks, > > Well, this is weird... > > I only recently updated to Sierra and have been going

Re: Migration Assistant moved MacPorts home directories

> On Mar 1, 2017, at 17:34, Brandon Allbery <allber...@gmail.com> wrote: > > > On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > I'm not talking about an unusual case. I'm talking about the completely > normal case that I expect all

Re: problem with qscintilla

> On Feb 26, 2017, at 16:03, Uli Wienands wrote: > > First, let me observe that MacPorts 2.4 seems to be a really nice release: I > got a whole lot of stuff installed on a "new" OS X 10.8.5 system with no > issues at all. Kudos to all who made this happen. > > I did run

Re: MacPorts 2.4.1 has been released

> On Feb 26, 2017, at 12:26, Al Varnell wrote: > > > On Sun, Feb 26, 2017 at 04:45 AM, Joshua Root wrote: >> >> >> The MacPorts Project is pleased to announce the release of version >> 2.4.1. This is a bugfix release with small changes only. See the >> ChangeLog [1] for

Re: Weird uninstall error

> On Nov 7, 2016, at 7:07 PM, Dave Horsfall wrote: > > (Apologies for possible duplicate) > > Doing my regular "port -u uninstall", I never saw this one before: > >---> Cleaning p5.22-datetime >---> Unable to uninstall p5.22-specio @0.280.0_0, the following ports

Re: Weird uninstall error

> On Nov 10, 2016, at 5:42 AM, Richard Cobbe <rco...@gmail.com> wrote: > > On Tue, Nov 08, 2016 at 09:45:59AM -0600, Ryan Schmidt wrote: >> >>> On Nov 7, 2016, at 7:07 PM, Dave Horsfall <d...@horsfall.org> wrote: >>> >>> (Apologies for

Re: selfupdate fails with '"/tarballs/ports.tar" (in release) failed: No such file or directory'

> On Nov 14, 2016, at 9:25 PM, Richard L. Hamilton <rlha...@smart.net> wrote: > > >> On Nov 14, 2016, at 18:48, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> No. There is a bug in mprsyncup in which updates of our private master rsync >> ser

Re: selfupdate fails with '"/tarballs/ports.tar" (in release) failed: No such file or directory'

> On Nov 15, 2016, at 10:39, Daniel J. Luke <dl...@geeklair.net> wrote: > >> On Nov 14, 2016, at 10:38 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> Because of the slow network connection, if someone commits updates to a >> large port, we have alr

Re: MacPorts 2.3.5 has been released

On Nov 17, 2016, at 16:43, Dave Horsfall wrote: > > Now, not to sound critical or anything, but when are we going to see the > various comments generated for various builds summarised at the end? What do you mean? What builds? What comments? Are you taking about the

Re: p5.22-specio failed to uninstall

> On Nov 20, 2016, at 12:38 PM, Lawrence Velázquez wrote: > >> On Nov 19, 2016, at 7:52 PM, Dave Horsfall wrote: >> >> Doing my weekly "port -u uninstall", I get: >> >> ---> Unable to uninstall p5.22-specio @0.280.0_0, the following ports >> depend

Re: Thanks

On Nov 26, 2016, at 2:15 PM, Marko Käning wrote: > I hope Apple will employ for longer than just the past year to keep > this community effort alive and ticking! My contract position with Apple was for the purpose of maintaining macOS forge and decommissioning it. Now that that has happened

Re: p7zip Fails to Build on Sierra

On Jan 14, 2017, at 00:38, Christopher Stone wrote: > When I try to install p7zip on Sierra the port file runs and appears to > complete, but I don't get a viable executable. > > Can someone confirm this? Could you describe in what way the executable is not viable?

Re: gnutls won't build on Snow Leopard

Yes, if you find ports that need their compiler changed (or rather, need certain compilers blacklisted), please let us know. Overriding the compiler on the command line can be a useful troubleshooting step for identifying the solution to a bug, but should not be required in the general case; we

Re: distfiles mirrors

> On Jan 10, 2017, at 10:13, Gregory Allen wrote: > > I’ve noticed a number of issues with the distfiles repo/mirrors over the past > few months. After the ports migration to git, a number of packages don’t make > it into the distfiles mirrors. That causes issues for

Re: mpv - runtime library check?

> On Dec 3, 2016, at 2:10 AM, Richard L. Hamilton wrote: > > Looks to me like mpv checks at runtime that it is linked with the same > version (regardless of nominal compatibility) of ffmpeg (at least) as when it > was built, and if not, refuses to run: > > ffmpeg library

Re: pan - start with script.app at the new Pan 0.141

On Jan 6, 2017, at 03:16, FritzS - gmx wrote: > > My script pan.app > do shell script "export PATH=\"/opt/local/bin:$PATH\" && pan" > do shell script "/opt/local/bin/pan“ > works now (without set the path in script it does’t run too) > > Pan 0.141 runs now well - but if I closed pan another

Re: GRASS 7.2 fails to install on Mac OS X Sierra 10.12.2

> On Jan 3, 2017, at 17:00, P Kishor wrote: > > I get the following message: :error:patch org.macports.patch for port grass7 > returned: sed: > /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/gis/grass7/files/patch-libraster_gdal_c.diff.tplt: >

Re: PowerMac download statistics?

> On Jan 8, 2017, at 08:47, Rainer Müller wrote: > > On 2017-01-06 23:33, Clemens Lang wrote: >> On Fri, Jan 06, 2017 at 04:48:37PM -0500, Jeffrey Walton wrote: >>> I'm looking for statistics on the number of Macports users and the >>> number of PowerMac users. >>> >>>

Re: Migration issue

> On Jan 5, 2017, at 09:26, Adam Dershowitz wrote: > > I just tried what you suggested for py27-numpy and it just activated without > any error. Yes, there will not be an error at activation time. However, if you have anything installed that required py27-numpy to be universal, it will now

Re: jasper +universal fails

> On Dec 20, 2016, at 08:27, Adam Dershowitz <de...@alum.mit.edu> wrote: > > > > >> On Dec 20, 2016, at 9:23 AM, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> >> On Dec 20, 2016, at 07:31, Adam Dershowitz wrote: >> >>>

Re: Csound fail to build

> On Dec 23, 2016, at 02:57, rmgls wrote: > > Hi all, > > Csound fail to build with ports updated. > > Below is the main.log. This problem has already been reported: https://trac.macports.org/ticket/45560 > Please can you upgrade to a more recent version? I'll look into

Re: (OT?) Tweaking MySQL57

On Dec 21, 2016, at 20:45, Bill Christensen wrote: > I recently updated one of my servers to MySQL57. Most of the sites on the > server are WordPress - everything is up to date. Most of the time it's > working fine, but a too large percentage of the time I'm getting "Error > establishing

Re: all compilers blacklisted or unavailable

On Mar 22, 2017, at 10:27, Jeremy Huddleston Sequoia wrote: >> This is clever, but I don't like that it causes MacPorts to print an >> inaccurate warning that clearly causes user confusion. I think we could fix >> the problem by having the port blacklist the compilers only when libc++ is >>

Re: building from source with libc++

On Mar 24, 2017, at 14:48, db <iams...@gmail.com> wrote: > On 24 Mar 2017, at 19:23, Ryan Schmidt <ryandes...@macports.org> wrote: >> I agree that ticket describes the error you encountered. It was closed >> because nobody could explain it and the problem went awa

Re: gdbm upgrade fails trying to retrieve patch

> On Mar 22, 2017, at 21:13, Richard L. Hamilton wrote: > > lapple:~ root# port list gdbm > gdbm @1.13 databases/gdbm > lapple:~ root# port upgrade gdbm > ---> Computing dependencies for gdbm > ---> Fetching archive for gdbm > --->

Re: libsdl2 built fails when updating ffmpeg

> On Mar 23, 2017, at 09:43, t...@qx.net wrote: > >> >> On Mar 23, 2017, at 09:33, t...@qx.net wrote: >> What version of Xcode and the command line tools do you have installed? If it's not the very latest for 10.7 (Xcode 4.6.3 and Command Line Tools (OS X Lion) for

Re: libsdl2 built fails when updating ffmpeg

On Mar 23, 2017, at 09:33, t...@qx.net wrote: >> What version of Xcode and the command line tools do you have installed? If >> it's not the very latest for 10.7 (Xcode 4.6.3 and Command Line Tools (OS >> X Lion) for Xcode - April 2013) try updating to that. > > Thank you. I am downloading

Re: gmp configure failure (was: Re: macports-users Digest, Vol 127, Issue 19)

On Mar 22, 2017, at 12:30, Franck Olivier Ngassam Nyakam wrote: > Please i would like you to help me finish my xcrysden installation via > macport. Indeed I followed the whole procedure and I have this > message:Configuring gmp > Error: Failed to configure gmp, consult >

Re: Click-and-hold instead of right-click?

> On Mar 15, 2017, at 12:08, Michael wrote: > > >> On 2017-03-15, at 9:26 AM, René J.V. Bertin wrote: >> >> Hi, >> >> Not specifically a MacPorts question: didn't Mac OS X at some point allow >> opening context menus with a click-and-hold gesture

Re: HELP INSTALLATION

On Mar 19, 2017, at 14:36, Franck Olivier Ngassam Nyakam wrote: > HELLO SIR > THANK YOU FOR YOUR RESPONSE THIS HAS HELPED ME. BUT WHEN I ENTER THE COMMAND > sudo port install xcrysden +x11 I HAVE THIS MESSAGE Error: Failed to > configure gmp, consult >

Re: Prevent MacPorts editing .bash_profile over and over again...

On Mar 21, 2017, at 18:21, Brandon Allbery wrote: > On Tue, Mar 21, 2017 at 7:18 PM, Brandon Allbery wrote: >> vim $(port logfile thePort) > > ...and the port you installed will usually get expanded with . > (bash/zsh, in default emacs mode) so you don't even need to type that :) I'm not aware

Re: Prevent MacPorts editing .bash_profile over and over again...

> On Mar 21, 2017, at 16:23, Dave Horsfall wrote: > > On Tue, 21 Mar 2017, Brandon Allbery wrote: > >> Never assume people will read instructions. How often do we get people >> who cut and paste the boilerplate at the end of a failed build that >> tells them to check the

Re: port diagnose fails on 10.6.8

> On Mar 21, 2017, at 02:56, Jan Stary wrote: > > This is MacPorts 2.4.1 on a mac mini running 10.6.8. > 'port diagnose fails like this: > > Error: process_cmd failed: > Usage: xcode-select -print-path > or: xcode-select -switch > or: xcode-select -version > Arguments:

Re: ffmpeg update fails

> On Mar 20, 2017, at 21:12, t...@qx.net wrote: > > Mac mini 2.7Ghz Intel Core i7 > 8 GB 1333 Mhz DDR3 > Lion OS X 10.7.5 > ffmpeg @3.1.4_0+gpl2+x11 (active) > > Attempting this update broke my ffmpeg. Port update was successful. > Please help. > > Thank you, > Tom This is the libarchive

Re: all compilers blacklisted or unavailable

Jeremy, I'm Cc'ing you for input on wavpack; see the last few paragraphs. On Mar 21, 2017, at 03:37, Jan Stary wrote: > This is MacPorts 2.4.1 on MacOSX 10.6.8. > A build of audio/sox starts with the following warning: > > $ sudo port install -d sox Note that this "-d" does nothing.

Re: Difficulty in upgrading MacPorts from El Capitan to Sierra

On Apr 4, 2017, at 02:44, Barrie Stott wrote: > A couple of weeks ago I had a bit of spare time so I looked at the inability > of my iMac to put itself to sleep: something that has caused mild irritation > from time to time. Cutting a long story short it eventually involved someone > from

Re: speex vs speex-devel

On Mar 31, 2017, at 16:21, Jan Stary wrote: > On Mar 31 14:05:03, h...@stare.cz wrote: >> The speex port has no maintainer so I am asking here. >> Why do we have both 'speex' and 'speex-devel'? >> They consist of exactly the same files. >> Similarly for speexDSP and speexDSP-devel. >> Xiph.org

Re: wine-devel error

On Apr 2, 2017, at 13:03, Curtis Matz wrote: > > I’ve installed wine-devel and am getting an error running winecfg. I’m on > MacOS Sierra 10.12.4 on a mid 2010 mbp 15”. > > err:module:DelayLoadFailureHook failed to delay load > shell32.dll.SHGetFolderPathW > wine: Call

Re: notes repeatedly showing in port session

> On Apr 11, 2017, at 13:18, db wrote: > > After installing a port with notes, these show after every command during the > same shell mode session on port 2.4.1. Is there any way to disable this great > feature? That sounds like a bug. We probably didn't test the change

Re: libgphoto2 build failed on Snow Leopard

> On Apr 11, 2017, at 17:56, Richard L. Hamilton wrote: > > I can do that; but will that need any more info than below? I doubt that I > kept the log, once I got it built. That's fine. We have a log here:

Re: notes repeatedly showing in port session

> On Apr 12, 2017, at 09:01, db <iams...@gmail.com> wrote: > > On 12 Apr 2017, at 11:02, db <iams...@gmail.com> wrote: >> On 12 Apr 2017, at 01:19, Ryan Schmidt <ryandes...@macports.org> wrote: >>> That sounds like a bug. We probably didn't test the c

Re: MP_EDITOR doesn't work

> On Apr 5, 2017, at 16:27, Lenore Horner wrote: > > >> On Apr 5, 2017, at 16:12, Rainer Müller wrote: >> >> On 2017-04-05 21:54, db wrote: >>> On 4 Apr 2017, at 11:21, db wrote: On 4 Apr 2017, at 11:18, Rainer Müller

Re: Pallet requires Tcl directory

On Apr 10, 2017, at 09:36, db wrote: > >> On 10 Apr 2017, at 14:32, Ryan Schmidt <ryandes...@macports.org> wrote: >> I haven't tried to build Pallet from the latest git source lately. Have you? > > Yes, I tried on OS X 10.8.5, Xcode 5.1.1. I cloned the repo and onl

Re: Pallet requires Tcl directory

> On Apr 11, 2017, at 02:16, db <iams...@gmail.com> wrote: > > On 11 Apr 2017, at 04:13, Ryan Schmidt <ryandes...@macports.org> wrote: >> Ok. I don't see anything in the crash report that says to me that 10.8 is >> unsupported. I just see a crash, which som

Re: qt5-qtenginio is obsolete

> On Apr 20, 2017, at 16:15, Clemens Lang wrote: > > Hi, > > On Tue, Apr 18, 2017 at 04:23:55PM +, Fielding, Eric J (329A) wrote: >> I just did a similar “port selfupdate” and “port upgrade outdated” on >> my other Mac, and I got the same error message when I tried to >>

Re: Permission denied writing temp file during restore_ports.tcl on macOS sierra

> On Apr 20, 2017, at 11:30, Kendall Shaw wrote: > > Building gmp fails because it can’t write to a directory that it creates in > /var/folders/xx/_blah/T: > > :info:build make: error: couldn't create cache file >

Re: unbound fails to rebuild

On Apr 21, 2017, at 01:34, Kastus Shchuka wrote: > > >> On Apr 20, 2017, at 11:13 PM, Kastus Shchuka wrote: >> >> >>> On Apr 20, 2017, at 11:01 PM, Kastus Shchuka wrote: >>> >>> I have a strange problem rebuilding unbound after

Re: port-depgraph warning

> On Apr 13, 2017, at 16:38, db wrote: > > On 13 Apr 2017, at 17:38, Rainer Müller wrote: >> You are effectively running it with an empty argument, which is not a valid >> port name: >> $ port-depgraph "" >> That could indeed be handled more graceful.

Re: Cannot upgrade libpurple

On Apr 14, 2017, at 04:06, S P Arif Sahari Wibowo wrote: > I found while trying to install another package, I cannot upgrade libpurple, > apparently because, "Tk 8.6 must be compiled with tcl.h from Tcl 8.6 or > better." Log file attached. Some info: > > bash-3.2# uname -v > Darwin Kernel

Re: qt5-qtenginio is obsolete

hat either. > I also did a “port reclaim” to remove all the outdated ports that might > depend on the old qt5. > > -Original Message- > From: "Eric J. Fielding" <eric.j.field...@jpl.nasa.gov> > Date: Tuesday, April 18, 2017 at 7:28 AM > To: Ryan

Re: binutils warning

> On Apr 22, 2017, at 10:02, db wrote: > > On 22 Apr 2017, at 16:16, Rainer Müller wrote: >> As identified by going back in history with 'git blame': >> https://trac.macports.org/changeset/67114 > > Is that still the case? binutils' binaries are

Re: qt5 build dependency on clang

> On Apr 22, 2017, at 15:55, db <iams...@gmail.com> wrote: > > On 22 Apr 2017, at 21:58, Ryan Schmidt <ryandes...@macports.org> wrote: >> Sounds plausible. What's your question / problem with this? > > Ken already point me to cxx11-1.1.tcl, but I still don't

Re: qt5-qtenginio is obsolete

On Apr 22, 2017, at 20:02, Fielding, Eric J (329A) wrote: > > In fact, I still have a remaining broken port message that I don’t know how > to solve: > ---> Scanning binaries for linking errors > ---> Found 1 broken file, matching files to ports > ---> Found 1 broken port: > py27-pyqt5

Re: Upgrade to Sierra from Mavericks

> On Mar 12, 2017, at 13:05, Mannucci, Anthony J (335G) wrote: > > I want to report an apparently smooth upgrade of macports when I upgraded my > OS to Sierra from Mavericks. Glad to hear it! > I tried to follow the instructions exactly, and found some minor issues: > 1) The lack of a

Re: port selfupdate fails

May we see your /opt/local/etc/macports/macports.conf file?

Re: verbose output in shell mode

> On Mar 6, 2017, at 03:46, db wrote: > > Is there any way to enable verbose output _after_ entering shell mode with > `port`? I'd rather not use `port -v`, then I get it unnecessarily for all > commands. Not that I know of.

Re: verbose output in shell mode

On Mar 6, 2017, at 07:44, db wrote: > Do you know of any means that I'm not aware of to make livecheck output its > result without -v? There doesn't seem to be any difference in livecheck output when using the verbose flag: $ port livecheck gcc7 gcc7 seems to have been updated (port

Re: gcc 4.8 problem in update

> On Mar 5, 2017, at 11:59, Comer Duncan wrote: > > I have had a failure to complete an update using a script that I have used > for quite a while. I attach the script and the end part of the main.log. Can > someone please take a look and offer some likely cause(s)? >

Re: verbose output in shell mode

On Mar 6, 2017, at 08:03, db wrote: > > I meant try with other ports, e.g., emacs > > $ port livecheck emacs > $ > $ port -v livecheck emacs > emacs seems to be up to date > > Not all ports give the same output with livecheck without -v. Ah, I see. Yes, when non-verbose

Re: verbose output in shell mode

On Mar 6, 2017, at 07:53, db wrote: > Try with emacs. Sorry, I've never used emacs.

Re: fail to destroot port with only makefile

On Mar 7, 2017, at 10:15, db wrote: > I'm trying to port a client that comes with only a makefile, but fail to > destroot it, although it sort of does if I sudo manually. I attach the log. > > https://github.com/tldr-pages/tldr-cpp-client/blob/master/Makefile > > The Makefile does not

Re: Migration Assistant moved MacPorts home directories

> On Mar 2, 2017, at 08:02, Rainer Müller <rai...@macports.org> wrote: > > On 2017-03-02 00:34, Brandon Allbery wrote: >> >> On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt <ryandes...@macports.org >> <mailto:ryandes...@macports.org>> wrote: >>

Re: fail to destroot port with only makefile

On Mar 7, 2017, at 13:27, db wrote: > On 7 Mar 2017, at 20:00, Ryan Schmidt wrote: >> That can be an acceptable workaround. Sometimes it has side effects. I don't >> know if it does with this port. > > Can you give an example? Suppose the program builds a dynamic libra

Re: fail to destroot port with only makefile

On Mar 7, 2017, at 12:37, db wrote: > On 7 Mar 2017, at 17:29, Ryan Schmidt wrote: >> The Makefile does not support DESTDIR. Ideally, fix the Makefile to support >> DESTDIR and submit that to the developers. > > MacPorts Guide links to > http://www.gnu.org/

Re: building from source with libc++

On Apr 1, 2017, at 09:35, db wrote: > Could someone from MP team shed some light on this, please? All of MacPorts is on a best-effort basis. There is no guarantee of anything. Most of us are volunteers working on MacPorts in our spare time on whatever limited set of hardware we happen to have

Re: No default port source

If you want aarnet to be your default ports source, use this line: rsync://aarnet.au.rsync.macports.org/pub/macports/ports/ [default] > On Apr 18, 2017, at 17:15, Ken Cunningham > wrote: > > you appear to have commented out the default ports source. > >

Re: port leaf becoming requested

On Apr 18, 2017, at 02:52, db wrote: > I wanted to install texinfo which is actually a leaf of coreutils, but `sudo > port install texinfo` doesn't make it a requested port, as I would expect. Is > it intended behaviour? I suppose, I could either uninstall leaves and > reinstall it, or use

Re: astropy 2.0.1?

On Aug 15, 2017, at 10:49, Michael Corcoran wrote: > Any info on when astropy (py27-astropy and py36-astropy) will be updated to > the current version (2.0.1) from 1.3.3? 2.0.1 was released July 30 The usual way to ask for a port to be updated is to file a ticket in the issue tracker.

Re: Anyone successfully install "meld"? Failed on gstreamer1-gst-plugins-bad

On Aug 12, 2017, at 08:20, James Kulp wrote: > :info:build /usr/include/signal.h:79: syntax error, unexpected identifier, > expecting ')' in 'void (* _Nullable bsd_signal(int, void (* > _Nullable)(int)))(int);' at 'bsd_signal' An error in a file in /usr/include makes me suspicious that you may

Re: Is anyone successfully using lout on Sierra?

On Aug 11, 2017, at 17:50, Ken Cunningham wrote: > Abort trap 6 has lots of references on google, e.g. > "Abort trap" means "it crashed". If you want to know more than that, you have to look at the crash log file.

Re: Is anyone successfully using lout on Sierra?

On Aug 11, 2017, at 01:21, Barrie Stott wrote: > I don’t remember having a problem with the lout port until I moved to Sierra. > Now all my ports are fine except lout. Could you be more specific about what doesn't work?

Re: expat 2.2.2 build fail on Snow Leopard

On Jul 15, 2017, at 22:36, Richard L. Hamilton wrote: > :info:build libtool: compile: /opt/local/bin/clang-mp-3.9 -I./lib -I. -pipe > -Os -arch x86_64 -arch i386 -Wall -Wmissing-prototypes -Wstrict-prototypes > -fexceptions -fno-strict-aliasing -I/opt/local/include -DHAVE_EXPAT_CONFIG_H > -c

Re: nmap doesn't like libc++ ?

On Jul 12, 2017, at 11:10, Richard L. Hamilton wrote: > After switching my Snow Leopard over to the toolchain that supports C++11 and > favors libc++ instead of libstdc++, I could no longer build nmap; it kept > getting undefined symbols like std::logic_error::logic_error (which as used, >

Re: problem with pkg_resources in python 3

On Jul 12, 2017, at 09:30, pagani laurent via macports-users wrote: > It is (to me) very strange! > > Lorenzo>sudo port upgrade python35 > ---> Scanning binaries for linking errors > ---> No broken files found. > Lorenzo>sudo port installed python35 > The

Re: svn server problem?

On Jul 14, 2017, at 19:24, Richard L. Hamilton wrote: > > svn co > https://svn.macports.org/repository/macports/contrib/MacPorts_Framework@86927 > svn: E170013: Unable to connect to a repository at URL > 'https://svn.macports.org/repository/macports/contrib/MacPorts_Framework' > svn: E120108:

Re: nmap doesn't like libc++ ?

On Jul 12, 2017, at 14:27, Ken Cunningham wrote: > You could do this in the portfile: > > configure.cxxflags-append -stdlib=libc++ > configure.ldflags-append -stdlib=libc++ > > and your build should proceed through. Should. Usually works. As I mentioned, some of the Makefile lines in question

Re: attach a diff or request a pull?

On Jul 1, 2017, at 09:01, Jan Stary wrote: > There seem to be two way to send a patch to a port: > > 1. create a ticket in trac and attach a diff > 2. create a pull request on github > > Is any of the two preferred by the MP developers? I would say to whatever you're most comfortable with.

Re: 'log2' is not a member of 'std'

On Jul 2, 2017, at 12:28, Joshua Root wrote: >> This is MacOSX 10.6.8 running various compilers provided by MacPorts. >> Compiling the following C++ source >> #include >> int main(void) >> { >> double d = std::log2(2.3456789f); >> return 0; >> } >>

  1   2   3   4   5   6   7   8   9   10   >