On Sep 14, 2013, at 9:51 PM, Joshua Root wrote:
>> Revision: 111056
>> https://trac.macports.org/changeset/111056
>> Author: larryv at macports.org
>> Date: 2013-09-13 18:42:54 -0700 (Fri, 13 Sep 2013)
>> Log Message:
>> ---
>> gettext: Run autoreconf to get libtool that pa
> Revision: 111056
> https://trac.macports.org/changeset/111056
> Author: larryv at macports.org
> Date: 2013-09-13 18:42:54 -0700 (Fri, 13 Sep 2013)
> Log Message:
> ---
> gettext: Run autoreconf to get libtool that passes -stdlib when linking
> dylibs.
This introduces a
On Sat, Sep 14, 2013 at 06:09:09AM -0500, Ryan Schmidt wrote:
> […] so I thought gcc48 was best as a default for other cases as well,
> and changed the recipe in the wiki page a couple days ago.
I wasn't aware of that.
> Unless you know a reason why we shouldn't change to gcc48?
No.
--
Clemen
On Sep 14, 2013, at 05:09, Clemens Lang wrote:
> On Sep 14, 2013 9:08 AM, Ryan Schmidt wrote:
>> Can we make gcc48 the default now?
>
> Have we decided gcc48 is our new default compiler?
Well Jeremy H S made gcc48 the default in the fortran recipe that he put in a
lot of ports, so I thought gcc
Hi,
On Sat, Sep 14, 2013 at 12:26:16AM -0700, mar...@macports.org wrote:
> Revision: 111075
> https://trac.macports.org/changeset/111075
> Author: mar...@macports.org
> Date: 2013-09-14 00:26:16 -0700 (Sat, 14 Sep 2013)
> Log Message:
> ---
> port1.0: added porttest.test fi
Hi,
On Sep 14, 2013 9:08 AM, "Ryan Schmidt" wrote:
> Can we make gcc48 the default now?
Have we decided gcc48 is our new default compiler?
--
Clemens
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman
On Sep 13, 2013, at 17:50, c...@macports.org wrote:
> Revision: 111036
> https://trac.macports.org/changeset/111036
> Author: c...@macports.org
> Date: 2013-09-13 15:50:54 -0700 (Fri, 13 Sep 2013)
> Log Message:
> ---
> ghc: add variants for gcc48 and 49
>
> Modified Paths
