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
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.
Try the following commands to determine if a version of hpoj is already installed on your system:
which ptal-connect /sbin/ldconfig -p | grep ptal # For Linux /sbin/ldconfig -r | grep ptal # For FreeBSDIf hpoj is not already installed as indicated by the above commands, then you can skip to the next section below to install it for the first time.
Check the list of known distribution versions that provide hpoj packages for the package name(s) that you should look for on your system. For example, on an RPM-based distribution you might be able to use commands such as the following:
rpm -qa | grep hpoj rpm -qa | grep ptal rpm -qa | grep -i officejetOr on an APT-based distribution such as Debian:
dpkg -l|grep hpojIf the desired components of the desired (current) version are already installed on your system, then you can likely skip to the next step of setting up basic device connectivity.
Important: If an old hpoj version is already installed, then be sure to do one of the following to prevent subsequent problems:
If you haven't already, issue one of the following commands to extract the source code from the hpoj-0.XX.tgz "tarball" file (the exact name depends on the version):
tar xvfz hpoj-0.XX.tgz # For GNU tar zcat hpoj-0.XX.tgz | tar xvf - # For non-GNU tarcd into the source-code directory that was created and enter the following commands at the shell prompt:
./configure # Watch closely for missing dependencies. make # Use "gmake" instead for FreeBSD. su # When prompted, enter the root password. make install # Watch closely for post-installation steps.By default, the hpoj software is installed under /usr/local, and the HTML documentation you're reading right now is installed under /usr/local/share/doc/hpoj (a different documentation path from version 0.8). If on the other hand your copy of hpoj is installed under /usr, then you can find the documentation under /usr/share/doc/hpoj. (However, if you're using a precompiled hpoj package from a distribution vendor, the downstream package maintainer may have elected to place the documentation files somewhere else.)
Important: Watch the "make install" step above closely for
any error messages that might indicate problems in automatically performing
certain operations. If you see any such error messages, then refer to the
Post-installation steps section,
especially if any error messages appear about "setting ptal-init to
start at bootup".
Caution: If ptal-init does not get started before the print spooler at boot time, then you run the risk of hanging your boot sequence.
Finally, you may need to log out and back in again to make changes to the PATH environment variable take effect.