On Aug 20, 2013, at 21:04, Stubbs Jeff wrote:
> I'm going to start testing the system shortly, but was curious if any one was
> able to install the ports without modification?
Yes, I can install them OK on Mountain Lion without changes.
> modified the deployment target to "macosx_deployment_ta
Definitely pass it along, but ecdsa sounds like public key. Is it just elliptic
curves it shuts off?
Stubbs Jeff wrote:
>Hi All,
>
>Wanted to integrate DomainKeys with the firm's Postfix mail server. So
>when I spotted the openDKIM port in the repository, I tried to install
>the dependencies fir
Hi All,
Wanted to integrate DomainKeys with the firm's Postfix mail server. So when I
spotted the openDKIM port in the repository, I tried to install the
dependencies first. The ldns port failed first attempt. Running the install
command in verbose mode, I noticed that it was failing in the co
On Aug 20, 2013, at 12:35 PM, Peter Danecek wrote:
> Should I compile a ticket against base?
Shouldn't be necessary.
What I think is happening is that your configure.compiler value is being
propagated to dependencies. So MacPorts needs to build llvm-3.3 as a dependency
of clang-3.3, but then
On Aug 20, 2013, at 18:19 , Lawrence Velázquez wrote:
>
> Yes, we'd have to see the main.log produced from the failure (or, if you
> can't find one, then the debug output from a "port -d" invocation).
>
> vq
Here the main.log I regenerated again!
libgcrypt.main.log
Description: Binary data
On Aug 20, 2013, at 17:43 , Lawrence Velázquez wrote:
> You're asking the wrong questions.
Well, if it was only about upgrading this port your are probably right.
> You don't really care about blacklisting;
If I want to understand what is going on, it probably helps to know the
background. An
On Aug 20, 2013, at 12:06 PM, Peter Danecek wrote:
> On Aug 20, 2013, at 17:43 , Lawrence Velázquez wrote:
>
>> what you want to do is get libgcrypt to build, and the easiest way for you
>> to accomplish this quickly is:
>>
>> % sudo port install libgcrypt configure.compiler=macports-clang-
You're asking the wrong questions. You don't really care about blacklisting;
what you want to do is get libgcrypt to build, and the easiest way for you to
accomplish this quickly is:
% sudo port install libgcrypt configure.compiler=macports-clang-3.3
On Aug 20, 2013, at 9:26 AM, Peter Dane
Hi
I just added "use_autoreconf yes" to a port file as I was patching the
build system however the buildbot is failing as it appears that it's
using the system autotools:
gnuscripts/lalsuite_build.m4:23: warning: macro `AM_COND_IF' not found
in library
gnuscripts/lalsuite_swig.m4:110: warning: ma
Hi all,
I am trying to upgrade libgcrypt to 1.5.3 on my MacOSX 10.5.8 machine. The
Problems are:
1. apple-gcc42 would not compile on that machine, ticket #36648;
2. libgcrypt has some compiler blacklisting logic and therefore seems to select
that compiler.
As a result I cannot build libgcryp
10 matches
Mail list logo
