BSP newlib building failure

Hi @ScottHu,

Hope this message find you well and good day, as we do not receive any response from you to the previous clarification that we have provided. Please post a response in the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you with your follow-up questions.

Warm Regards

Hi,

I'm still facing this problem.

Using Win10 Pro 10.0.19041

Still using QUartus 20.1 Pro ; Patch 20.1-0.49 installed

Have you any suggestions?

Best regards

Tim

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.64. Invocation command line was

$ /mnt/c/intelFPGA_pro/20.1/nios2eds/bin/gnu/src/newlib-3.1.0/configure --enable-multilib --enable-newlib-nano-malloc CFLAGS_FOR_TARGET=-g -Os -ffunction-sections -fdata-sections CXXFLAGS_FOR_TARGET=-g -Os -ffunction-sections -fdata-sections --prefix=/mnt/e/TIM/00_BAYTEK/WARP_REF/udx10_warp_ea_0.1.20210308/udx10_warp/software/vip_control_bsp/newlib --target=nios2-elf

## --------- ##
## Platform. ##
## --------- ##

hostname = DESKTOP-SCM7FSJ
uname -m = x86_64
uname -r = 4.4.0-19041-Microsoft
uname -s = Linux
uname -v = #488-Microsoft Mon Sep 01 13:43:00 PST 2020

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

PATH: /mnt/c/intelFPGA_pro/20.1/nios2eds/bin/gnu/H-x86_64-mingw32/bin
PATH: /mnt/c/intelFPGA_pro/20.1/nios2eds/sdk2/bin
PATH: /mnt/c/intelFPGA_pro/20.1/nios2eds/bin
PATH: /mnt/c/intelFPGA_pro/20.1/quartus/bin64
PATH: /mnt/c/intelFPGA_pro/20.1/quartus/sopc_builder/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /mnt/c/Windows/system32
PATH: /mnt/c/Windows
PATH: /mnt/c/Windows/System32/Wbem
PATH: /mnt/c/Program Files/PuTTY/
PATH: /mnt/c/Users/TK/AppData/Local/Microsoft/WindowsApps
PATH: /mnt/c/Users/TK/.dotnet/tools
PATH: /mnt/e/Intel/Quartus/20.4/modelsim_ae/win32aloem
PATH: /mnt/e/Intel/Quartus/20.4/modelsim_ase/win32aloem
PATH: /mnt/c/Program Files (x86)/Silicon Laboratories/ClockBuilder Pro/Bin

## ----------- ##
## Core tests. ##
## ----------- ##

configure:2320: checking build system type
configure:2334: result: x86_64-pc-linux-gnu
configure:2381: checking host system type
configure:2394: result: x86_64-pc-linux-gnu
configure:2414: checking target system type
configure:2427: result: nios2-unknown-elf
configure:2481: checking for a BSD-compatible install
configure:2549: result: /usr/bin/install -c
configure:2560: checking whether ln works
configure:2578: result: no, using cp
configure:2586: checking whether ln -s works
configure:2593: result: no, using cp -p
configure:2597: checking for a sed that does not truncate output
configure:2661: result: /bin/sed
configure:2670: checking for gawk
configure:2686: found /usr/bin/gawk
configure:2697: result: gawk
configure:4152: checking for gcc
configure:4182: result: no
configure:4245: checking for cc
configure:4292: result: no
configure:4348: checking for cl.exe
configure:4378: result: no
configure:4402: error: in `/mnt/e/TIM/00_BAYTEK/WARP_REF/udx10_warp_ea_0.1.20210308/udx10_warp/software/vip_control_bsp/newlib-build-tmp/smallc':
configure:4405: error: no acceptable C compiler found in $PATH
See `config.log' for more details.