Enabling CONFIG_POSIX_API w/ NRF v1.0.0 causes linker error for multiple definitions of fcntl

[jbrzozoski]

While trying to upgrade my application from v0.4.0 to v1.0.0, I bumped into this issue.  I am using CONFIG_POSIX_API primarily for the clock functions like clock_settime and clock_gettime.

The "desirable" definition is the one in subsys/net/lib/sockets/socket_offload.c, and the "unwanted" definition is the one over in lib/os/fdtable.c.

It looks like at least one other architecture simply skips the fdtable version based on the architecture type.  I suspect the same may be needed for nRF9160...

[jbrzozoski]

Yes, I confirmed that this can be reproduced by adding CONFIG_POSIX_API=y to the mqtt_simple sample prj..conf and rebuilding.

[Joakim Jakobsen]

Hi. 

Thanks for the feedback. I talked to one of my colleagues and we were able to reproduce this. 

I have reported this internally. 

Best regards, 
Joakim

[jbrzozoski]

Just bumped into this ticket on upstream Zephyr which I suspect is related:

https://github.com/zephyrproject-rtos/zephyr/issues/12368

[Joakim Jakobsen]

Thanks. 

It seems that they might be related. I'll forward this to the guys working on this.