Kevin P. Fleming wrote:
I think we should do that, especially because it will reduce the size of
the generated aclocal.m4 (and potentially the configure script itself,
depending on how smart m4 is).
Alright, I'll work on doing that right now. However, I don't think the size of
aclocal.m4 real
Russell Bryant wrote:
> That macro is provided when you install libtool. We can work around
> that dependency by copying the macro into our file that contains our
> custom macros, acinclude.m4 if we would like.
I think we should do that, especially because it will reduce the size of
the generated
On Mon, Nov 06, 2006 at 03:16:45PM -0600, Kevin P. Fleming wrote:
> Luigi Rizzo wrote:
> > after this commit acloca.m4e went up from one line to over 6200:
> >
> > http://svn.digium.com/view/asterisk/trunk/aclocal.m4?rev=46846&view=log
> >
> > surely there must be a more compact way to figure out
Kevin P. Fleming wrote:
However, it appears that using macro brought in _all_ of the
libtool-related macros. Probably we can just copy AC_PROG_LD_GNU and its
sub-macros directly into acinclude.m4 instead, and not bring in all the
other libtool stuff.
Yeah, sorry about that. This is just what h
Luigi Rizzo wrote:
> after this commit acloca.m4e went up from one line to over 6200:
>
> http://svn.digium.com/view/asterisk/trunk/aclocal.m4?rev=46846&view=log
>
> surely there must be a more compact way to figure out whether we
> are using gnu-ld or something else ?
This macro is what GNU lib
