Thanks Gustaf,
Yes, it helped. I was blindly looking at the source, available on Bitbucket,
which has only Makefile (i.e. there was no nsldap.o neither nsldap.so). Then I
started to wonder how I would compile it, or if there was another method to do
so.
I should have thought out of the box a bit (i.e. after I noticed the files were
missing), and gone straight ahead to source forge file repository, which is
know by myself already.
I’ve installed nsldap successfully. Thanks a lot!
One quick thing, I ran into the error bellow. lber.h was missing on my Debian
distro.
nsldap.c:38:18: fatal error: lber.h: No such file or directory
I went to the file nsldap to debug it and I quickly verified that lber.h is
required and called in the respective line 38. Nothing much, that a few more
packages installed through apt-get to solve the problem.
apt-get install libsasl2-dev libldap2-dev libssl-dev
Best wishes,
Iuri
> On May 12, 2018, at 06:16, Gustaf Neumann <neum...@wu.ac.at> wrote:
>
> On 10.05.18 04:01, Iuri Sampaio wrote:
>> Hi there,
>>
>> In attempt to to install and setup nsldap, I have changed install-ns.sh
>> script to look to HEAD repos but When running install-ns build it returns
>>
>> ------------------------ Downloading sources ----------------------------
>> abort: no repository found in '/usr/local/src/modules/nsdbbdb' (.hg not
>> found)!
> the error message means: your changes to install-ns are incorrect, you are
> trying to use mercurial on a non-mercurial directory (mercurial checks the
> .hg directory). You can can install the modules via source code management
> system (mercurial) or via the packaged tar file (recommended for beginners).
>> Then I realized that recompiling NS from HEAD could dangerous. rsrs!
>>
>> In another front, I've downloaded NSLDAP, available on bitbucket
>> https://bitbucket.org/naviserver/nsldap
>> <https://bitbucket.org/naviserver/nsldap>, but I don’t know how to install
>> and enable into my current Naviserver installation (i.e. generating .so file
>> in the proper location and so on).
>>
>> Do I need to recompile NS? Re-Installing it from scratch?
>> Where should I place nsldap source files?
>>
>> The information is not available on README.txt
> the cooking recipe for all modules is essentially the same.
> a) first install NaviServer (preferably on the standard place in
> /usr/local/ns, otherwise
> you have to specify for the compilation of a module "NAVISERVER=...")
>
> b) obtain the modules source code, either via the modules tar file from
> sourceforge
> (naviserver-*-modules.tar.gz) - this is preferred, or via mercurial (clone
> every single
> module you need)
>
> c) change to the directory of the modules and do
>
> make
> make install
>
> Sometimes, module specific configurations are need (e.g. paths to includes
> or libraries) as indicated in the README file of the module.
> the place, where you put the source files, does not matter.
> there is no need to recompile NaviServer, when adding modules.
>
> Hope, this helps
> -gn
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> naviserver-devel mailing list
> naviserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
