Re: sourceforge.net - gsmartcontrol 1.1.1 now available

On Sep 26, 2017, at 03:04, FritzS wrote: > please make an update from gsmartcontrol 1.0.2 to gsmartcontrol 1.1.1 > > gsmartcontrol 1.0.2 > https://www.macports.org/ports.php?by=name&substr=gsmartcontrol > > gsmartcontrol 1.1.1 > https://sourceforge.net/projects/gsmartcontrol/ > https://source

macOS 10.13 High Sierra

macOS 10.13 High Sierra has been released. As usual with any major OS update, we recommend MacPorts users wait a few weeks before updating. This will give us time to produce an installer package for MacPorts for this new OS version, to get our automated build system producing binaries for the ne

Re: port mpkg deliverables for older systems?

On Sep 22, 2017, at 17:32, Ken Cunningham wrote: > You might get this to work by setting the macosx_deployment_target in > macports.conf to the minimum system you want to support. In addition, set "buildfromsource never" so that you don't get any binaries from our server which were built with

Re: xcode, clt or both

On Sep 20, 2017, at 01:31, db wrote: > On 19 Sep 2017, at 23:06, Ryan Schmidt wrote: >> On Sep 19, 2017, at 11:40, db wrote: >>> On 19 Sep 2017, at 01:01, Ryan Schmidt wrote: >>>> For certain subsets of ports, you can get by with installing just one or >>&

Re: xcode, clt or both

On Sep 19, 2017, at 12:21, Arno Hautala wrote: > I think Xcode is only required by a few ports. Certainly a minority. > It might be nice if Xcode showed up as a dependency or could be > searched on. That's not currently possible because the data on which that would be based has not been collect

Re: xcode, clt or both

On Sep 19, 2017, at 11:40, db wrote: > On 19 Sep 2017, at 01:01, Ryan Schmidt wrote: >> For certain subsets of ports, you can get by with installing just one or the >> other. > > How can I know this beforehand? That's the reason I'm actually asking what > e

Re: xcode, clt or both

On Sep 18, 2017, at 22:08, Richard L. Hamilton wrote: > By "We are trying to move toward a future where MacPorts recommends > installing only Xcode, and not the command line tools", does that mean that > only Xcode will be required then, or that the command line tools should > actually be avoi

Re: xcode, clt or both

On Sep 18, 2017, at 15:19, db wrote: > I checked the guide and searched both lists with google but don't seem to > find an answer. What exactly do Xcode and the Command Line Tools provide? Are > both necessary at all times or could building some ports do without either of > them? In modern ti

Re: mercurial fails to build when

On Sep 13, 2017, at 13:14, Sean Farley wrote: > Ryan Schmidt writes: > >> On Sep 12, 2017, at 19:36, Glenn Ramsey wrote: >>> >>> On OSX 10.12.6 with the latest Xcode I have set macosx_deployment_target to >>> 10.8 >>> in macports.con

Re: using pip3 to call pip

On Sep 11, 2017, at 05:06, David Epstein wrote: > How do I arrange for my shell command > pip3 > to give the pip associated with my /opt/local/bin/python3? > > I tried to do this using "port select", but that failed, as you can see > below. Can someone give some explanation of the meaning of th

Re: mercurial fails to build when

On Sep 12, 2017, at 19:36, Glenn Ramsey wrote: > > On OSX 10.12.6 with the latest Xcode I have set macosx_deployment_target to > 10.8 > in macports.conf and when installing mercurial I get this error: > > error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.8" but "10.12" during > configure > >

Re: On Snow Leopard, updating at-spi2-atk to @2.26.0_0+universal failed unless at-spi2-core updated first

On Sep 12, 2017, at 13:58, Richard L. Hamilton wrote: > Hardware Version: Mac mini (Mid 2007) > Model Identifier: Macmini2,1 > Mac OS X 10.6.8 10K549 (Snow Leopard) > Xcode 3.2.6 DevToolsSupport-1806.0 > MacPorts Version: 2.4.1 > > The error in the log file seems to say as much: > > :info:confi

Re: crash with python3.6.2 and readline

We should keep the discussion on the mailing list. (Use Reply All when you reply.) On Sep 6, 2017, at 06:35, David Epstein wrote: > On 06/09/2017 08:58, Ryan Schmidt wrote: >> On Sep 5, 2017, at 18:29, David Epstein wrote: >> >> >>> What is the procedure f

Re: crash with python3.6.2 and readline

