[SOLVED] make[1]: Nothing to be done for `all-am' problem while using make

SkyerSK · 01-08-2011, 03:30 AM

Hello,
I've been trying to install several different programs in time, but in some of them, while running make (or sudo make), I get errors similar to: (this one was while installing chmlib)

Code:

Making all in src
make[1]: Entering directory `/home/user/Desktop/chmlib-0.40/src'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/user/Desktop/chmlib-0.40/src'
make[1]: Entering directory `/home/user/Desktop/chmlib-0.40'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/home/user/Desktop/chmlib-0.40'

Could you please tell me how can I solve this, or where is the problem? Thanks.

markush · 01-08-2011, 03:52 AM

Hello,

this are no errormessages. Didn't the programs compile/install correctly?

Markus

knudfl · 01-08-2011, 05:32 AM

'chmlib-0.40' : When you run 'make', everything is compiled in two seconds.

? May be you didn't notice, what happened, and did 'make' another time.
Which is the only way, you will get the "information / message" :
"" make[1]: Nothing to be done for `all-am'.""

Please try : 'make clean', and then watch 'make' again.

In some other applications there are really nothing to do, when you run make.
They will also reply : 'Nothing to be done for all..' or similar.

..

SkyerSK · 01-08-2011, 07:48 AM

Markush: I am not sure, that's the thing. It first happened to me when I was installing alsa-oss, and these audio things are kinda buggy for me, because I am using older motherboard now. So I am not sure....
Knudfl: Ok, did it. It looks like it compiler everything right, except the "default" (where is my current path) directory, which again, gives me "Nothing to do" error. I guess it's done correct then, or not?

Thanks for your answers.

knudfl · 01-08-2011, 01:02 PM

Quote:

except the "default"

Please explain, what it means.

Quote:

(where is my current path) directory

I also do not understand, what you mean with this.

..

SkyerSK · 01-08-2011, 02:44 PM

Knudfl: I am sorry for my English, I am not nationally speaking it. So, by "default" directory or current path I mean current working (active) directory, the one, which is the result of using pwd command. hope it's better

knudfl · 01-08-2011, 03:20 PM

If the right files are present : Nothing to worry about.

'ls chmlib-0.40/src/.libs/' should reply ""chm_lib.o libchm.a libchm.la@
libchm.lai libchm.so@ libchm.so.0@ libchm.so.0.0.0* lzx.o""

There is no default location for building applications / libraries.
The most used is /home/<name>/tmp/<app>/ or similar.
Directories outside /home/<name> : Not meant for building.

A directory does not turn into "active" or "working", when you use it.
A directory is just a placeholder for some files.
( EDIT : The currently used directory ( $(pwd) ) is named "working directory".)

..

SkyerSK · 01-09-2011, 03:14 AM

eh, thanks for explanation. Also, installation seems to be successful, so problem is solved. Thanks everyone who participated.

About the directories - well, I was always told that current working directory of shell is really called current working directory. Please, take a look
on these documents (found them by google): http://www.comptechdoc.org/os/linux/..._ugbasics.html, http://tldp.org/LDP/abs/html/internal.html, search
for "current working directory.

markush · 01-09-2011, 04:53 AM

Hello SykerSK,

I'm happy to read that you've found an answer to your question, please don't forget to use the "Thread Tools" and mark this thread as "SOLVED".

Markus

SkyerSK · 01-10-2011, 09:03 AM

Oh, ok, thanks, I forgot to do so. (It's done now).