FS#39043 - [qhull] qhull headers reside in /usr/include/libqhull instead of /usr/include/qhull

Attached to Project: Arch Linux
Opened by fe rew (ferew2) - Tuesday, 25 February 2014, 17:16 GMT
Last edited by Ronald van Haren (pressh) - Monday, 03 March 2014, 10:38 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
qhull headers reside in /usr/include/libqhull while qhull docs say that ../qhull should be used

The qhull documentation states: “To access all functions, use qhull_a.h. Include the file with "#include <qhull/qhull_a.h>".” (see http://www.qhull.org/html/qh-code.htm#library)

Solution:
I suggest to symlink qhull to libqhull after installing the headers. Something along the lines of
cd $PREFIX/include/
ln -s libqhull qhull


Additional info:
* package version: 2012.1-2

Steps to reproduce:
1. install qhull
2. create test program using qhull
3. follow the advice from the docs:
To access all functions, use qhull_a.h. Include the file with "#include <qhull/qhull_a.h>".
4. the compiler complains that the file does not exist
This task depends upon

Closed by  Ronald van Haren (pressh)
Monday, 03 March 2014, 10:38 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Upstream had a bug in its own documentation.
Comment by Doug Newgard (Scimmia) - Tuesday, 25 February 2014, 17:23 GMT
They are not in /usr/local, look again.

If they're in the wrong place, it's because upstream puts them there. Looking at the PKGBUILD, it does nothing about moving the headers at all. Please report this upstream.

Maybe it's simply the documentation is out of date.
Comment by fe rew (ferew2) - Tuesday, 25 February 2014, 17:42 GMT
I totally messed that up. I mixed two issues. sorry.
Here is what I mean:
qhull headers reside in /usr/include/libqhull instead of /usr/include/qhull

and of course
cd $PREFIX/include/
ln -s libqhull qhull

the rest is valid
Comment by Doug Newgard (Scimmia) - Tuesday, 25 February 2014, 17:44 GMT
The rest is still what the upstream makefiles are doing, not the Arch packaging. So, as I said, either their build system has a bug or their documentation is wrong.
Comment by fe rew (ferew2) - Tuesday, 25 February 2014, 17:47 GMT
some other major distros place headers according to how i suggested above, so I doubt it is an upstream problem.

can you pint me to the PKGBUILD?

Can I edit the summary and description?

Sorry for the newbie questions.
Comment by Doug Newgard (Scimmia) - Tuesday, 25 February 2014, 17:52 GMT
PKGBUILD: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/qhull

As you can see, all it really does is:
cmake -DCMAKE_INSTALL_PREFIX=/usr
make
make install

So $PREFIX/include/libqhull is where upstream is putting them.
Comment by fe rew (ferew2) - Tuesday, 25 February 2014, 18:02 GMT
I see.

still. a symlink would be an easy fix (to what seems to be an upstream bug)
Is that definitely not an option?

I probably should check how other distros deal with that. It may be that they created the artefact and everybody got used to it.

thanks for considering!
thanks for your help and answers!
keep up the good work!
Comment by Doug Newgard (Scimmia) - Tuesday, 25 February 2014, 18:08 GMT
I just checked Debian, they're creating symlinks manually and specifically say "Convenience links for backwards compatibility", so the documentation is simply out of date. Please contact upstream so they can fix it.

Arch tries to keep packages as close to upstream as possible. Upstream chose not to include a symlink for backward compatibility, so it's doubtful that the Arch maintainer will add it. Even worse, there is no maintainer for this package (it's a orphan), so unless there's a serious problem, I doubt anyone will care about modifying it. I'll go ahead and assign this to the person listed as the maintainer in the PKGBUILD, but it will probably be closed as "Won't fix".
Comment by fe rew (ferew2) - Sunday, 02 March 2014, 22:14 GMT
Just to close this: the problem was resolved by updating the documentation upstream. (Thanks Brad)

/usr/include/libqhull has been the right place since 2011.

Thanks Doug for hunting down the problem.

Loading...