esock_atom_user problem and Android builds

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

esock_atom_user problem and Android builds

Joacim Grebenö
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@eve:~/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/gen_git_version.mk
  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;

Reply | Threaded
Open this post in threaded view
|

Re: esock_atom_user problem and Android builds

Micael Karlberg-5
Hi,

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

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

Must have missed one :(

Regards,
        /BMK

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@eve:~/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/gen_git_version.mk
>   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;
>
>
Reply | Threaded
Open this post in threaded view
|

Re: esock_atom_user problem and Android builds

Micael Karlberg-5
A fix has now been merged (into maint and master).

On 2020-01-10 13:56, Micael Karlberg wrote:
> Hi,
>
> It seems you are correct. Those kind of atoms are (supposed to be)
> created:
>
>      GLOBAL_ATOM_DEFS (in socket_int.h)
>      GLOBAL_ATOMS     (in socket_nif.c)
>
> Must have missed one :(

Actually I missed two (also esock_atom_kernel).

>
> Regards,
>      /BMK
>

Regards,
        /BMK

> 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@eve:~/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/gen_git_version.mk
>>   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;
>>
>>
>