Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Apr 2004 16:27:44 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        Ade Lovett <ade@FreeBSD.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: automake 1.4 -> 1.8 ?
Message-ID:  <Pine.BSF.4.53.0404091624480.53738@e0-0.zab2.int.zabbadoz.net>
In-Reply-To: <B66B6F50-8A3D-11D8-94AA-000A956B6386@FreeBSD.org>
References:  <Pine.BSF.4.53.0404091536540.53738@e0-0.zab2.int.zabbadoz.net> <B66B6F50-8A3D-11D8-94AA-000A956B6386@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 9 Apr 2004, Ade Lovett wrote:

> On Apr 09, 2004, at 08:41, Bjoern A. Zeeb wrote:
>
> > I am just at the point updating a port and have seen the note in
> > automake14 Makefile that it says one should use automake18 with the
> > beginning of 2005.
> >
> > But bsd.port.mk does not know about automake18 yet and thus
> > automatically marks the port as BROKEN when one tries to use
> > automake18.
>
> There is a pending update to break out all of the autotools gunk from
> bsd.port.mk to bsd.autotools.mk, which will be closely followed by an
> update to bsd.autotools.mk to handle any and all versions of
> libtool/autoconf/automake in the tree.
>
> The message is purely advisory at the moment.

Thanks for your response. Will there then also be a chance to run
aclocal and libtool ?

Currently it is not possible to call ${LIBTOOLIZE} after
patch-libtool and before run-autotools and run-autotools does not
call LIBTOOLIZE.

aclocal still can be run from pre-configure I think.

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0404091624480.53738>