This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF connect SDK fails to build with "attempt to assign the value 'y' to the undefined symbol"

Hi,

Just reporting an issue I am having with the nRF9160 SDK in the hope that it will help someone else. OS is Ubuntu 18.04.

I was getting errors which look like this:

/home/jeremy/nrfconnect/ncs/nrf/samples/nrf9160/https_client/prj.conf:2: warning: attempt to assign the value 'y' to the undefined symbol BSD_LIBRARY

/home/jeremy/nrfconnect/ncs/nrf/samples/nrf9160/https_client/prj.conf:3: warning: attempt to assign the value 'n' to the undefined symbol BSD_LIBRARY_SYS_INIT

/home/jeremy/nrfconnect/ncs/nrf/samples/nrf9160/https_client/prj.conf:12: warning: attempt to assign the value 'y' to the undefined symbol MODEM_KEY_MGMT

/home/jeremy/nrfconnect/ncs/nrf/samples/nrf9160/https_client/prj.conf:13: warning: attempt to assign the value 'y' to the undefined symbol LTE_LINK_CONTROL

and these were preventing the build from completing. The issue here is that the nRF connect setup asks you to install the pip libraries using the --user flag, which will put everything in ~/.local/bin. However, this path is not part of the default PATH environment variable. Adding this to the path in Segger Embedded Studio (or CLion in my case) is what fixed the problem.

Parents Reply Children
No Data
Related