Fast-Poisson-Image-Editing icon indicating copy to clipboard operation
Fast-Poisson-Image-Editing copied to clipboard

fpie failed building in windows 11 / python 3.10.6

Open francoisbonnard opened this issue 3 years ago • 12 comments
trafficstars

Hello

Here are my logs from anaconda virutal env terminal :

pip install vie

Here is the log

(sd-inf) C:\Users\B\Desktop\stablediffusion\stablediffusion-infinity>pip install fpie Collecting fpie Using cached fpie-0.2.4.tar.gz (29 kB) Preparing metadata (setup.py) ... done Requirement already satisfied: cmake>=3.4 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from fpie) (3.24.1.1) Requirement already satisfied: opencv-python-headless>=4.2 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from fpie) (4.6.0.66) Requirement already satisfied: numpy>=1.18 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from fpie) (1.23.3) Requirement already satisfied: taichi>=1.0 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from fpie) (1.1.3) Requirement already satisfied: numba>=0.51 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from fpie) (0.56.3) Requirement already satisfied: llvmlite<0.40,>=0.39.0dev0 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from numba>=0.51->fpie) (0.39.1) Requirement already satisfied: setuptools in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from numba>=0.51->fpie) (63.4.1) Requirement already satisfied: sourceinspect>=0.0.4 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from taichi>=1.0->fpie) (0.0.4) Requirement already satisfied: colorama in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from taichi>=1.0->fpie) (0.4.5) Requirement already satisfied: rich in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from taichi>=1.0->fpie) (12.6.0) Requirement already satisfied: dill in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from sourceinspect>=0.0.4->taichi>=1.0->fpie) (0.3.5.1) Requirement already satisfied: commonmark<0.10.0,>=0.9.0 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from rich->taichi>=1.0->fpie) (0.9.1) Requirement already satisfied: pygments<3.0.0,>=2.6.0 in c:\users\b\anaconda3\envs\sd-inf\lib\site-packages (from rich->taichi>=1.0->fpie) (2.13.0) Building wheels for collected packages: fpie Building wheel for fpie (setup.py) ... error error: subprocess-exited-with-error

× python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [62 lines of output] running bdist_wheel running build running build_py creating build creating build\lib.win-amd64-cpython-310 creating build\lib.win-amd64-cpython-310\fpie copying fpie\args.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\cli.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\gui.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\io.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\np_solver.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\numba_solver.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\process.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\taichi_solver.py -> build\lib.win-amd64-cpython-310\fpie copying fpie_init_.py -> build\lib.win-amd64-cpython-310\fpie running build_ext -- Building for: Visual Studio 16 2019 -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19044. -- The C compiler identification is MSVC 19.29.30146.0 -- The CXX compiler identification is MSVC 19.29.30146.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.36.0.windows.1") -- downloading/updating pybind11 -- pybind11 directory not found, cloning... Cloning into 'C:/Users/B/AppData/Local/Temp/pip-install-5bykcwlg/fpie_1af82193c262414a803966f640d8358b/pybind11'... -- Switched to a new branch 'stable' -- branch 'stable' set up to track 'origin/stable'.

  -- pybind11 v2.10.0
  -- Found PythonInterp: C:/Users/B/anaconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3.6")
  -- Found PythonLibs: C:/Users/B/anaconda3/envs/sd-inf/libs/python310.lib
  -- Performing Test HAS_MSVC_GL_LTCG
  -- Performing Test HAS_MSVC_GL_LTCG - Success
  -- Found OpenMP_C: -openmp (found version "2.0")
  -- Found OpenMP_CXX: -openmp (found version "2.0")
  -- Found OpenMP: TRUE (found version "2.0")
  -- Could NOT find MPI_C (missing: MPI_C_LIB_NAMES MPI_C_HEADER_DIR MPI_C_WORKS)
  -- Could NOT find MPI_CXX (missing: MPI_CXX_LIB_NAMES MPI_CXX_HEADER_DIR MPI_CXX_WORKS)
  -- Could NOT find MPI (missing: MPI_C_FOUND MPI_CXX_FOUND)
  -- Found CUDA: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.7 (found version "11.7")
  -- The CUDA compiler identification is NVIDIA 11.7.99
  -- Detecting CUDA compiler ABI info
  -- Detecting CUDA compiler ABI info - done
  -- Check for working CUDA compiler: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.7/bin/nvcc.exe - skipped
  -- Detecting CUDA compile features
  -- Detecting CUDA compile features - done
  -- Found PythonInterp: C:/Users/B/anaconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3")
  -- Found PythonLibs: C:/Users/B/anaconda3/envs/sd-inf/libs/python310.lib (found suitable version "3.10.6", minimum required is "3.10")
  -- Configuring done
  -- Generating done
  -- Build files have been written to: C:/Users/B/AppData/Local/Temp/pip-install-5bykcwlg/fpie_1af82193c262414a803966f640d8358b/build/temp.win-amd64-cpython-310/Release
  error: [WinError 2] Le fichier spécifié est introuvable
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for fpie Running setup.py clean for fpie Failed to build fpie Installing collected packages: fpie Running setup.py install for fpie ... error error: subprocess-exited-with-error

