Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23186 - [mupdf] Missing header files and library file should be included in the package

Attached to Project: Community Packages
Opened by Uli (Army) - Tuesday, 08 March 2011, 13:23 GMT
Last edited by Brad Fanella (cesura) - Saturday, 12 March 2011, 22:57 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Brad Fanella (cesura)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
The whole discussion was started here http://aur.archlinux.org/packages.php?ID=46304 because fbpdf can't be compiled against mupdf the way it is intended. When I created the PKGBUILD for mupdf-git http://aur.archlinux.org/packages.php?ID=47196 I noticed, that the PKGBUILD of [community]'s mupdf doesn't use "make install", it only uses "make" and the files are being installed manually. In my opinion this violates the principles of Archlinux to provide packages the way they are intended upstream. Upstream wants to install
/usr/include/fitz.h
/usr/include/mupdf.h
/usr/lib/libmupdf.a
as well, which are required for fbpdf-git to build correctly and maybe other (future) packages as well.

So please use "make install" rather than all those install lines.

Installing the stuff from the debian directory is fine of course!

Additional info:
* package version(s)
# pacman -Qi mupdf | grep Version
Version : 0.8-1
* config and/or log files etc.
-

Steps to reproduce:
Install mupdf from the repos and then try to install fbpdf-git (or another affected package which I'm unaware of) with this PKGBUILD http://pastebin.com/UGZmFZDj (the up to date PKGBUILD from AUR includes a workaround, it compiles mupdf again, which isn't supposed to be necessary!). It won't work because of missing files.
Then try to compile fbpdf-git against mupdf-git, which uses "make install". Now it works.
This task depends upon

Closed by  Brad Fanella (cesura)
Saturday, 12 March 2011, 22:57 GMT
Reason for closing:  Fixed
Comment by Moritz Lipp (mlq) - Thursday, 10 March 2011, 01:35 GMT
In addition to the above I want to state that it is not possible to build a shared library and link against mupdf.a unless mupdf has been build with the -fPIC flag. It would be nice if this could be considered when dealing with the above report which I highly support.
Comment by Brad Fanella (cesura) - Friday, 11 March 2011, 03:17 GMT
@Army: Thank you for bringing this to my attention. I really apologize for this; upstream appeared to have made a mistake somewhere in the build process (or I had a corrupt copy, which is probably more likely, as your AUR package builds fine. Whatever the case may have been.), forcing me to install the executables by hand. I suppose that I neglected to install the header files along with it as well.

I have tested it ("it" being mupdf-0.8-2, now in community) out and it appears to work just fine; would you like to do the same before I close this and notify Sara of the changes?
Comment by Uli (Army) - Saturday, 12 March 2011, 15:30 GMT
Ok, I didn't test it, but Sara did and seems like it works fine. Thanks for fixing it Brad.
Comment by Brad Fanella (cesura) - Saturday, 12 March 2011, 22:57 GMT
Not a problem. Thank *you* for reporting this. :-)

Loading...