esock_atom_user problem and Android builds

Micael Karlberg micael.karlberg@REDACTED
Fri Jan 10 13:56:00 CET 2020


It seems you are correct. Those kind of atoms are (supposed to be)

	GLOBAL_ATOM_DEFS (in socket_int.h)
	GLOBAL_ATOMS     (in socket_nif.c)

Must have missed one :(


On 2020-01-09 14:43, Joakim G. wrote:
> Hi,
> I'm trying to cross compile BEAM for Android but I'm stuck on a compile error.
> It seems that 'esock_atom_user' is undeclared and I can not even find any decalartion of it on the 
> emulator/erts code.
> Can anyone point me in the right direction?
> Cheers
> /Joakim
> jocke@REDACTED:~/src/erlang/otp_src_22.2$ make noboot
> make USE_PGO=false BOOT_PREFIX= build_erl_interface emulator libs local_setup
> ...
> make[4]: Går till katalogen ”/home/jocke/src/erlang/otp_src_22.2/erts/emulator”
>   MAKE    opt
> make[5]: Går till katalogen ”/home/jocke/src/erlang/otp_src_22.2/erts/emulator”
>   GEN    arm-unknown-linux-androideabi/
>   CC    obj/arm-unknown-linux-androideabi/opt/smp/socket_util.o
> nifs/common/socket_util.c: In function 'esock_encode_packet_pkttype':
> nifs/common/socket_util.c:1495:21: error: 'esock_atom_user' undeclared (first use in this function)
>           *ePktType = esock_atom_user;

More information about the erlang-questions mailing list