hi len

> > [..]
> >
> > *** Warning: linker path does not have real file for library -lvpopmail.
> > *** I have the capability to make that library automatically link in when
> > *** you link to this library.  But I can only do this if you have a
> > *** shared version of the library, which you do not appear to have
> > *** because I did check the linker path looking for a file starting
> > *** with libvpopmail and none of the candidates passed a file format test
> > *** using a regex pattern. Last file checked:
> > /home/vpopmail/lib/libvpopmail.a
> >
> > *** Warning: libtool could not satisfy all declared inter-library
> > *** dependencies of module libauthvchkpw.  Therefore, libtool will create
> > *** a static module, that should work as long as the dlopening
> > *** application is linked with the -dlopen flag.
> > ..
> > --- snip ---
>
> I ran into a problem very similar to this building authdaemon against
> vpopmail-5.20 under NetBSD-3.1-i386.  After a lot of twists and turns
> I modified the vpopmail source to build libvpopmail as a shared lib as
> well as static.  I am not especially tallented with automake, autoconf
> and libtool, in fact I had never modified a build to create shared
> libs.  I found an excellent resource on how to do this at:
>
> http://sourceware.org/autobook/autobook/autobook_toc.html
>
> I successfully built libvpopmail.so, and placed it in a location where my
> build of courier-authdaemon would link against it.  The build was
> successful, and authdaemon is working flawlessly using the authvchkpw
> module.  It was a good learning experience; glad I know how to do this
> if I find myself in this situation again.  HTH

ok, it's not doing - for me - in a short time. i read this howto last view 
hours and realy: i learned. but - until know - i was not able to build 
libvpopmail.so . so i will try it later when i have more time. thank you

- Christoph

Reply via email to