Hello Alessandro, On 03/31/2017 10:49 AM, Alessandro Vesely wrote: > I, for one, run my own pipeauth > > ldd /etc/courier/authlib/authProg > linux-vdso.so.1 => (0x00007fffb59bc000) > libcourierauthsasl.so => > /usr/local/lib/courier-authlib/libcourierauthsasl.so (0x00007ff1e44cd000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff1e4140000) > libcourierauthcommon.so => > /usr/local/lib/courier-authlib/libcourierauthcommon.so (0x00007ff1e3f37000) > libcourierauth.so => /usr/local/lib/courier-authlib/libcourierauth.so > (0x00007ff1e3d2a000) > /lib64/ld-linux-x86-64.so.2 (0x00007ff1e46d0000) > libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > (0x00007ff1e3a23000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff1e37a1000) > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x00007ff1e358b000) > libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 > (0x00007ff1e3354000)
The interesting question here would be whether you're linking against libcourierauthsasl (and using its symbols only) or if your authProg depends on libcourierauthcommon, directly. (Indirectly, via libcourierauthsasl, libcourierauthcommon will always be linked in either case.) (Other than that I note that you're not using Debian packages, in the first place, so you wouldn't be affected. I still appreciate your inputs. Maybe there are Debian users doing or wanting to do the same.) Kind Regards Markus Wanner
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
