Windows dependency file contains invalid absolute paths
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Arm Embedded Toolchain |
New
|
Undecided
|
Unassigned |
Bug Description
Toolchain: 10.0 Q4 2020 (verified with binary package only)
Host machine: Windows 10 build 1803 (Command Prompt, nmake 9.0)
The Windows toolchain releases enabled automatic conversion from relative to absolute paths (ENABLE_
The path conversion works fine in these .d files using any version from 4.8 Q2 2014 to 9.0 Q2 2020 update. If I update to 10.0 Q4 2020, any converted paths in my .d files start with the incorrect prefix "c\:" instead of "c:", which then breaks subsequent builds.
Example minimal project attached:
- Extract zip to c:\test
- Zip contains test.c, which does nothing useful but include test.h using a long relative path (via the dummy subdirectory 0123456789ABCDEF)
- Set environment variable _GCCARM_CC_BIN to the bin folder of your GCC ARM 10.0 installation (or just modify the CC path in MAKEFILE)
- Compile and check output test.d dependency file contents:
test.exe: test.c c\:\test\test.h
Downgrading the toolchain below 10.0 produces the correct output in test.d:
test.exe: test.c c:\test\test.h
Hi,
Is this issue (https:/ /bugs.linaro. org/show_ bug.cgi? id=5750) similar to yours Matthew?
/Przemek