On Sep 6, 2017, at 02:41, David Epstein wrote: > I don't suppose that the output from a port install command is saved > automatically somewhere? It seems like it would often be useful to have this > output saved. Nope, not saved anywhere. > Last night I posted (with the same subject line as t

Re: crash with python3.6.2 and readline

On Sep 5, 2017, at 18:29, David Epstein wrote: > What is the procedure for adding to bug report #54728. Log in to our Trac with your GitHub account. This will reveal the new comment field at the bottom of the ticket which you can type into and then submit. > Here is a summary of what happened

Re: Searching macports-users Archives

On Sep 4, 2017, at 08:43, David Epstein wrote: > Is there a way of searching Macports-users archive? > They seem dauntingly large and unapproachable. Google. In addition to what you want to search for, include the search term site:https://lists.macports.org/pipermail/macports-users/

Re: Mariadb-10.1 download gives error 404

st mariadb-10.0 > > Regards, > Horst > >> On 2 Sep 2017, at 9:04 am, Ryan Schmidt wrote: >> >> >>> On Aug 31, 2017, at 23:57, Horst Simon wrote: >>> >>> When I tried to install mariadb-10.1 I get following error, is it removed? >>&

Re: running macports along with homebrew

> On Sep 1, 2017, at 03:22, db wrote: > > On 31 Aug 2017, at 21:34, Craig Treleaven wrote: >> Gentle reminders, regularily applied, tend to cure the ‘missing ports and >> updated versions’ issue. > > It shouldn't work like that. Actually, it didn't. Ok. How would you like us to proceed?

Re: Mariadb-10.1 download gives error 404

On Aug 31, 2017, at 23:57, Horst Simon wrote: > When I tried to install mariadb-10.1 I get following error, is it removed? It > work previously. Upstream developers must have moved or removed the file on their server. I've added it to our mirror server. It should be available to you within a c

Re: running macports along with homebrew

On Aug 31, 2017, at 10:53, Ken Cunningham wrote: > I think homebrew gets attention for two reasons. > > > 1. a one-line copy & paste install command that is pasted into the terminal > (macports could / should do that too, BTW). While I agree our web site, including installation instructions,

Re: running macports along with homebrew

On Aug 29, 2017, at 07:08, db wrote: > best practice for running macports along with homebrew The best practice is not to do that. We don't support it. It can cause you problems that we don't want to spend time investigating, because they wouldn't be problems if you hadn't also used a second p

Re: Tried to install gcc7, couldn't because libgcc conflict

On Aug 23, 2017, at 07:52, David wrote: > > 704_ sudo port install gcc7 > ---> Computing dependencies for gcc7 > Error: Can't install libgcc-devel because conflicting ports are active: libgcc > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > Error: Processing of port

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. https:/

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: 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: macports' hardlinks and time machine backups

On Aug 14, 2017, at 19:04, Peter West wrote: > When I see MiB, I think million bytes. Is this wrong? Yes, that is wrong, or at least is not what other people mean. 1 MB = one megabyte = 10^6 bytes = 1,000,000 bytes 1 MiB = one mebibyte (what we used to call one megabyte) = 2^20 bytes = 1,048,5

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: New version of emacs-mac-app

On Aug 7, 2017, at 15:05, M A wrote: > An updated version of emacs-mac-app is available at its home (6.5 while 6.4 > is what's on macports). Could this be updated in macports? Thanks. Usually you should request updates by filing a ticket in our issue tracker.

Re: port upgrade outdated reports weird problems with deadline and poplar

> On Aug 4, 2017, at 20:36, Richard L. Hamilton wrote: > > Some notes of mine on /usr/local: I can't avoid /usr/local entirely, since > VirtualBox and Parallels install their command line tools there. Those probably won't cause problems for MacPorts. > But I can move /usr/local out of the wa

Re: port upgrade outdated reports weird problems with deadline and poplar

On Aug 4, 2017, at 17:25, Jerry wrote: > I just ran port selfupdate after several months and experienced the following > oddities. > > > * readline was reported as disabled: > > $ sudo port selfupdate > Password: > ---> Updating MacPorts base sources using rsync > MacPorts base version 2.4.0

Re: clang vs gcc: installing python-qpid-proton

It's news to me that MacPorts gcc has /opt/local/include in its default search path, and my first response is that I would not want it to do that, especially if as you say MacPorts clang doesn't do the same thing. So I would consider this a bug in MacPorts gcc that I would want to fix. Does anyo

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: 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: Er

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: 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, > ma

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 following

Re: Using qemu-system-ppc from MacPorts to run MacOS 9.2.1 in 10 minutes or less - QuickStart.

On Jul 9, 2017, at 11:37, Ken Cunningham wrote: > [Apologies if this is off-topic for the users’ list, but I hoped this might > be of interest to both users of MacPorts and the interests of the members of > this list, so I thought I would share it.] > > It is reported qemu-system-ppc can run M

Re: Failure to build libsndfile

On Jul 3, 2017, at 01:07, Dave Horsfall wrote: > On Sun, 2 Jul 2017, Ryan Schmidt wrote: > >>> Is there some reason why my local mirror is out of date? >> >> The mirror isn't out of date. MacPorts should never have attempted to >> fetch the patch fro

Re: Failure to build libsndfile

On Jul 2, 2017, at 20:30, Dave Horsfall wrote: > Doing my weekly "port upgrade outdated", it fell over when building "flac" > (whatever that is): Note that it failed at libsndfile, not flac. >---> Attempting to fetch patch-Wvla.diff from > http://her.gr.distfiles.macports.org/libsndfile

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; >> } >> r

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. I

