KeepAlive has been enabled, max requests set to 1000.
-Bill
On Jul 15, 2013, at 8:41 AM, Daniel J. Luke wrote:
> On Jul 12, 2013, at 9:55 PM, Lawrence Velázquez wrote:
>> Independent of updating Subversion, would it be beneficial to turn on
>> KeepAlive?
>
>
> probably. I think the apache
attached is an improved version.
Changes:
- Clean function: "mac-ports-bundle.sh clean"
- installs into /opt/local/libexec/macports
- use sha checksum to validate curled tar files
-gustaf
Am 14.07.13 06:11, schrieb Ryan Schmidt:
On Jul 13, 2013, at 08:37, Lawrence Velázquez wrote:
On Jul 13,
No. The maintainer is on vacation until next week. The port is open maintainer
if someone else has commit rights.
--
Tersely written with my 'Droid
MacPorts wrote:
>#39698: sbcl @1.1.8: update to 1.1.9 and revbump maxima
>--+
> Reporter: crossd
On Jul 15, 2013, at 10:13 AM, Joshua Root wrote:
> The categories field now lists python twice. If python is not intended
> to be the primary category, then the port dir needs to be moved as well.
No, sorry, asleep at the wheel. Undone in r108191.
vq
On Jul 12, 2013, at 9:55 PM, Lawrence Velázquez wrote:
> Independent of updating Subversion, would it be beneficial to turn on
> KeepAlive?
probably. I think the apache shipped conf files have it 'on' by default
(although some distros change it). The subversion docs recommend having it on
and
> Revision: 108172
> https://trac.macports.org/changeset/108172
> Author: larryv at macports.org
> Date: 2013-07-14 23:40:49 -0700 (Sun, 14 Jul 2013)
> Log Message:
> ---
> py*-openbabel: Add to python category.
>
> Modified Paths:
> --
> trunk/dports/python
> cadabra just finished building successfully for me with gcc-4.2 on
> Snow Leopard. What steps should I now perform to verify whether it
> works correctly?
'make test' and 'make advtest' should both complete without errors.
> configure.compiler gcc-4.Z means the FSF GCC compiler version 4.Z as
>
On Jul 15, 2013, at 03:02, Ryan Schmidt wrote:
> configure.compiler apple-llvm-gcc-4.2 means the LLVM GCC 4.2 compiler as
> installed by the MacPorts llvm-gcc42 port in /opt/local/bin/llvm-gcc-4.2. It
> should be the same software as Xcode provides, or perhaps a slightly newer
> version. The p
On Jul 15, 2013, at 02:33, Kasper Peeters wrote:
>> I believe the developer is confusing "gcc-4.2" with "gcc42".
>
> I may very well have at some point (given they look, eh, kinda
> similar ;-) ). I don't think that's the issue anymore. The issue is
> definitely that if I do not restrict to Appl
> I believe the developer is confusing "gcc-4.2" with "gcc42".
I may very well have at some point (given they look, eh, kinda
similar ;-) ). I don't think that's the issue anymore. The issue is
definitely that if I do not restrict to Apple's gcc version 4.2 but
allow the Macports gcc version 4.2 a
On Jul 15, 2013, at 01:42, Lawrence Velázquez wrote:
> On Jul 14, 2013, at 6:40 PM, Ryan Schmidt wrote:
>
>> The gcc-4.2 compiler shipped in Xcode 3 is not suitable?
>
> I'm not sure. The developer seems to be having issues sorting out libstdc++
> and seems to find apple-gcc-4.2 to be the only
> > The gcc-4.2 compiler shipped in Xcode 3 is not suitable?
>
> I'm not sure. The developer seems to be having issues sorting out
> libstdc++ and seems to find apple-gcc-4.2 to be the only usable
> compiler. I have my doubts.
>
> https://trac.macports.org/ticket/38938
> https://lists.macosforge.
12 matches
Mail list logo
