Adding a module, config variables unknown
is at rambler-co.ru
Thu Aug 21 19:25:22 MSD 2008
On Thu, Aug 21, 2008 at 05:07:41PM +0200, Bjoern wrote:
> it seems the absolute path was the problem.
> My solution is this:
> cd ~/devel/nginx
> mkdir src/addons
> ln -s /home/myuser/data/development/workspace/ngx_mymodule/src/
> ./configure --add-module=src/addons/ngx_mymodule
> make install
> I don't know why the absolute path doesn't work. The oddest thing is,
> that everything gets compiled perfectly well and that the binary
> contains strings containing 'ngx_mymodule', so it's in there.
> I'm not sure, why the path is relevant after the compile process
> succeeded... but it seems to be. Can anybody explain this to me, please?
> Or am I just misinterpreting anything?
I commonly use
and did not tried aboslute path, I will look.
> Bjoern wrote:
> >sorry.. That was just the example...
> >I used the absolute path of course...
> >/home/myuser/data/development/workspace/ngx_accesskey/src/ to be exact.
> >Unfortunately, that's not the problem.
> >Valery Kholodkov wrote:
> >>"Bjoern" <bjoern at pokerstrategy.com> wrote:
> >>>Hi everybody,
> >>> I have a problem adding a module.
> >>>I've downloaded and extracted the nginx sources.
> >>>Downloaded the sources of the module called "accesskey".
> >>>Extracted the files to a folder let's call it
> >>>cd ~/devel/nginx
> >>>./configure --add-module=~/devel/ngx_accesskey/src/
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>Tilde (~) is not going to be expanded here. Use full path.
More information about the nginx