× Running setup.py install for fpie did not run successfully. │ exit code: 1 ╰─> [56 lines of output] running install C:\Users\B\anaconda3\envs\sd-inf\lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( running build running build_py creating build creating build\lib.win-amd64-cpython-310 creating build\lib.win-amd64-cpython-310\fpie copying fpie\args.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\cli.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\gui.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\io.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\np_solver.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\numba_solver.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\process.py -> build\lib.win-amd64-cpython-310\fpie copying fpie\taichi_solver.py -> build\lib.win-amd64-cpython-310\fpie copying fpie_init_.py -> build\lib.win-amd64-cpython-310\fpie running build_ext -- Building for: Visual Studio 16 2019 -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19044. -- The C compiler identification is MSVC 19.29.30146.0 -- The CXX compiler identification is MSVC 19.29.30146.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- pybind11 v2.10.0 -- Found PythonInterp: C:/Users/B/anaconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3.6") -- Found PythonLibs: C:/Users/B/anaconda3/envs/sd-inf/libs/python310.lib -- Performing Test HAS_MSVC_GL_LTCG -- Performing Test HAS_MSVC_GL_LTCG - Success -- Found OpenMP_C: -openmp (found version "2.0") -- Found OpenMP_CXX: -openmp (found version "2.0") -- Found OpenMP: TRUE (found version "2.0") -- Could NOT find MPI_C (missing: MPI_C_LIB_NAMES MPI_C_HEADER_DIR MPI_C_WORKS) -- Could NOT find MPI_CXX (missing: MPI_CXX_LIB_NAMES MPI_CXX_HEADER_DIR MPI_CXX_WORKS) -- Could NOT find MPI (missing: MPI_C_FOUND MPI_CXX_FOUND) -- Found CUDA: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.7 (found version "11.7") -- The CUDA compiler identification is NVIDIA 11.7.99 -- Detecting CUDA compiler ABI info -- Detecting CUDA compiler ABI info - done -- Check for working CUDA compiler: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.7/bin/nvcc.exe - skipped -- Detecting CUDA compile features -- Detecting CUDA compile features - done -- Found PythonInterp: C:/Users/B/anaconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3") -- Found PythonLibs: C:/Users/B/anaconda3/envs/sd-inf/libs/python310.lib (found suitable version "3.10.6", minimum required is "3.10") -- Configuring done -- Generating done -- Build files have been written to: C:/Users/B/AppData/Local/Temp/pip-install-5bykcwlg/fpie_1af82193c262414a803966f640d8358b/build/temp.win-amd64-cpython-310/Release error: [WinError 2] Le fichier spécifié est introuvable [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip. error: legacy-install-failure

× Encountered error while trying to install package. ╰─> fpie

note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.

francoisbonnard avatar Oct 21 '22 17:10 francoisbonnard

I'm getting the same issue.

(sd-inf) D:\Code\Stable-Diffusion\Fast-Poisson-Image-Editing>pip install .
Processing d:\code\stable-diffusion\fast-poisson-image-editing
  Preparing metadata (setup.py) ... done
Requirement already satisfied: cmake>=3.4 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from fpie==0.2.4) (3.24.1.1)
Requirement already satisfied: opencv-python-headless>=4.2 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from fpie==0.2.4) (4.6.0.66)
Requirement already satisfied: numpy>=1.18 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from fpie==0.2.4) (1.23.2)
Requirement already satisfied: taichi>=1.0 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from fpie==0.2.4) (1.1.3)
Requirement already satisfied: numba>=0.51 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from fpie==0.2.4) (0.56.3)
Requirement already satisfied: setuptools in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from numba>=0.51->fpie==0.2.4) (63.4.1)
Requirement already satisfied: llvmlite<0.40,>=0.39.0dev0 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from numba>=0.51->fpie==0.2.4) (0.39.1)
Requirement already satisfied: rich in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from taichi>=1.0->fpie==0.2.4) (12.6.0)
Requirement already satisfied: colorama in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from taichi>=1.0->fpie==0.2.4) (0.4.5)
Requirement already satisfied: sourceinspect>=0.0.4 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from taichi>=1.0->fpie==0.2.4) (0.0.4)
Requirement already satisfied: dill in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from sourceinspect>=0.0.4->taichi>=1.0->fpie==0.2.4) (0.3.5.1)
Requirement already satisfied: commonmark<0.10.0,>=0.9.0 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from rich->taichi>=1.0->fpie==0.2.4) (0.9.1)
Requirement already satisfied: pygments<3.0.0,>=2.6.0 in c:\users\arron\miniconda3\envs\sd-inf\lib\site-packages (from rich->taichi>=1.0->fpie==0.2.4) (2.13.0)
Building wheels for collected packages: fpie
  Building wheel for fpie (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [15 lines of output]
      running bdist_wheel
      running build
      running build_py
      running build_ext
      -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22621.
      -- pybind11 v2.10.0
      -- Found PythonInterp: C:/Users/Arron/miniconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3.6")
      -- Could NOT find MPI_C (missing: MPI_C_LIB_NAMES MPI_C_HEADER_DIR MPI_C_WORKS)
      -- Could NOT find MPI_CXX (missing: MPI_CXX_LIB_NAMES MPI_CXX_HEADER_DIR MPI_CXX_WORKS)
      -- Could NOT find MPI (missing: MPI_C_FOUND MPI_CXX_FOUND)
      -- Found PythonInterp: C:/Users/Arron/miniconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3")
      -- Configuring done
      -- Generating done
      -- Build files have been written to: D:/Code/Stable-Diffusion/Fast-Poisson-Image-Editing/build/temp.win-amd64-cpython-310/Release
      error: [WinError 2] The system cannot find the file specified
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for fpie
  Running setup.py clean for fpie
Failed to build fpie
Installing collected packages: fpie
  Running setup.py install for fpie ... error
  error: subprocess-exited-with-error

  × Running setup.py install for fpie did not run successfully.
  │ exit code: 1
  ╰─> [56 lines of output]
      running install
      C:\Users\Arron\miniconda3\envs\sd-inf\lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build\lib.win-amd64-cpython-310
      creating build\lib.win-amd64-cpython-310\fpie
      copying fpie\args.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\cli.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\gui.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\io.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\np_solver.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\numba_solver.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\process.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\taichi_solver.py -> build\lib.win-amd64-cpython-310\fpie
      copying fpie\__init__.py -> build\lib.win-amd64-cpython-310\fpie
      running build_ext
      -- Building for: Visual Studio 17 2022
      -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22621.
      -- The C compiler identification is MSVC 19.33.31630.0
      -- The CXX compiler identification is MSVC 19.33.31630.0
      -- Detecting C compiler ABI info
      -- Detecting C compiler ABI info - done
      -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.33.31629/bin/Hostx64/x64/cl.exe - skipped
      -- Detecting C compile features
      -- Detecting C compile features - done
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.33.31629/bin/Hostx64/x64/cl.exe - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done
      -- pybind11 v2.10.0
      -- Found PythonInterp: C:/Users/Arron/miniconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3.6")
      -- Found PythonLibs: C:/Users/Arron/miniconda3/envs/sd-inf/libs/python310.lib
      -- Performing Test HAS_MSVC_GL_LTCG
      -- Performing Test HAS_MSVC_GL_LTCG - Success
      -- Found OpenMP_C: -openmp (found version "2.0")
      -- Found OpenMP_CXX: -openmp (found version "2.0")
      -- Found OpenMP: TRUE (found version "2.0")
      -- Could NOT find MPI_C (missing: MPI_C_LIB_NAMES MPI_C_HEADER_DIR MPI_C_WORKS)
      -- Could NOT find MPI_CXX (missing: MPI_CXX_LIB_NAMES MPI_CXX_HEADER_DIR MPI_CXX_WORKS)
      -- Could NOT find MPI (missing: MPI_C_FOUND MPI_CXX_FOUND)
      -- Found CUDA: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.8 (found version "11.8")
      -- The CUDA compiler identification is NVIDIA 11.8.89
      -- Detecting CUDA compiler ABI info
      -- Detecting CUDA compiler ABI info - done
      -- Check for working CUDA compiler: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.8/bin/nvcc.exe - skipped
      -- Detecting CUDA compile features
      -- Detecting CUDA compile features - done
      -- Found PythonInterp: C:/Users/Arron/miniconda3/envs/sd-inf/python.exe (found suitable version "3.10.6", minimum required is "3")
      -- Found PythonLibs: C:/Users/Arron/miniconda3/envs/sd-inf/libs/python310.lib (found suitable version "3.10.6", minimum required is "3.10")
      -- Configuring done
      -- Generating done
      -- Build files have been written to: D:/Code/Stable-Diffusion/Fast-Poisson-Image-Editing/build/temp.win-amd64-cpython-310/Release
      error: [WinError 2] The system cannot find the file specified
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> fpie

note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.`

If I look in the CMakeError.log file I see

D:\Code\Stable-Diffusion\Fast-Poisson-Image-Editing\build\temp.win-amd64-cpython-310\Release\CMakeFiles\FindMPI\test_mpi.cpp(1,10): fatal error C1083: Cannot open include file: 'mpi.h': No such file or directory [D:\Code\Stable-Diffusion\Fast-Poisson-Image-Editing\build\temp.win-amd64-cpython-310\Release\CMakeFiles\CMakeTmp\cmTC_99397.vcxproj]

Arron17 avatar Oct 23 '22 17:10 Arron17

I was able to resolve the issue by uninstalling Visual Studio. I don't really understand why this is happening, but it seems like when Visual Studio is installed it tries to use the Visual Studio compliers and stops it from working properly.

Arron17 avatar Oct 23 '22 20:10 Arron17

Same issue I am having

ManyStrongWords avatar Oct 26 '22 02:10 ManyStrongWords

same here

KermitTheHog avatar Nov 05 '22 22:11 KermitTheHog

Please use pip install git+https://github.com/Trinkle23897/Fast-Poisson-Image-Editing.git

Trinkle23897 avatar Nov 07 '22 04:11 Trinkle23897

Please use pip install git+https://github.com/Trinkle23897/Fast-Poisson-Image-Editing.git

I got a warning about PY_DEBUG being unset but I'm on Windows so not the first time I've seen that from pip. This successfully installed fpie-0.2.4 for me, thank you!!

KermitTheHog avatar Nov 07 '22 15:11 KermitTheHog

Please use pip install git+https://github.com/Trinkle23897/Fast-Poisson-Image-Editing.git

i install fipe,and run fpie --check-backend output: ['numpy', 'numba', 'taichi-cpu', 'taichi-gpu'], not yours examples output, it's ok? it's mean not use cuda ?? ['numpy', 'numba', 'taichi-cpu', 'taichi-gpu', 'gcc', 'openmp', 'mpi', 'cuda']

zhanghongyong123456 avatar Nov 22 '22 06:11 zhanghongyong123456

It means either cmake or cuda library is not installed on your own computer, or there's something wrong with compilation. I think it's cmake/gcc issue in your case because none of the last four are available.

Trinkle23897 avatar Nov 22 '22 19:11 Trinkle23897

It means either cmake or cuda library is not installed on your own computer, or there's something wrong with compilation. I think it's cmake/gcc issue in your case because none of the last four are available.

i install on windows,so gcc will not appear, but what else is needed to get the installation done

zhanghongyong123456 avatar Nov 23 '22 01:11 zhanghongyong123456

cuda/openmp/mpi are all based on gcc

Trinkle23897 avatar Nov 23 '22 04:11 Trinkle23897

cuda/openmp/mpi are all based on gcc

ok,mean only linux can use cuda/openmp/mpi

zhanghongyong123456 avatar Nov 23 '22 06:11 zhanghongyong123456

windows can also use these extensions! but you need first to uncomment try... except... in setup.py to see what happens:

-    try:
-      subprocess.check_call(
-        ["cmake", ext.sourcedir] + cmake_args, cwd=self.build_temp
-      )
-      subprocess.check_call(["make"] + build_args, cwd=self.build_temp)
-    except Exception as e:
-      print(f"{type(e)}: {e}")
-      pass
+    subprocess.check_call(
+      ["cmake", ext.sourcedir] + cmake_args, cwd=self.build_temp
+    )
+    subprocess.check_call(["make"] + build_args, cwd=self.build_temp)

Trinkle23897 avatar Nov 23 '22 16:11 Trinkle23897