make -v gmake -v # If make isn't the GNU version. gcc -v g++ -v ld -vNote that some distributions don't install development utilities (compilers, etc.) or packages (header files, etc.) by default.
perl -v which perl
bash --version which bash
If you're using a pre-compiled hpoj package that lacks some of these options, then please report this issue to the downstream package maintainer.
uname -a ldconfig -p | grep libusb # For Linux ldconfig -r | grep libusb # For FreeBSDIf building hpoj from source: also the libusb header files, which might be in a separate package such as libusb-devel.
ldconfig -p | grep libsnmp # For Linux ldconfig -r | grep libsnmp # For FreeBSDIf building hpoj from source: also the SNMP library header files, which might be in a separate package such as ucd-snmp-devel. In addition, if your SNMP library was built with OpenSSL support, then you may need to ensure that the OpenSSL development libraries are installed, which might be in a separate package such as openssl-devel. Look for a library symlink with the name libcrypto.so.
ldconfig -p | grep libcrypto # For Linux ldconfig -r | grep libcrypto # For FreeBSD
http://localhost:631
hpijs -h gs -h(Due to the complexity of manually installing or upgrading hpijs and configuring the print subsystem to make use of it, you might want to consider installing a distribution that includes it already. However, recent hpijs versions install the necessary PPD files to make setup of CUPS-based printing much easier.)
which scanimage which xscanimage which xsane
which mdir which mcopy
ldconfig -p | grep libqt # For Linux ldconfig -r | grep libqt # For FreeBSDIf building hpoj from source: also the QT header files and meta-object compiler, which might be in a separate package such as qt-devel.
which moc
Try the following commands to determessary, and re-run ldconfig to make your changes take effect.
As an alternative to modifying /etc/ld.so.conf, you can set the environment variable LD_LIBRARY_PATH to /usr/local/lib (or wherever the libraries were installed) before running any of the hpoj programs that depend on libptal.so.
If you install the hpoj software into separate unique directories for different versions (such as /opt/hpoj-0.90, etc.), then you should also check /etc/ld.so.conf and remove lines that point to old hpoj versions. However, be careful not to delete the line for the current version, or any line specifying a path containing other libraries on your system that you want to continue to be accessible. Run ldconfig (again, as root) to make your changes to this file take effect.