can't build 1.16.1 - fatal error: fitz.h not exist #358

alium · 2019-09-10T08:49:03Z

I want build PyMuPDF as usually i build python-packages, ergo:

python setup.py build, python setup.py install --root="$pkgdir" --optimize=1

but i can build that, because fitz.h missing

log:
running build
running build_py
running build_ext
building 'fitz._fitz' extension
swigging fitz/fitz.i to fitz/fitz_wrap.c
swig -python -o fitz/fitz_wrap.c fitz/fitz.i
creating build
creating build/temp.linux-x86_64-3.7
creating build/temp.linux-x86_64-3.7/fitz
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -march=x86-64 -mtune=generic -O3 -pipe -fstack-protector-strong -fno-plt -march=x86-64 -mtune=generic -O3 -pipe -fstack-protector-strong -fno-plt -march=x86-64 -mtune=generic -O3 -pipe -fstack-protector-strong -fno-plt -march=haswell -mtune=haswell -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/mupdf -I/usr/local/include/mupdf -I/usr/include/python3.7m -c fitz/fitz_wrap.c -o build/temp.linux-x86_64-3.7/fitz/fitz_wrap.o
fitz/fitz_wrap.c:2732:10: fatal error: fitz.h: directory or file does not exist
2732 | #include <fitz.h>
| ^~~~~~~~
compilation terminated.
error: command 'gcc' failed with exit status 1

1.16.1 and 1.14.18 tested and both are affected...

maybe stupid question, but i found no solution....

JorjMcKie · 2019-09-10T10:09:42Z

Have you read the installation documentation of the manual and the hints on the homepage of the repo?

Downloaded & installed MuPDF from their download (!) site?
Downloaded PyMuPDF source from PyPI?
Copied the _config.h from the fitz folder of the repo to the downloaded MuPDF folder replacing config.h (without underscore) there?
Generated MuPDF after all the previous steps?
Adjusted any folder names in setup.py?

Your error means that the MuPDF source is not accessible - a clear sign that you missed one or more of the previous steps: fitz.h is contained in mupdf/include/mupdf, which therefore must be missing in your setup.py.

alium · 2019-09-10T12:00:51Z

pretty stupid installation :-D

emacs18 · 2019-12-22T17:04:14Z

I ran into the same error on a freshly installed CentOS 8 while running

pip3 install --user pymudpf

Prior to this following completed successfully:

sudo yum install python3-qt5-devel.x86_64
pip3 install --user dbus-python python-xlib pyqt5 pyqtwebengine grip qrcode feedparser

Must I build pymudpdf from source and not using pip3?
I don't even know what pymupdf is. I'm just trying to follow instructions at
https://github.com/manateelazycat/emacs-application-framework
ie., pymupdf is just one of many preprequisites.

JorjMcKie · 2019-12-22T20:22:07Z

Must I build pymudpdf from source and not using pip3?
I don't even know what pymupdf is. I'm just trying to follow instructions at
https://github.com/manateelazycat/emacs-application-framework
ie., pymupdf is just one of many preprequisites.

PyMuPDF is a package to access PDF and many other document types (XPS, EPUB, ...) from Python.
I am not familiar with CentOS, but obviously it is not one of the OS upported by the wheels I am offering on PyPI. I am a little surprised, that this Linux type wouldn't be among the ones supported by the platform tag manylinux2010. If you know what you are doing, you can even unzip the right wheel version an manually copy those 5 files to your dist or site packages ... There are also tools to convert wheels back to an egg format, which is certainly cleaner (https://github.com/dairiki/humpty). This in the hope, that the egg install will be less picky that pip.
In that case one must install from sources. As such not a big deal (and you can use pip3 for it), but before this, the base library MuPDF must be installed. This is explained on the homepage and more dilligently in the PyMuPDF documentation.

emacs18 · 2019-12-23T15:33:43Z

Thank you for your reply.
I will try to build this from source.
The only reason why I bother with CentOS is that it is used in my day job.
Compared with ubuntu, centos seems like it is from dinosaur age as far as basic user experience goes.
I can't see why anyone would choose to use this for personal use.

chenghaitao · 2020-08-28T10:42:41Z

$ pip3 install --upgrade pip
Collecting pip
Downloading https://files.pythonhosted.org/packages/5a/4a/39400ff9b36e719bdf8f31c99fe1fa7842a42fa77432e584f707a5080063/pip-20.2.2-py2.py3-none-any.whl (1.5MB)
100% |████████████████████████████████| 1.5MB 408kB/s
Installing collected packages: pip
Successfully installed pip-20.2.2

