I'd love to release a patch with my software, but the license that has
been chosen is LGPL (since it's a framework), so I don't want to
distribute a GPL-licensed source file (or patch to one) along with it.
However, if I simply redefine AC_LANG(Erlang) to do the right thing in
my configure.ac it seems to work.
-- Samuel
On Dec 31, 2008, at 2:06 PM, Eric Blake wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Samuel Tesla on 12/31/2008 11:58 AM:
Hello there!
I am encountering an issue that appears to be due to the bug in
erlang.m4 that was discovered back in September. It was mentioned
in the
thread then that this might warrant releasing 2.64. The fix appears
to
be in git as commit 20c24928. Are there any plans for getting a
release
out soon?
Thanks for the followup. As this is an open source project done
entirely
on volunteer time, I hesitate to commit to any firm release date.
On the
other hand, we've made a number of substantial improvements since
2.63,
and I really want a beta release of 2.63b (or name it 2.64) in the
near
future so we can start checking for regressions. However, there are
still
a few sticking points that it would be nice to resolve before a
release,
such as making the parallel autotest suites less likely to fork-bomb
on
BSD systems. In the meantime, you can use the latest unreleased
software,
or backport just the patch you needed and apply it on top of your
build of
2.63.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@xxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklb0LwACgkQ84KuGfSFAYCtuACeIpclAS9wBX+hPA6T0CkhvgVt
x7IAoLseQai1zHhsP6aZTV72WbN11gWI
=JnGw
-----END PGP SIGNATURE-----
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
