[adding Romain as the original erlang contributor, hoping the email address in THANKS is still valid]
> > And sadly, this means that both 2.62 and 2.63 are completely unusable > > with Erlang (maybe this warrants a 2.64 release soon?) > > I'd say that depends a bit on the motivation of whoever will do the > release. :-) > > But anyway the bug really warrants testsuite exposure. > It would have been caught before the release if there was > an erlang compile and execution test. Agreed - I won't even be considering a release of 2.64 unless someone more familiar with Erlang than me steps up and contributes a testsuite addition (for that matter, I'm not even sure whether an Erlang interpreter has been ported to cygwin, which is where I tend to do most of my autoconf development). -- Eric Blake
