Skip to main content.
home | support | download

Back to List Archive

Q: No rule to make target `parse_conffile.c', needed by `parse_conffile.o'. Stop.

From: Kati Gäbler <katigaebler(at)>
Date: Fri Feb 23 2001 - 19:08:23 GMT

After doing ./configure of swish-e-2.1-dev-20, at the make stage, I get the 

"No rule to make target `parse_conffile.c', needed by `parse_conffile.o'.  

Anyone knows what it means? the complete make output was:

$ make

making swish-e
(cd src; make)
make[1]: Entering directory `/space/web/servers/alpha/swish-e-2.1-dev-20/src'
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c check.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c file.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c index.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c search.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c error.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c methods.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c hash.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c list.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c mem.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c string.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c merge.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c swish2.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c stemmer.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c soundex.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c docprop.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c compress.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c deflate.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c xml.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c txt.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c html.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c metanames.c
gcc -DSWISH_VERSION=\"2.1-dev-20\" -g -O2 -c result_output.c
make[1]: *** No rule to make target `parse_conffile.c', needed by 
`parse_conffile.o'.  Stop.
make[1]: Leaving directory `/space/web/servers/alpha/swish-e-2.1-dev-20/src'
make: *** [swish-e] Error 2


Should I use a PREFIX of some kind with configure or/and when doing make, as 
I don't have root permissions, if so, exactly how is that normally done?

Below is the output of the configure which I did before the make as above:

creating cache ./config.cache
checking whether #! works in shell scripts... yes
checking whether make sets ${MAKE}... yes
checking for perl... /usr/bin/perl
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for ranlib... ranlib
checking for main in -lm... yes
checking for dirent.h that defines DIR... yes
checking for opendir in -ldir... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for strings.h... yes
checking for unistd.h... yes
checking for working const... yes
checking for pid_t... yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for working alloca.h... yes
checking for alloca... yes
checking for strftime... yes
checking for vprintf... yes
checking for re_comp... yes
checking for regcomp... yes
checking for strdup... yes
checking for strstr... yes
checking for log in -lm... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
creating doc/Makefile
creating src/Makefile


Thanks for any tips!

Received on Fri Feb 23 19:13:52 2001