I use Ubuntu, in which the bug appears with GCC 4.1 and not with GCC 4.0. That's why I assumed that the same bug appears in Debian.
The problem is not that Erlang does not start. Instead, it is that the
crypto module does not load correctly:
*****
[EMAIL PROTECTED]:~$ erl
Eshell V5.5.1 (abort with ^G)
1> crypto:start().
exec: 1: ok
2> crypto_drv: not found
=ERROR REPORT==== 25-Oct-2006::12:57:02 ===
** Generic server crypto_server terminating
** Last message in was {'EXIT',#Port<0.96>,normal}
** When Server state == {#Port<0.96>,[]}
** Reason for termination ==
** {port_died,normal}
exec: 1: crypto_drv: not found
*****
If this does work for you without problems (it should only output exec:
1: ok and nothing more) in Debian with erlang compiled using GCC 4.1,
then please close this bug.
Martin
signature.asc
Description: This is a digitally signed message part
