httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralf S. Engelschall" <>
Subject Re: [PATCH] Fix module execution order for DSO situation
Date Fri, 17 Apr 1998 13:07:03 GMT

In article <> you wrote:
> According to Ralf S. Engelschall:

>>  Comments and votes?

> Just one thing...
> Is there a reason why the Load/AddModule directives are differently
> sorted compared to src/Configuration?

> Configuration has
>   ...
>   mod_setenvif
>   mod_unique_id
>   mod_so

> while APACI creates AddModule lines in the following order
>   ...
>   mod_unique_id.c
>   mod_so.c
>   mod_setenvif.c

> IMHO the order doesn't cause problems (the priority of
> mod_so is more or less unimportant and mod_unique_id 'only' plays
> with the UNIQUE_ID variable), but I'm curious if APACI is doing this
> intentionally or not...

I'm totally confused. The order APACI creates is exactly the order from
Configuration.apaci which itself is derived from Configuration.tmpl. Can it be
that your Configuration is an old one? The .tmpl shows the order


which _is_ the one you present for APACI's AddModule lines. Hmmm...

> BTW, how can I add/change compiler flags (e.g. -DBUFFERED_LOGS)
> when using APACI? If people have to edit src/apaci rsp. src/Makefile
> after configuring it should be noted in README.configure...
> But how about something like 'configure --extra-cflags="-DFOO -DBAR" ...'
> (same with extra-ldflags, extra-libs and extra-includes).
> Or did I missed something?

You missed something and seems that this was to read the INSTALL file ;_)
When you look at it you see that you just can use

$ CFLAGS="-DFOO -DBAR" ./configure ...

as you would with any other real Autoconf-based "configure" scripts.

                                       Ralf S. Engelschall

View raw message