Hi,
On Mon, Jun 22, 2020 at 01:19:34PM -0700, Jeremy Huddleston Sequoia wrote:
> 1) libtool required an update for the version bump. This means many
> projects might need an autoreconf to build correctly.
Should we just make running autoreconf for autotools and automake builds
the default? This
Everyone, please use the new list addresses at lists.macports.org, not the old
macosforge addresses that were deprecated in 2016.
On Jun 23, 2020, at 01:40, Vincent Habchi wrote:
> Wouldn’t it be possible to somehow set up a new hardware machine with
> MacPorts installed and give all
t; the major first step here.
>
> On Tue, Jun 23, 2020 at 1:41 AM Vincent Habchi <mailto:vi...@macports.org>> wrote:
>
> > On 22 Jun 2020, at 22:19, Jeremy Huddleston Sequoia > <mailto:jerem...@macports.org>> wrote:
> >
> > I just pushed some change
n Sequoia <
> jerem...@macports.org> wrote:
> >
> > I just pushed some changes to base/master and dports/master to better
> support macOS 11 and Apple Silicon, but there's quite a bit of work ahead
> of us.
>
> […]
>
> > Please reach out if you have any q
> On 22 Jun 2020, at 22:19, Jeremy Huddleston Sequoia
> wrote:
>
> I just pushed some changes to base/master and dports/master to better support
> macOS 11 and Apple Silicon, but there's quite a bit of work ahead of us.
[…]
> Please reach out if you have any questions o
I just pushed some changes to base/master and dports/master to better support
macOS 11 and Apple Silicon, but there's quite a bit of work ahead of us.
Some common issues to be aware of:
1) libtool required an update for the version bump. This means many projects
might need an autoreconf
