Bug#408077: crypto module not working when compiled with gcc 4.1

[Martin Jürgens]

Package: erlang
Version: 1:11.b.2-4

The crypto module is not working when compiling erlang with gcc 4.1:

zeank@sz2:~/src/ejabberd111/src$ erl
Erlang (BEAM) emulator version 5.5.1 [source] [async-threads:0]
[kernel-poll:false]

Eshell V5.5.1 (abort with ^G)
1> crypto:start().
exec: 1: ok
2> crypto_drv: not found
[.........]

A fix is to add

-fno-stack-protector

to the CFLAGS as suggested here:
http://forum.trapexit.org/viewtopic.php?t=6630&highlight=cryptodrv

Ubuntu bug report is here:
https://launchpad.net/ubuntu/+source/erlang/+bug/68163

[Sergei Golovan]

On 1/23/07, Martin Jürgens <mar...@gamesplace.info> wrote:
> Package: erlang
> Version: 1:11.b.2-4
>
> The crypto module is not working when compiling erlang with gcc 4.1:

Which Debian distribution and architecture are you using? Erlang,
which is in etch now (1:11.b.2-4), definitely is built using GCC 4.1,
and it works (at least for i386).

--
Sergei Golovan

[Martin Jürgens]

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:

*****

martin@astebuntu:~$ 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