Multiple definitions of read and write in nrf_fstorage_nvmc.c

[Kenzi]

Ran in to a build error when using nrf_fstorage_nvmc.c:
\components\libraries\fstorage\nrf_fstorage_nvmc.c(128,19): error : conflicting types for 'write'

nrf_fstorage_nvmc.c
-> declares static read() and static write()
-> includes \modules\nrfx\hal\nrf_nvmc.h
  -> includes \modules\nrfx\nrfx.h
    -> includes \integration\nrfx\nrfx_glue.h
      -> includes \components\libraries\util\app_util_platform.h
        -> includes \components\libraries\util\app_error.h
          -> includes \arm-eabi\sys-include\stdio.h
            -> includes \arm-eabi\sys-include\sys\types.h
              -> includes \components\iot\socket\api\sys\select.h
                -> includes \components\iot\socket\api\socket_api.h
                  -> declares read() and write()

I installed 15.3 yesterday and this is the second build error I've run in to in as many days. 

[Alexander2]

Probably the simplest way to get it working is patch the file nrf_fstorage_nvmc.c. Rename these two conflicting functions. For example - read->read_, write->write_

[Vidar Berg]

Agree. The naming should have been unique in fstorage. nrf_send() for instance, but are you using the Socket API in your app. If not you can remove it. 

I noticed that it says "arm-eabi" in your include path, it's generally recommended to use the same toolchain as specified in the SDK release notes (GCC ARM Embedded 7.2018q2.update for SDK 15.3.0).