cc1 throwing "no such file or directory" even though path is correct and file is there (sdk 14)

[MattFL]

I'm attempting to build the ble_app_hids_keyboard example from sdk 14 using gcc and the compiler is throwing the error "No such file or directory", but the file is there and the path is correct.  Oddly it will build some files just fine, but give the error for other files.  Has anyone seen this before?  Here is the output: 

N:\examples\ble_peripheral\ble_app_hids_keyboard\pca10040\s132\armgcc>make
Compiling file: nrf_log_backend_rtt.c
Compiling file: nrf_log_backend_serial.c
Compiling file: nrf_log_backend_uart.c
Assembling file: gcc_startup_nrf52.S
cc1.exe: fatal error: ../../../../../../components/toolchain/gcc/gcc_startup_nrf52.S: No such file or directory
compilation terminated.
make: *** [../../../../../../components/toolchain/gcc/Makefile.common:280: _build/nrf52832_xxaa/gcc_startup_nrf52.S.o] Error 1

N:\examples\ble_peripheral\ble_app_hids_keyboard\pca10040\s132\armgcc>dir ..\..\..\..\..\..\components\toolchain\gcc\gcc_startup_nrf52.S
 Volume in drive N is Google Drive File Stream
 Volume Serial Number is 1983-1116

 Directory of N:\components\toolchain\gcc

11/14/2017  03:01 PM            12,798 gcc_startup_nrf52.S
               1 File(s)         12,798 bytes
               0 Dir(s)  708,252,553,216 bytes free

N:\examples\ble_peripheral\ble_app_hids_keyboard\pca10040\s132\armgcc>arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


N:\examples\ble_peripheral\ble_app_hids_keyboard\pca10040\s132\armgcc>make --version
GNU Make 4.2.1
Built for x86_64-w64-mingw32
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

[MattFL]

I found the problem.  The files were on a Google Filestream drive, and apparently that was the problem.  After moving the directory tree into a directory that is not under my filestream drive letter everything seems to be working.