HPLIP 2.8.7 error: 'make' command failed with status code 2

run ./configure
and paste here the log

Daniel,

Thanks. But I've since started over and re-installed Ubuntu 8.04, and all is well now. I've always preferred Ubuntu, but 8.04 caused issued with my NVIDIA card and using dual head displays. Today i decided to try an re-tackle the problem, and got it resolved. I then installed the current HPLIP software, and the printer is working great (haven't tried scanning yet though). I think I can now finally break my dependence on Windows since the printer was the last holdout (I admit, i had to buy this one yesterday since there was no hope for the Lexmark now sitting in the closet :-) )

On a side note, the printer i am now using is an HP PhotoSmart C4580. I read somewhere in this section that this printer was not supported in 2.8.7, yet. However, using hp-setup, I was able to enter the ip address (I'm using it wirelessly) and locate it. I then selected the PPD for the C_4400 series printers. I selected this because the image of the 4400 looks identical to the c4580. I thought I would pass this one since a number of people I've talked to have this printer, love it, and would like to use it within Linux. I figured that you store this info and pass on if ever needed.

Anyway, thanks for the time to help, and I apologize for wasting your time by switching back to another distro.

so, I have the same problem now and I have an Ubuntu 8.04 hardy

this is the log from ./configure:

max@Notebook:~/Рабочий стол$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/bin/bash: /home/max/Рабочий: No such file or directory
configure: WARNING: `missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for gfortran option to produce PIC... -fPIC
checking if gfortran PIC flag -fPIC works... yes
checking if gfortran static flag -static works... yes
checking if gfortran supports -c -o file.o... yes
checking whether the gfortran linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking for pthread_create in -lpthread... yes
checking for pow in -lm... yes
checking for jpeg_set_defaults in -ljpeg... yes
checking for dlopen in -ldl... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking whether byte ordering is bigendian... no
checking for uint32_t... yes
checking "for platform-dependencies"... "using Default platform.h"
checking for documentation build... yes
checking for hpijs only build... no
checking for network build... yes
checking for parallel port build... yes
checking for scanner build... yes
checking for gui build... yes
checking for fax build... yes
checking for dbus build... yes
checking for cups 1.1.x build... no
checking for shadow build... no
checking for foomatic ppd install... no
checking for foomatic drv install... yes
checking for foomatic-rip-hplip install... yes
checking for qt4... no
checking for qt3... yes
checking for restricted build... grep: bb_build.inc: No such file or directory
no
checking for host machine platform... x86_32
checking for CRYPTO_free in -lcrypto... yes
checking for snmp_timeout in -lnetsnmp... yes
checking net-snmp/net-snmp-config.h usability... yes
checking net-snmp/net-snmp-config.h presence... yes
checking for net-snmp/net-snmp-config.h... yes
checking linux/ppdev.h usability... yes
checking linux/ppdev.h presence... yes
checking for linux/ppdev.h... yes
checking for cupsDoFileRequest in -lcups... yes
checking cups/cups.h usability... yes
checking cups/cups.h presence... yes
checking for cups/cups.h... yes
checking for usb_init in -lusb... yes
checking usb.h usability... yes
checking usb.h presence... yes
checking for usb.h... yes
checking for a Python interpreter with version >= 2.2... python
checking for python... /usr/bin/python
checking for python version... 2.5
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.5/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages
checking for path to Python.h... "using /usr/include/python2.5"
checking python2.5/Python.h usability... yes
checking python2.5/Python.h presence... yes
checking for python2.5/Python.h... yes
checking for sane_open in -lsane... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DBUS... yes
checking for dbus_connection_open in -ldbus-1... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating hplip.conf
config.status: creating hplip.desktop
config.status: creating hplip-systray.desktop
config.status: creating prnt/drv/hpijs.drv
config.status: creating hplip.list
config.status: executing depfiles commands

I think I has just solved this problem by changing directory of the file - I put it into my home directory

Ah, solution (for me)...

By looking into the logfile, I detected that one part of the make processes tried to find a file, which another part created before... while reading carefully, I detected that the file was present, but,.... *drums*... my path contained something like this "......../HP Officejet J45....", yes, and the log file said something like ".... J45..."...

So, we have a simple "developer-forgot-to-escape-the-pathname-to-avoid-problems-with-spaces-error".

So, put your hplib in a path that does not contain any spaces, start the whole make/installation process and you feel well...

(Another helper to find it was the fact that I just installed the same software on another machine just 5 minutes earlier....)

So, bye
Sven

Thanks...

I've just went through the same trouble on Ubuntu 8.04. Turned out I'd stopped having this same "code 2" message only after moving the .sh file to a directory without spaces on the folder name. Go figure. :-p

automake uses libtool, this issue is happening while automake form commands for libtool.

This is a known issue from GNU libtool.This defect need to fix from libtool side.

Thank you!
Naga Samrat Chowdary, Narla.