Re: logging all port command activity

On Jun 28, 2017, at 13:14, db wrote: > Is it possible to have all activity logged to a file? There's no such capability built in.

Re: port install pear-TCPDF fails with checksum error

On Jun 27, 2017, at 00:42, Joshua Root wrote: >> port install pear-TCPDF fails with checksum error >> i have read https://trac.macports.org/wiki/MisbehavingServers and i am sure >> my isp's dns server is not misbehaving. >> i have read https://trac.macports.org/wiki/FAQ#checksums. >> i have sear

Re: replace existing attachment of the same name in trac

On Jun 26, 2017, at 12:34, db wrote: > > Has anyone noticed that replacing an attached file keeps the previous > optional description? Is that expected or a bug? > > E.g. trac.macports.org/ticket/54014#no1. I hadn't noticed. If it does that, it would probably be a Trac bug.

Re: Mac port error

On Jun 22, 2017, at 11:13, Simone Poli wrote: > dear mac port users, I’ve just installed mac port, but no commando can be > executed on it, not even the sudo self update, no action is recognised: > > MacBook-Pro-di-nicola-travaglia:/ SimonePoli$ port > MacPorts 2.4.1 > Entering shell mode... ("

Re: Missing /opt/local/share/man/whatis DB

On Jun 20, 2017, at 18:53, Stephen Baber wrote: > Hi MacPorts architects/maintainers, > > Author of JPortsUI here. I have built features into the next version > of my application that use the "whatis" DB to describe the executable > files installed after MacPorts completes a "port install foo".

Re: How to get date when port was added? To list ports added in last 1/2/3/.../X weeks?

On Jun 20, 2017, at 14:13, Ken Cunningham wrote: > The Portfiles used to have the date they were added in the top line, which > was handy to see if the port was ancient. This line was removed once macports > moved to git, which was in a way too bad. No, it was the date the last change was comm

Re: patching error building glib2 on Snow Leopard

> On Jun 18, 2017, at 15:48, Richard L. Hamilton wrote: > > Please file bug reports in the issue tracker.

Re: How to get date when port was added? To list ports added in last 1/2/3/.../X weeks?

On Jun 13, 2017, at 02:30, Kurt Pfeifle wrote: > From time to time I would like to get a list of newly added ports so I can > see if I'm interested to install any one of them. > > * How can I get the info about the dates when a port was added for the first > time to MacPorts? > * How can I lis

Re: Installing WINE

> On Jun 11, 2017, at 11:10, Mojca Miklavec wrote: > > On 11 June 2017 at 10:32, Ryan Schmidt wrote: >> >>> On Jun 10, 2017, at 23:29, Dave Horsfall wrote: >>> >>> I just did "port install wine", and it seeme to be (re)installing ha

Re: Installing WINE

> On Jun 10, 2017, at 23:29, Dave Horsfall wrote: > > I just did "port install wine", and it seeme to be (re)installing half the > known universe... Is this to be expected? Installinh it on Debian was > quite simple - just an "apt-get" or two. MacPorts Wine is 32-bit. Usually, your other por

Re: Could not initialize

On Jun 2, 2017, at 16:29, Sundareswara, Rashmi N wrote: > I’m trying to install macports on MAC OS Yosemite. I followed the > instructions for the install but here is the error message I get when I type > “port help” TIA! > > > Last login: Fri Jun 2 14:11:06 on ttys000 > HRLE04332:~ rnsu

Re: various errors building poppler on Snow Leopard

> On Jun 1, 2017, at 05:59, Richard L. Hamilton wrote: > > >> On Jun 1, 2017, at 01:33, Ryan Schmidt wrote: >> >> >>> On May 31, 2017, at 18:24, Richard L. Hamilton wrote: >>> >>> The default compiler didn't like the option -s

Re: various errors building poppler on Snow Leopard

> On May 31, 2017, at 18:24, Richard L. Hamilton wrote: > > The default compiler didn't like the option -std=c++11. When I ran with > configure.compiler=macports-clang-3.8 (which was perhaps the newest of what I > had installed), it coped with that, but later got errors as shown in the > att

Re: libxml2 2.9.4 config error #54070 wontfix

> On May 30, 2017, at 11:23, Mojca Miklavec wrote: > > On 30 May 2017 at 17:08, Ryan Schmidt wrote: >> On May 30, 2017, at 09:52, db wrote: >> >>> On 30 May 2017, at 14:58, Ryan Schmidt wrote: >>> >>>> What specific fix to you recommend?

Re: libxml2 2.9.4 config error #54070 wontfix

On May 30, 2017, at 09:52, db wrote: > On 30 May 2017, at 14:58, Ryan Schmidt wrote: > >> What specific fix to you recommend? > > I have no fix to recommend. My uneducated guess is that it's searching for > /opt/local/lib/libreadline.6.dylib while I've just up

Re: libxml2 2.9.4 config error #54070 wontfix

On May 30, 2017, at 06:53, db wrote: > > I got basically the same error referenced in that ticket. > > :info:configure config.status: creating libxml2.spec > :info:configure dyld: Library not loaded: /opt/local/lib/libreadline.6.dylib > :info:configure Referenced from: /opt/local/bin/gawk > :in

Re: Fork in MacPorts Users list?

> On May 28, 2017, at 14:11, Fielding, Eric J (329A) > wrote: > > Hello, > > Since yesterday, I noticed that I am now getting MacPorts “macports-users > Digest” email from two different lists, one at “macosforge.org” (Vol 125, > Issue 10 today) and one at “macports.org” (Vol 129, Issue 19 t

Re: Error installing bash on Sierra

Barrie, The error in your log says: > :error:install Failed to install bash: no destroot found at: > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_shells_bash/bash/work/destroot The solution is here: https://trac.macports.org/w

Re: tea checksum error

On May 26, 2017, at 19:12, Ryan Schmidt wrote: > I guess the developer re-released ("stealth-updated") 44.0.0 with the > necessary build fixes after I originally grabbed it and put it on the mirror > server. Fixed in https://github.com/macports/ma

Re: tea checksum error

> On May 26, 2017, at 02:14, Richard L. Hamilton wrote: > > ...when fetching it as > ---> Attempting to fetch tea-44.0.0.tar.bz2 from > http://semiletov.org/tea/dloads/ > (which one of my systems did consistently) > > but fine when fetching it as > ---> Attempting to fetch tea-44.0.0.tar.bz2

Re: libzzip fails to build on Snow Leopard

I don't see any open bug reports in our issue tracker for libzzip, so you should file one.

Re: icu build failed on Snow Leopard

Yes, it's been reported: https://trac.macports.org/ticket/54209 > On May 23, 2017, at 02:16, Richard L. Hamilton wrote: > >

Re: how to uninstall macport with OS conflict ?

> On May 19, 2017, at 04:13, db wrote: > >> On 19 May 2017, at 00:00, Clemens Lang wrote: >> Run the MacPorts installer for your new OS (yes, I know it's >> counter-intuitive), then follow the uninstall instructions. It should only >> take a couple of minutes if you use the installer and all

Re: [MacPorts] #54149: gcc6 fails to compile because "configure: error: cannot compute sizeof (long long)"

> On May 18, 2017, at 18:55, René J.V. Bertin wrote: > > On Thursday May 11 2017 07:38:01 Ryan Schmidt wrote: > >> It's a matter of doing the equivalent of this, with updated versions: >> >> https://github.com/macports/macports-ports/commit/c4ddd1af302d5b

Re: Trac does not see /opt for attaching files

On May 15, 2017, at 20:18, Al Varnell wrote: > /opt has been installed as a hidden directory by every macOS/OS X installer > from day 1. I guess /opt is a standard UNIX directory, and macOS does install other UNIX directories like /private and /usr as hidden, so it makes sense. Nevertheless,

Re: Trac does not see /opt for attaching files

> On May 15, 2017, at 14:53, Lenore Horner wrote: > > >> On May 15, 2017, at 13:56, Ryan Schmidt wrote: >> >> >>> On May 15, 2017, at 12:03, Dave Horsfall wrote: >>> >>> On Tue, 16 May 2017, Joshua Root wrote: >>> >>>

Re: Trac does not see /opt for attaching files

> On May 15, 2017, at 12:03, Dave Horsfall wrote: > > On Tue, 16 May 2017, Joshua Root wrote: > >> You can hit cmd-shift-. to show hidden files and folders in open/save >> dialogs. > > The question is of course why is /opt hidden in the first place? This > smacks of the M$ "you don't need t

Re: Trac does not see /opt for attaching files

Works as intended. The Finder and the file choosing dialogs do not show hidden directories, and we do indeed mark /opt as hidden. In the Finder, you can press Command-Shift-G, then type /opt to get there. You can do that in file choosing dialogs too, or just start typing /opt. If we don't ment

Re: [MacPorts] #54149: gcc6 fails to compile because "configure: error: cannot compute sizeof (long long)"

>> I have been updating gcc7 snapshots weekly and stopped recently when I >> realized they were preparing for the first release. I did not know they had >> now done so. I will update the ports once a snapshot of gcc8 is available >> (probably already is), since gcc6, gcc7 and gcc8 will need to b

Re: [MacPorts] #54149: gcc6 fails to compile because "configure: error: cannot compute sizeof (long long)"

I have not seen that problem building gcc6 before. I have been updating gcc7 snapshots weekly and stopped recently when I realized they were preparing for the first release. I did not know they had now done so. I will update the ports once a snapshot of gcc8 is available (probably already is),

Re: autogen install or upgrade fails

at 07:40, Ryan Schmidt wrote: > > Ah yes, I didn't notice that there had been a guile update to 2.2 yesterday. > I guess you should file a bug report against the autogen port. > >> On May 4, 2017, at 07:38, Richard L. Hamilton wrote: >> >> lapple:~ root# port inst

Re: autogen install or upgrade fails

cal/bin/guile > > So it looks like there was a guile update to 2.2.2_0 (based on the date of > the file), which autogen wasn't ready for. > > The config log shows it trying to fall back to guile18 when 2.0 isn't found, > but isn't getting that right either. > &g

Re: autogen install or upgrade fails

> On May 3, 2017, at 19:15, Richard L. Hamilton wrote: > > autogen fails rev-upgrade after installing from binaries (!) (update: for > some reason, later today it no longer attempts to install from binaries). It > then fails the build: > > :info:configure awk: can't open file > /opt/local/

Re: cppunit requires C++11 capable compiler now

Yes it looks like cppunit now requires C++11, which means everything that requires cppunit now requires C++11 too. Which means problems for users of macOS versions earlier than El Capitan. https://trac.macports.org/ticket/54078 > On May 1, 2017, at 11:41, Richard L. Hamilton wrote: > > That

Re: Do I need +universal to be used when installing ports?

> On Apr 29, 2017, at 10:13, Richard L. Hamilton wrote: > > In favor of getting rid of it, the pre-built binaries (much faster to install > or upgrade) aren't built +universal; so if you get rid of it, you'll often > get them. Some things aren't pre-built, so you won't always get them, but >

Re: gss build fails on Snow Leopard

On Apr 29, 2017, at 10:29, Richard L. Hamilton wrote: > > ...because getline() is not provided by the OS (or compiler? since I don't > see the symbol in libSystem.B.dylib even on Sierra). Logfile attached. Correct, getline was not in macOS until 10.7. Please report the problem to the develope

Re: Is There a Port for a compiler compatible with OpenMP and Imagemagick

> On Apr 25, 2017, at 22:11, Fred Weinhaus wrote: > > >> On Apr 25, 2017, at 5:21 PM, Ryan Schmidt wrote: >> >> >>> On Apr 25, 2017, at 18:38, Fred Weinhaus wrote: >>> >>> I am trying to install Imagemagick from source using all my de

Re: Is There a Port for a compiler compatible with OpenMP and Imagemagick

> On Apr 25, 2017, at 19:48, Ken Cunningham > wrote: > > sudo port -v install imagemagick configure.cppflags-append="-fopenmp" > configure.compiler=macports-clang-3.9 You can't augment a port's variables from the command line, only override them, which isn't recommended.

Re: Is There a Port for a compiler compatible with OpenMP and Imagemagick

> On Apr 25, 2017, at 18:38, Fred Weinhaus wrote: > > I am trying to install Imagemagick from source using all my delegates > installed from MacPorts. I have been doing this for years on OSX > SnowLeopard. But I recently bought a new Mac with OSX 10.12.4 Sierra and > the compiler will compile Im

Re: binutils warning

> On Apr 24, 2017, at 14:22, db wrote: > >> On 22 Apr 2017, at 20:21, Ryan Schmidt wrote: >> Feel free to re-test the ports that failed to build back then that caused us >> to add that warning. > > #22539 atlas (also #22674) -> it built for hours and I di

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 @5.

Re: qt5 build dependency on clang

> On Apr 22, 2017, at 15:55, db wrote: > > On 22 Apr 2017, at 21:58, Ryan Schmidt wrote: >> Sounds plausible. What's your question / problem with this? > > Ken already point me to cxx11-1.1.tcl, but I still don't get why 4.0 isn't > whitelisted in a

Re: qt5 build dependency on clang

On Apr 22, 2017, at 13:56, db wrote: > > On a 10.8.5-system with default compiler qt5 @5.7.1 and qt56 @5.6.2 require > clang-4.0 to build, while another whose compiler is set to clang-3.9 shows > this as dependency. Can anyone confirm the former? Sounds plausible. What's your question / problem

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 prepended with g like those > from coreutils —

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 upgrade of libressl to >>> 2.5.3. >>> >>> Rebuild succeeded o

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 > '/var/folders/sr/_cb62lmn0v36cvbz11hjgy7rgn/T/xcrun_db-eQZtJHV5' > (errno

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 >> uninstall qt5-qteng

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. > > Ken > > > On 2017-04-18, at 3:00 P

Re: qt5-qtenginio is obsolete

will be fixed the next time I upgrade outdated. The file name is > suspiciously similar to the qt5-qtenginio port that was obsolete. > > -Original Message- > From: Ryan Schmidt > Date: Tuesday, April 18, 2017 at 9:24 AM > > >> On Apr 18, 2017, at 11:23, Fielding, Eric J

Re: qt5-qtenginio is obsolete

o did a “port reclaim” to remove all the outdated ports that might > depend on the old qt5. > > -Original Message- > From: "Eric J. Fielding" > Date: Tuesday, April 18, 2017 at 7:28 AM > To: Ryan Schmidt > Cc: MacPorts Users > Subject: Re: qt5-qtenginio

Re: qt5-qtenginio is obsolete

qtwebchannel @5.7.1_0 (active) > qt5-qtwebsockets @5.6.2_0 > qt5-qtwebsockets @5.7.1_0 (active) > qt5-qtxmlpatterns @5.6.2_0 > qt5-qtxmlpatterns @5.7.1_0 (active) > qt5-sqlite-plugin @5.6.2_0 > qt5-sqlite-plugin @5.7.1_0 (active) > > ++Eric > > -Original Mes

Re: port leaf becoming requested

> On Apr 18, 2017, at 07:37, db wrote: > > On 18 Apr 2017, at 13:07, Ryan Schmidt wrote: >> Yes, installing a port should mark it requested. I'm unclear what happened >> in your situation. > > This is what I do: > > Last login: Tue Apr 18 14:14:12 on tt

Re: qt5-qtenginio is obsolete

> On Apr 17, 2017, at 20:27, Fielding, Eric J (329A) > wrote: > > I might have missed something in the last few months, but I didn’t find a > mention of this. > > I did a “port upgrade outdated” after a month or two, and I got this error > message: > > Error: qt5-qtenginio is obsolete; pl

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 set

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 Vers

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. The source can be found here >> after the

Re: notes repeatedly showing in port session

> On Apr 12, 2017, at 09:01, db wrote: > > On 12 Apr 2017, at 11:02, db wrote: >> On 12 Apr 2017, at 01:19, Ryan Schmidt wrote: >>> That sounds like a bug. We probably didn't test the change with shell mode. >> #53967, I hope I filed it correctly. >

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 with shell mode.

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: https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/25779

<    10   11   12   13   14   15   16   17   >