Antwort: Re: [Mod_gzip] Makefile problem for Apache static compile

[mod_gzip@lists.over.net]

Hi Christopher,


> "--activate-module=src/modules/gzip/mod_gzip.a" \

you should refer to the source file "mod_gzip.c" in this line
(at least this is how it works for me), but I am not sure
whether this is important at all ("configure" might just take
the directory path and rely on the "Makefile" within to do what
has to be done).

> Makefile:108: warning: overriding commands for target `libgzip.a'
> make[4]: *** No rule to make target `mod_gzip.a', needed by
> My repertoire doesn't extend to Makefiles yet, can someone help?

Sigh. I recognize the symptoms, yet cannot explain the effect
in full detail. because I cannot reproduce it on every platform.
On some it works, and on others it doesn't ...

The compilation process of Apache works such that the "configure"
script will generate a "Makefile" from every "Makefile.tmpl" file
within any 'relevant' subdirectory. Thus mod_gzip provides its own
"Makefile.tmpl" file to create a library from its three modules.

By "activate-module" you have (correctly) added mod_gzip to the
list of these 'relevant' modules, and Apache will generate the
"Makefile" within this directory, and then "make" will try to
compile this module.

But the problem seems to be that the line
     LIB=libgzip.$(LIBEXT)
doesn't always work as expected.

For other Apache modules, "configure" will insert the value of
the library to be built, which should be "libgzip.a", and in
this case the generated "Makefile" would work nicely.

I have the same problem on my platform (Solaris 2.8), while the
identical "Makefile.tmpl" seems to work without problems on
several other platforms (BSD and Linux seem to be fine with it).

Could you please edit the "Makefile.tmpl" file and change the
first (non-empty) line to
     LIB=libgzip.a
and then re-run "configure"? (This is how it works on my platform.)
Be careful to use an editor that preserves tab characters, as
these are semantically important within Makefiles! (Check the
file size before and after this modification.)

> My repertoire doesn't extend to Makefiles yet, can someone help?

Same with me, which is the reason of the problem. I would provide
a better "Makefile.tmpl" if I understood the reason of the problem.

I simply tried to use the same mechanism as is in use for compiling
the Apache standard module mod_proxy which contains several modules
as well and looked most similar to be when I first wrote the
"Makefile.tmpl" file.
Unfortunately, I am not using "make" for a long time now and am
not into the details of "Makefile" logic any more, so I would
appreciate any expert to step in here and correct whatever errors
the "Makefile.tmpl" file may contain.

> make[4]: Warning: File `libgzip.a' has modification time 6.1e+04 s in
> the future

This line makes me wonder the most.

I am not sure whether there is some race conditions that might be
specific for your installation. I have never seen this effect before.

Regards, Michael