susuusus · 2020-11-18T10:48:18Z

Hi @JorjMcKie , correct me if I am wrong .Once I installed pymupdf, mupdf should get automatically downloaded in window and linux, but why I still encounter the issue that fitz.h not found

JorjMcKie · 2020-11-18T12:49:37Z

Once I installed pymupdf, mupdf should get automatically downloaded in window and linux

No, this won't (and should not!) happen automatically. You must download and install MuPDF as a separate step prior to generating PyMuPDF from source.

susuusus · 2020-11-18T13:01:26Z

Thanks for the prompt reply. But I am able to use pymupdf in local drive which is window without downloading mupdf in advance. But once I put it on cloud, it fails.

…

On Wed, 18 Nov 2020 at 8:49 PM, Jorj X. McKie ***@***.***> wrote: Once I installed pymupdf, mupdf should get automatically downloaded in window and linux No, this won't happen automatically. You must download and install MuPDF as a separate step prior to generating PyMuPDF from source. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#358 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGZLK3YQDWAUS4VDNPHHQEDSQO7HDANCNFSM4IVEZA2Q> .

JorjMcKie · 2020-11-18T13:11:02Z

I have seen a similar problem earlier here: #430. Maybe you can get ideas from that discussion. Jorj Von: susuusus<mailto:[email protected]> Gesendet: Mittwoch, 18. November 2020 09:01 An: pymupdf/PyMuPDF<mailto:[email protected]> Cc: Jorj X. McKie<mailto:[email protected]>; Mention<mailto:[email protected]> Betreff: Re: [pymupdf/PyMuPDF] can't build 1.16.1 - fatal error: fitz.h not exist (#358) Thanks for the prompt reply. But I am able to use pymupdf in local drive which is window without downloading mupdf in advance. But once I put it on cloud, it fails.

On Wed, 18 Nov 2020 at 8:49 PM, Jorj X. McKie ***@***.***> wrote: Once I installed pymupdf, mupdf should get automatically downloaded in window and linux No, this won't happen automatically. You must download and install MuPDF as a separate step prior to generating PyMuPDF from source. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#358 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGZLK3YQDWAUS4VDNPHHQEDSQO7HDANCNFSM4IVEZA2Q> .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#358 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB7IDIUSXAWX6NTLF27KRNTSQPATNANCNFSM4IVEZA2Q>.

denyu95 · 2020-12-01T05:55:00Z

Maybe you need to upgrade pip first

pip3 install --upgrade pip
pip3 install PyMuPDF
Good luck

hammady · 2021-05-02T18:18:32Z

For anyone trying to install mupdf on Apple's M1 or any arm based architecture, there is no binary available for arm and pip will try to build from source. Until the maintainers here provide system requirements to install before pip, this will always fail.

sailist · 2021-10-30T07:04:08Z

my m1 solution:

brew install mupdf
pip3 install PyMuPDF

NixBiks · 2022-01-25T10:21:46Z

my m1 solution:

brew install mupdf
pip3 install PyMuPDF

@sailist Have you been able to install pymupdf in a docker container (e.g. based on python:3.8-bullseye) on your M1 machine? I keep getting the following error

  gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/usr/include/mupdf -I/usr/local/include/mupdf -Imupdf/thirdparty/freetype/include -I/usr/include/freetype2 -I/opt/pysetup/.venv/include -I/usr/local/include/python3.8 -c fitz/fitz_wrap.c -o build/temp.linux-aarch64-3.8/fitz/fitz_wrap.o
  fitz/fitz_wrap.c:2755:10: fatal error: fitz.h: No such file or directory
   2755 | #include <fitz.h>
        |          ^~~~~~~~
  compilation terminated.
  error: command 'gcc' failed with exit status 1

lucasfonsecads · 2022-01-28T15:33:02Z

@mr-bjerre In the case of Docker, you need to check if your image is using an image that is not based on the M1 architecture, so you won't have any problems installing packages that don't work on M1.

NixBiks · 2022-01-28T15:37:03Z

I solved it. See my solution here

charanjit-singh · 2022-04-04T14:27:53Z

on MBPro M1
After running
brew install mupdf
I am getting
fatal error: 'ft2build.h' file not found

V-Holodov · 2022-04-04T17:19:56Z

@charanjit-singh On an ARM M1 Mac, with native homebrew & pip in place, these steps should work (the second step being replaced by pip install pymupdf as soon as the referenced PR reach PyPI):

brew install mupdf swig
pip install https://github.com/pymupdf/PyMuPDF/archive/master.tar.gz

#875

