patacongo commented on issue #1672:
URL: 
https://github.com/apache/incubator-nuttx/issues/1672#issuecomment-683454953


   > $ dir `arm-none-eabi-gcc --print-file-name=libgcc.a`
   > dir: cannot access 'c:/program': No such file or directory
   > dir: cannot access 'files': No such file or directory
   > dir: cannot access '(x86)/gnu': No such file or directory
   > dir: cannot access 'arm': No such file or directory
   > dir: cannot access 'embedded/9': No such file or directory
   > dir: cannot access 
'2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/libgcc.a'$'\r': No such file 
or directory
   > ...
   
   Just as a clarification.  The above uses the command 'dir' which is not the 
same as the make 'dir' command.  So lets do things right:
   
       diff --git a/arch/arm/src/armv7-m/Toolchain.defs 
b/arch/arm/src/armv7-m/Toolchain.defs
       index 74e071bb0f..4d3b80c42f 100644
       --- a/arch/arm/src/armv7-m/Toolchain.defs
       +++ b/arch/arm/src/armv7-m/Toolchain.defs
       @@ -155,6 +155,9 @@ OBJDUMP = $(CROSSDEV)objdump
        EXTRA_LIBS += -lgcc
        EXTRA_LIBPATHS += -L "${dir ${shell $(CC) $(ARCHCPUFLAGS) 
--print-libgcc-file-name}}"
       
       +$(warning libgcc= ${shell $(CC) $(ARCHCPUFLAGS) 
--print-libgcc-file-name})
       +$(warning EXTRA_LIBPATHS=$(EXTRA_LIBPATHS))
       +
        ifneq ($(CONFIG_LIBM),y)
          EXTRA_LIBS += -lm
          EXTRA_LIBPATHS += -L "${dir ${shell $(CC) $(ARCHCPUFLAGS) 
--print-file-name=libm.a}}"
   
   Now we see: 
   
       make[1]: Entering directory 
'/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src'
       
/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/armv7-m/Toolchain.defs:158:
 libgcc= c:/program files (x86)/gnu tools arm embedded/9 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m/nofp/libgcc.a
       
/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/armv7-m/Toolchain.defs:159:
 EXTRA_LIBPATHS=-L "c:/ ./ (x86)/ ./ ./ embedded/ 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m/nofp/"
       make[2]: Entering directory 
'/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/board'
       
/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/armv7-m/Toolchain.defs:158:
 libgcc= c:/program files (x86)/gnu tools arm embedded/9 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m/nofp/libgcc.a
       
/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/armv7-m/Toolchain.defs:159:
 EXTRA_LIBPATHS=-L "c:/ ./ (x86)/ ./ ./ embedded/ 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m/nofp/"
       
/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/armv7-m/Toolchain.defs:158:
 libgcc= c:/program files (x86)/gnu tools arm embedded/9 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m/nofp/libgcc.a
       
/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/armv7-m/Toolchain.defs:159:
 EXTRA_LIBPATHS=-L "c:/ ./ (x86)/ ./ ./ embedded/ 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m/nofp/" -L "c:/ ./ 
(x86)/ ./ ./ embedded/ 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m/nofp/"
 -L "c:/ ./ (x86)/ ./ ./ embedded/ 
2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/thumb/v7e-m/nofp/"
       make[2]: 'libboard.a' is up to date.
       make[2]: Leaving directory 
'/cygdrive/d/Spuda/Documents/projects/nuttx/master/nuttx_fork/arch/arm/src/board'
       LD: nuttx
       C:\Program Files (x86)\GNU Tools ARM Embedded\9 
2019-q4-major\bin\arm-none-eabi-ld.exe: cannot find -lgcc
       C:\Program Files (x86)\GNU Tools ARM Embedded\9 
2019-q4-major\bin\arm-none-eabi-ld.exe: cannot find -lm
       make[1]: *** [Makefile:172: nuttx.exe] Error 1
   
   Proving that PR #1450 is the cause of the Cygwin build failure.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to