On Dec 15, 2014, at 11:41 PM, Joshua Root wrote:
>> Howdy all.
>>
>> I’ve been using macports for a number of years, but have never figured out
>> how to readily identify NEW ports (newly available ports, not updates of
>> existing packages). I am forced to root around in the ports list or th
On 2014-12-18 01:53 , Tres Finocchiaro wrote:
> I'll fire up a Lion VM for this, thank you.
NP. That's probably the best approach.
- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/m
On Wed, Dec 17, 2014 at 9:47 AM, Joshua Root wrote:
>
> Xcode 3.x is not the right version to use with Lion, 4.x is. 3.1 is for
> Leopard and 3.2 is for Snow Leopard. IIRC, 3.2.6 didn't even work right
> on Lion, so I wouldn't expect it to work on Mavericks.
>
Sorry, typo, 4.6.3 is the exact Lion
> Hi,
>
> I'm recently trying to bundling some backwards compat software packages
> using a Lion version of XCode (3.x) on Mavericks and MacPorts.
Xcode 3.x is not the right version to use with Lion, 4.x is. 3.1 is for
Leopard and 3.2 is for Snow Leopard. IIRC, 3.2.6 didn't even work right
on Li
Hi,
I'm recently trying to bundling some backwards compat software packages
using a Lion version of XCode (3.x) on Mavericks and MacPorts.
However, Mavericks had previously been setup with MacPorts and the
Mavericks version of XCode (5.x).
The compilation is succeeding when I force the Lion bui
At 10:20 AM +0100 12/17/14, Vincent Habchi wrote:
> On 16 Dec 2014, at 16:37, Craig Treleaven wrote:
https://trac.macports.org/ticket/38834
See also:
Thanks so much Craig.
Is there any reason why the port hasn't been committed? I got a bit
lost in all the comments.
I don't really know.
> On 16 Dec 2014, at 16:37, Craig Treleaven wrote:
> https://trac.macports.org/ticket/38834
> See also:
Thanks so much Craig.
Is there any reason why the port hasn’t been committed? I got a bit lost in all
the comments.
Vincent
___
macports-users mai