mojo-anand · 2022-05-23T04:04:23Z

on Mac M1, I was getting:
fatal error: 'ft2build.h' file not found
had to additionally do:
brew install freetype

ZaXk · 2022-06-27T08:05:20Z

My solution(for alpine 3.16):
apk add
mupdf-dev
gcc
make
libc-dev
musl-dev
jbig2dec
openjpeg-dev
jpeg-dev
harfbuzz-dev
swig

ln -s /usr/lib/libjbig2dec.so.0 /usr/lib/libjbig2dec.so

python -m pip install --upgrade pip
python -m pip install --upgrade pymupdf

alium added the bug label Sep 10, 2019

alium assigned JorjMcKie Sep 10, 2019

alium closed this as completed Sep 10, 2019

cbm755 mentioned this issue Nov 12, 2019

Linux wheel platform tag "manylinux2010" requires pip 19.0 or greater #400

Closed

This was referenced Dec 9, 2020

pip install fails when installing pymupdf on macOS Big Sur lucasrla/remarks#7

Closed

Question / Comment: How to ensure 1.17.4 installs through dependency on macOS 11.1, properly? #758

Closed

RecNes mentioned this issue Jun 9, 2021

Installation failing while build. #1086

Closed

Lucas-C mentioned this issue Jul 15, 2021

Feature Request: Allow "FPDF.add_font" to accept a bytes/buffer object py-pdf/fpdf2#172

Closed

NixBiks mentioned this issue Jan 27, 2022

Support building docker image from M1 Mac #1562

Closed

puhao7117441 mentioned this issue Oct 14, 2022

安装paddleocr时出现错误：PyMuPDF无法安装 PaddlePaddle/PaddleOCR#7934

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

can't build 1.16.1 - fatal error: fitz.h not exist #358

can't build 1.16.1 - fatal error: fitz.h not exist #358

alium commented Sep 10, 2019

JorjMcKie commented Sep 10, 2019

alium commented Sep 10, 2019

emacs18 commented Dec 22, 2019 •

edited

Loading

JorjMcKie commented Dec 22, 2019

emacs18 commented Dec 23, 2019

chenghaitao commented Aug 28, 2020

susuusus commented Nov 18, 2020

JorjMcKie commented Nov 18, 2020 •

edited

Loading

susuusus commented Nov 18, 2020 via email

JorjMcKie commented Nov 18, 2020 via email

denyu95 commented Dec 1, 2020

hammady commented May 2, 2021

sailist commented Oct 30, 2021

NixBiks commented Jan 25, 2022 •

edited

Loading

lucasfonsecads commented Jan 28, 2022

NixBiks commented Jan 28, 2022

charanjit-singh commented Apr 4, 2022 •

edited

Loading

V-Holodov commented Apr 4, 2022 •

edited

Loading

mojo-anand commented May 23, 2022 •

edited

Loading

ZaXk commented Jun 27, 2022 •

edited

Loading

can't build 1.16.1 - fatal error: fitz.h not exist #358

can't build 1.16.1 - fatal error: fitz.h not exist #358

Comments

alium commented Sep 10, 2019

JorjMcKie commented Sep 10, 2019

alium commented Sep 10, 2019

emacs18 commented Dec 22, 2019 • edited Loading

JorjMcKie commented Dec 22, 2019

emacs18 commented Dec 23, 2019

chenghaitao commented Aug 28, 2020

susuusus commented Nov 18, 2020

JorjMcKie commented Nov 18, 2020 • edited Loading

susuusus commented Nov 18, 2020 via email

JorjMcKie commented Nov 18, 2020 via email

denyu95 commented Dec 1, 2020

hammady commented May 2, 2021

sailist commented Oct 30, 2021

NixBiks commented Jan 25, 2022 • edited Loading

lucasfonsecads commented Jan 28, 2022

NixBiks commented Jan 28, 2022

charanjit-singh commented Apr 4, 2022 • edited Loading

V-Holodov commented Apr 4, 2022 • edited Loading

mojo-anand commented May 23, 2022 • edited Loading

ZaXk commented Jun 27, 2022 • edited Loading

emacs18 commented Dec 22, 2019 •

edited

Loading

JorjMcKie commented Nov 18, 2020 •

edited

Loading

NixBiks commented Jan 25, 2022 •

edited

Loading

charanjit-singh commented Apr 4, 2022 •

edited

Loading

V-Holodov commented Apr 4, 2022 •

edited

Loading

mojo-anand commented May 23, 2022 •

edited

Loading

ZaXk commented Jun 27, 2022 •

edited

Loading