On Sep 9, 2012, at 08:07, Mark Evenson wrote:
> On Sep 9, 2012, at 2:52 PM, Ryan Schmidt wrote:
>
>> On Sep 9, 2012, at 07:35, easie...@macports.org wrote:
>>
>>> Needed to explicitly name llvm-gcc-4.2 as the compiler for OS X 12.x.
>>> Maybe this needs to be done for other platforms?
>>
>> Wh
On Sep 9, 2012, at 2:52 PM, Ryan Schmidt wrote:
>
> On Sep 9, 2012, at 07:35, easie...@macports.org wrote:
>
>> Needed to explicitly name llvm-gcc-4.2 as the compiler for OS X 12.x.
>> Maybe this needs to be done for other platforms?
>
> Why? What happened using clang?
The build fails with c
On Sep 9, 2012, at 07:35, easie...@macports.org wrote:
> Needed to explicitly name llvm-gcc-4.2 as the compiler for OS X 12.x.
> Maybe this needs to be done for other platforms?
Why? What happened using clang?
If anything, the compiler choice should be based on the Xcode version, not the
OS ve
On Sep 9, 2012, at 05:44, dev...@macports.org wrote:
> Revision: 97564
> https://trac.macports.org/changeset/97564
> Author: dev...@macports.org
> Date: 2012-09-09 03:44:06 -0700 (Sun, 09 Sep 2012)
> Log Message:
> ---
> gimp-gap: apply patch to allow use of ccache (#35556)
On Sep 9, 2012, at 04:12, easie...@macports.org wrote:
> Revision: 97561
> https://trac.macports.org/changeset/97561
> Author: easie...@macports.org
> Date: 2012-09-09 02:12:34 -0700 (Sun, 09 Sep 2012)
> Log Message:
> ---
> emacs-w3m-dev: Track the CVS version of W3M for E
On Sep 3, 2012, at 9:15 AM, Joshua Root wrote:
> At a high level, this is what MacPorts wants:
> * to deny write access to everything outside ${workpath} for most
> phases, excepting also a handful of other places on a per-phase basis
> (like ${distpath} for fetch).
> * to deny read access to an