while trying to build wheel the code gives the following error:
running build
running build_py
running build_ext
configure: loading site script /usr/local/etc/config.site
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... x86_64-pc-msys
checking host system type... x86_64-pc-msys
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/x86_64-pc-msys/bin/ld.exe
checking if the linker (/usr/x86_64-pc-msys/bin/ld.exe) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... no, using cp -p
checking the maximum length of command line arguments... 24000
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/x86_64-pc-msys/bin/ld.exe option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... unknown
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-pc-msys/bin/ld.exe) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for native Win32... no
checking for some Win32 platform... no
checking for ANSI C header files... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking asm/page.h usability... no
checking asm/page.h presence... no
checking for asm/page.h... no
checking sys/times.h usability... yes
checking sys/times.h presence... yes
checking for sys/times.h... yes
checking for an ANSI C-conforming const... yes
checking for preprocessor stringizing operator... yes
checking size of int... 4
checking size of short... 2
checking size of void *... 8
checking size of wchar_t... 2
checking for memmove... yes
checking for memset... yes
checking for strdup... yes
checking return type of signal handlers... void
configure: creating ./config.status
config.status: creating fribidi.pc
config.status: creating lib/fribidi-config.h
config.status: creating Makefile
config.status: creating charset/Makefile
config.status: creating gen.tab/Makefile
config.status: creating lib/Makefile
config.status: creating bin/Makefile
config.status: creating doc/Makefile
config.status: creating test/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
building '_pyfribidi' extension
creating build\temp.win32-cpython-310\Release\fribidi-src
creating build\temp.win32-cpython-310\Release\fribidi-src\charset
creating build\temp.win32-cpython-310\Release\fribidi-src\lib
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\bin\HostX86\x86\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -DHAVE_CONFIG_H=1 -Ifribidi-src -Ifribidi-src/lib -Ifribidi-src/charset -Ibuild\temp.win32-cpython-310\Release\fribidi -Ibuild\temp.win32-cpython-310\Release\fribidi/lib -IC:\Lavori\vt3_git\GIT_VT3_CORE\Project\src\venv\include -IC:\Python310-32\include -IC:\Python310-32\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include" /Tcfribidi-src/charset/fribidi-char-sets-cap-rtl.c /Fobuild\temp.win32-cpython-310\Release\fribidi-src/charset/fribidi-char-sets-cap-rtl.obj
fribidi-char-sets-cap-rtl.c
fribidi-src/lib\common.h(111): fatal error C1083: Cannot open include file: 'stdlib.h': No such file or directory
error: command 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.38.33130\\bin\\HostX86\\x86\\cl.exe' failed with exit code 2
and another error is found while trying to install:
Collecting pyfribidi
Using cached pyfribidi-0.12.0.zip (788 kB)
Preparing metadata (setup.py) ... done
Requirement already satisfied: six in c:\lavori\vt3_git\git_vt3_core\project\src\venv\lib\site-packages (from pyfribidi) (1.16.0)
Building wheels for collected packages: pyfribidi
Building wheel for pyfribidi (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [71 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win32-cpython-310
copying pyfribidi.py -> build\lib.win32-cpython-310
copying pyfribidi2.py -> build\lib.win32-cpython-310
running build_ext
configure: loading site script /usr/local/etc/config.site
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... C:\Users\mattiazzi.alessandro\AppData\Local\Temp\pip-install-9z_nl7rc\pyfribidi_5fde673676f2446a93183e07ac2a2c01\fribidi-src/config.guess: unable to guess system type
This script, last modified 2008-11-15, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from
http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
and
http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD
If the version you run (C:\Users\mattiazzi.alessandro\AppData\Local\Temp\pip-install-9z_nl7rc\pyfribidi_5fde673676f2446a93183e07ac2a2c01\fribidi-src/config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.
config.guess timestamp = 2008-11-15
uname -m = x86_64
uname -r = 3.4.7.x86_64
uname -s = MSYS_NT-10.0-19045
uname -v = 2023-08-09 17:32 UTC
/usr/bin/uname -p = unknown
/bin/uname -X =
hostinfo =
/bin/universe =
/usr/bin/arch -k =
/bin/arch = x86_64
/usr/bin/oslevel =
/usr/convex/getsysinfo =
UNAME_MACHINE = x86_64
UNAME_RELEASE = 3.4.7.x86_64
UNAME_SYSTEM = MSYS_NT-10.0-19045
UNAME_VERSION = 2023-08-09 17:32 UTC
configure: error: cannot guess build type; you must specify one
building '_pyfribidi' extension
creating build\temp.win32-cpython-310\Release\fribidi-src
creating build\temp.win32-cpython-310\Release\fribidi-src\charset
creating build\temp.win32-cpython-310\Release\fribidi-src\lib
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\bin\HostX86\x86\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -DHAVE_CONFIG_H=1 -Ifribidi-src -Ifribidi-src/lib -Ifribidi-src/charset -Ibuild\temp.win32-cpython-310\Release\fribidi -Ibuild\temp.win32-cpython-310\Release\fribidi/lib -IC:\Lavori\vt3_git\GIT_VT3_CORE\Project\src\venv\include -IC:\Python310-32\include -IC:\Python310-32\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include" /Tcfribidi-src/charset/fribidi-char-sets-cap-rtl.c /Fobuild\temp.win32-cpython-310\Release\fribidi-src/charset/fribidi-char-sets-cap-rtl.obj
fribidi-char-sets-cap-rtl.c
fribidi-src/lib\common.h(36): fatal error C1083: Cannot open include file: 'config.h': No such file or directory
error: command 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.38.33130\\bin\\HostX86\\x86\\cl.exe' failed with exit code 2
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pyfribidi
Running setup.py clean for pyfribidi
Failed to build pyfribidi
ERROR: Could not build wheels for pyfribidi, which is required to install pyproject.toml-based projects
while trying to build wheel the code gives the following error:
and another error is found while trying to install: