Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have encountered some cases that the ./configure log says:

config.status: creating xxx/Makefile

but when make fails on:

make[2]: Entering directory xxx
make[2]: *** No rule to make target `all', Stop

and xxx/Makefile is absent in the disk. Why does it happened?

share|improve this question
You haven't given enough information to know what went wrong. You should show at least a complete transcript of your unpack-configure-make session. Preferably with an open source program so that other people can try to reproduce your problem. – Gilles Sep 1 '10 at 7:19
Have you manually checked that the Makefile in question is indeed there (i.e. via ls command or something) as the configure log suggests prior to running make? You need to post a lot more information to track this problem down. – dtlussier Sep 1 '10 at 13:20
@Gilles: Herm, it is hard to reproduce. This situation would not happen every time you compile it. The two pkg I've encountered with this problem is libvorbis and bind -- all are normal autotools stuff. – Grissiom Sep 2 '10 at 3:27
@dtlussier: Hrm, the problem env is on the production machine which is not at my hand. And the problem is so hard to reproduce that I cannot introspect at that degree... ;( – Grissiom Sep 2 '10 at 4:18

If you compile from the command-line make is likely to work.

But if - for instance - after ./configure you open Eclipse and try to build the project, you may have that warning (no all rule).

Also, some make by default expect a all in the Makefile if no specific rule is provided on the command line.

I suggest you open the Makefile(s) and add the rule

all: build

after the first rule (this is usually the default: make takes the first rule if none provided).
build being that first rule - it may be different in your case.

Or you make change the make calls to make <rule>.

share|improve this answer
But the problem I encountered is that the whole Makefile file is missing ;) – Grissiom Sep 2 '10 at 4:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.