IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
I have to investigate the effect of these and evaluate the need of
their presence. For now establish more reasonable grouping.
Michael
(This used to be commit 3ba8fa1c4b)
This should work with m4_include(lib/tdb/libtdb.m4) like already
done with talloc, but currently this does not work (yet) - tdb
code has to be merged from s4 before that.
Michael
(This used to be commit e92fdf6b20)
Golly gosh, this one took me quite some time to figure out!
Hopefully, I did not introduce any typos copying...
Michael
(This used to be commit 85ca2c9edb)
Formerly this was only needed for libwbclient, but now that we start
using more shared libs internally, this is needed more globally
to support linking internal libs dynamically on systemy without winbindd.
Michael
(This used to be commit ec79357218)
This also establishes a general configure mechanism to control static vs
dynamic linking of internal subsystems built as libraries:
This first simple approach is as follows.
* It applies only to "subsystems" that we build as libraries and for
that linking samba against the libraries (as opposed to linking in
the plain object files) has been configured in Makefile.in.
* If we do build the shared library, then we link dynamically by default.
* We only link statically if we don't build shared or if the library
appears in the new --with-static-libs configure option
(comma-separated list).
Example (currently only one):
--with-static-libs=talloc makes use of libtalloc.a instead
of linking the dynamic variant with -ltalloc.
A possilble way to setup linking against libraries in Makefile.in is this:
For a subsystem, "mylib" say, we build bin/libmylib.a and bin/libmylib.so.
The subsystem usually has a MYLIB_OBJ definition in Makefile.in. Define
LIBMYLIB_STATIC=bin/libmylib.a and and LIBMYLIB_LIBS=-lmylib in configure.in
as controlled by presence of "mylib" in the list given to --with-static-libs
and change uses of $(MYLIB_OBJ) to @LIBMYLIB_STATIC@ in Makefile.in and
add @LIBMYLIB_LIBS@ to the link targets as needed.
In the example of talloc, which is needed everywhere, I have simply
added @LIBTALLOC_LIBS@ to the definition of "LIBS" in Makefile.in.
For other subsystems, one will have to be more careful.
Michael
(This used to be commit 71b990d9d6)
Use the resulting HAVE_LBER_LOG_PRINT_FN to determine whether we can
use it in init_ldap_debugging to intercept LDAP debug output and print
it out in the samba logs (controlled with "ldap debug level").
Michael
(This used to be commit 8dfc389ff6)
-bexpall only exports the names without leading _, so we don't get
_talloc_reallo_array for example.
Thanks a lot to Heinrich Mislik for the hint!
(This used to be commit 74a71f1988)
Store streams in posix xattrs. A kludge, as xattrs are limited in many ways,
but it might be a help for some situations.
(This used to be commit 83a805220e)
This reverts commit e33286f4a6.
393bab185e0e9f02aac5740becc2aba2762133c8 is the v4-0-test fix
for the same problem.
metze
(This used to be commit b8a57a24c3)
This is an option for file systems that do not implement xattrs: in
lockdir/eas.tdb an array of xatts per inode is stored.
It can not solve the problem that xattrs might reappear if a posix-level
process deletes a file and happens to re-create it under the same name. On file
systems with birthtime we might have a chance to detect this, but not with
standard posix. A future version might put relief on file systems that do have
xattrs but where these are severely limited in size/speed/whatever: We can put
a simple marker as a native xattr, but the xattrs proper are stored in the tdb.
Volker
(This used to be commit 2036b4c5ad)
This patch adds the configure option --enable-libwbclient-shared that defaults
to yes. If you set --enable-developer=yes, then you can say
--enable-libwbclient-shared=no to avoid problems you might have with the wrong
shared libaries.
Jerry, is this acceptable to you? If yes, please push.
Thanks!
Volker
(This used to be commit 7a88cd61e0)
