Antwort: Re: Antwort: [Mod_gzip] [compilation problem] apache&mod
_gzip
mod_gzip@lists.over.net
mod_gzip@lists.over.net
Mon, 17 Mar 2003 14:36:38 +0200
Hi Phil,
> replace at line 63: "all: lib shlib" by "all: libgzip.a mod_gzip.a"
> and at line 112: "all: lib" by "all: libgzip.a mod_gzip.a"
this should have been generated automatically.
"lib" and "shlib" are only variables whose content is to be
computed and assigned by "configure" while generating a
"Makefile" from the "Makefile.tmpl" template.
> from line 96 to 103 of apache/src/modules/gzip/mod_gzip.c :
>
> #include "httpd.h"
> #include "http_config.h"
> #include "http_core.h"
> #include "http_log.h"
> #include "http_main.h"
> #include "http_protocol.h"
> #include "http_request.h"
> #include "util_script.h"
>
> by
>
> #include "../../include/httpd.h"
> #include "../../include/http_config.h"
> #include "../../include/http_core.h"
> #include "../../include/http_log.h"
> #include "../../include/http_main.h"
> #include "../../include/http_protocol.h"
> #include "../../include/http_request.h"
> #include "../../include/util_script.h"
Again, this should not be necessary.
An "include" statement in C will be matched against the
list of all directories that are given as "-I" parameters
to the "cc" call.
One SHOULD NOT hard-code explicit paths here, because in
this case you are dependent on a certain directory structure.
> line 114 of apache/src/include/ap_config.h
> #include "os.h" by #include "../os/unix/os.h"
>
> line 62 of apache/src/os/unix/os.h
> #include "ap_config.h" by #include "../../include/ap_config.h"
And these lines prove that the origin of the problem is
not inside mod_gzip.
If you aren't able to compile even an Apache core source
file, then something in your environment seems to be broken.
You should be able to replace all the changes above by
adding the proper "-I" parameter to your "cc" statements
- this is the place where something doesn't work correctly.
But I don't know the temporary files of "configure" well
enough to tell you what actually went wrong.
"configure" is caching the results of previous runs in
some files. So maybe it would be a good idea to cleanup
the file tree ("make distclean") and start from scratch.
Regards, Michael