mirror of
https://github.com/Ponce/slackbuilds
synced 2024-11-20 19:41:34 +01:00
684c94b762
modified: academic/GMT/GMT.info modified: academic/arpack/arpack.info modified: academic/ngspice/ngspice.info modified: desktop/enlightenment/enlightenment.info modified: development/gprolog/gprolog.info modified: development/pycrypto/pycrypto.info modified: graphics/unpaper/unpaper.info modified: libraries/gtk-qt-engine/gtk-qt-engine.info modified: libraries/p4api/p4api.info modified: network/centerim/centerim.info modified: network/lurc/lurc.info modified: network/nethogs/nethogs.info modified: network/psi/psi.info modified: network/wireshark/wireshark.info modified: office/go_openoffice/go_openoffice.info modified: system/dosemu/dosemu.info modified: system/mbr/mbr.info modified: system/wine/wine.info Thanks to slakmagik. Signed-off-by: Robby Workman <rworkman@slackbuilds.org> |
||
---|---|---|
.. | ||
gprolog.info | ||
gprolog.SlackBuild | ||
README | ||
slack-desc |
The gprolog configure script appears to ignore the exec-prefix information handed to it which indicates where compiled binaries should be installed. It insists on installing everything into /usr/gprolog-$VERSION/ and then creating symlinks in /usr/bin. This script will correct this by moving the files in /usr/gprolog-$VERSION to their proper places in /usr, ie: binaries are placed in /usr/bin, libraries in /usr/lib or /usr/lib64 and documentation in /usr/doc/gprolog-$VERSION.