How do I track down compiling problems ?

Using applications, configuring, problems
Post Reply
Message
Author
User avatar
Billwho?
Posts: 559
Joined: Tue 06 Dec 2005, 09:28
Location: still "In The Dog House" East Coast Oz
Trialing 4.20

How do I track down compiling problems ?

#1 Post by Billwho? »

I have been trying to compile the HPLIP printer/scanner driver in Puppy 1.0.8rc1 live cd. I have usrdevx on my home partition beside my pupxxx file.

When I run the "Configure" command I get no error mesages.

When I run the "make" command I still get no error messages

But when I run the "make install" comand I get the following error messages.

Code: Select all

Usage: /etc/init.d/hplip {start|stop|status|restart|condrestart}
make[3]: *** [install-data-hook] Error 1
make[3]: Leaving directory `/mnt/pupxxx/hplip/hplip-0.9.8'
make[2]: *** [install-data-am] Error 2
make[2]: Leaving directory `/mnt/pupxxx/hplip/hplip-0.9.8'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/mnt/pupxxx/hplip/hplip-0.9.8'
make: *** [install-recursive] Error 1
My question is not what have I done wrong ( I know there is not anywhere enough information here to answer that question )
My question is where do I look and what should I be looking for to work out what has gone wrong.
Linux = Learning through doing :shock: :? :D
The learning curve may be steep but there is a light at the end of the tunnel.
You just have to pass the occasional oncoming train to get there.

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

Re: How do I track down compiling problems ?

#2 Post by rarsa »

Billwho? wrote:But when I run the "make install" comand I get the following error messages.

Code: Select all

Usage: /etc/init.d/hplip {start|stop|status|restart|condrestart}
I think that the clue is in this line (It's usually the first error that you care about)

I think that the 'make install' is trying to execute hplip but it's not passing the right parameter.

Check if you can find hplip under /etc/init.d. and let us know.

Maybe hplip is already installed, try executing it manually giving the full path and the start parameter.

One thing to consider is that puppy does not use /etc/init.d. In some distros the scripts under init.d get executed at startup. In puppy, if you want hplip to start at boot time you must add the start command to /etc/rc.d/rc.local.

Let us know how it goes.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to

muggins
Posts: 6724
Joined: Fri 20 Jan 2006, 10:44
Location: hobart

#3 Post by muggins »

billwho?,

what about hplip 0.9.4 from linuxpackages.net here:

http://www.linuxpackages.net/search_vie ... p&ver=10.1

i'm not at my 'puter at moment, so can't check, but i suspect it's already compiled for slack environment.

User avatar
MU
Posts: 13649
Joined: Wed 24 Aug 2005, 16:52
Location: Karlsruhe, Germany
Contact:

#4 Post by MU »

try to create the folder /etc/init.d before running make install.

**edit** no forget it, it seems it was created, sorry for reading wrong.
Mark

User avatar
Billwho?
Posts: 559
Joined: Tue 06 Dec 2005, 09:28
Location: still "In The Dog House" East Coast Oz
Trialing 4.20

#5 Post by Billwho? »

Thanks for the quick replies.
what about hplip 0.9.4 from linuxpackages.net here:
Once I worked out why some of the packages I dowloaded from Linuxpackages didn't work I tried their hplip 0.9.4 package. Unfortunately it wanted snmp which I downloaded and installed. It then wanted the snmp libraries, downloaded and installed what I thought was all of them but seem to have missed one which I cant find. :( On top of which I dont need this feature once I can get hplip to install ( its for networking and this is a stand alone machine).
try to create the folder /etc/init.d before running make install.
Already doing that. At one stage I got make install to run with no errors at all. But when I ran

Code: Select all

/etc/init.d/hplip restart
I got

Code: Select all

no such file or directory
and when I investigated further I found that the directory did not exist.

Now when I restart I get

Code: Select all

# /etc/init.d/hplip restart
Stopping hpiod:                                            [  OK  ]
Stopping hpssd:                                            [  OK  ]
Starting hpiod:                                            [  OK  ]
Starting hpssd:                                            [FAILED]
# 
Linux = Learning through doing :shock: :? :D
The learning curve may be steep but there is a light at the end of the tunnel.
You just have to pass the occasional oncoming train to get there.

Post Reply