Hi,
I think I stumbled upon a more likely reason for the build issues evoked below.
There's been a change in the cmake portgroup,
registry/portgroups/636464737c420ea283d4ad483ea35193d9da591588cba9f1d1d4e56d8ff6912e-6789/cmake-1.0.tcl
vs.
On 29/07/14 03:20, Sam Finn wrote:
I do have Intego’s NetBarrier installed; however, I’ve shut it down for these
operations.
Remove it completely then try... My suspicion is it is still somehow in
the way...
--
Lee Samuel Finn
lsf...@gmail.com
On Jul 28, 2014, at 10:16 PM, Ryan
On Tue, Jul 29, 2014 at 10:24 AM, René J.V. Bertin wrote:
Hi,
I think I stumbled upon a more likely reason for the build issues evoked
below. There's been a change in the cmake portgroup,
registry/portgroups/636464737c420ea283d4ad483ea35193d9da591588cba9f1d1d4e56d8ff6912e-6789/cmake-1.0.tcl
Morning!
On Jul 29, 2014, at 10:01, Frank Osterfeld wrote:
On 28 Jul 2014, at 23:30, René J.V. Bertin rjvber...@gmail.com wrote:
I just stumbled across a Cmake variable/flag, MAC_USE_OSXKEYCHAIN :
option(MAC_USE_OSXKEYCHAIN On OS X, use the keychain as backend for
kwallet, instead of
This reminds me, the configure script for subversion checks for both
kwallet support and for OSX KeyChain support... is there any point in
configuring it with both if kwallet is just using the system keychain as a
backend in the first place?
On Tue, Jul 29, 2014 at 6:06 AM, René J.V. Bertin
On Jul 29, 2014, at 12:54, Eric Gallager wrote:
This reminds me, the configure script for subversion checks for both kwallet
support and for OSX KeyChain support... is there any point in configuring it
with both if kwallet is just using the system keychain as a backend in the
first place?
On Tue, Jul 29, 2014 at 11:36 AM, René J.V. Bertin wrote:
On Jul 29, 2014, at 10:51, Mojca Miklavec wrote:
You reversed the direction of the commit
Indeed ...
(http://trac.macports.org/changeset/121112), but adding
configure.cppflags is certainly not acceptable as it causes way too
many
After seeing https://trac.macports.org/ticket/44485 filed against
open-cobol about this same issue, I decided to check up on the upstream bug
I had filed that was blocking my update to version 2.0, and found that it
had some new responses: https://sourceforge.net/p/open-cobol/bugs/73/
Could
On Jul 28, 2014, at 11:56 AM, Jonathan Stickel jjstic...@gmail.com wrote:
Date: Sun, 27 Jul 2014 13:47:20 -0500
From: Mark Brethen mark.bret...@gmail.com
Subject: py-cvxopt +DSDP
py-cvxopt installed fine without any errors. However, when I tried running
example code it reports:
Symbol
On Jul 29, 2014, at 11:38 AM, Eric Gallager eg...@gwmail.gwu.edu wrote:
After seeing https://trac.macports.org/ticket/44485 filed against open-cobol
about this same issue, I decided to check up on the upstream bug I had filed
that was blocking my update to version 2.0, and found that it had
10 matches
Mail list logo
