| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Change a few things a suggested in to make things work out-of-the-box on
old MacOS X.
https://bugzilla.gnome.org/show_bug.cgi?id=580301
http://bugzilla-attachments.gnome.org/attachment.cgi?id=133452
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This ensures that hte library will be built in a way that will not
fail when --as-needed is used.
|
|
|
|
| |
This way they don't get added to the generated configure script.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Instead of using AC_SEARCH_LIBS or AC_CHECK_LIB, create a new macro to
search for function in different libraries; this is needed since the
function name might just be a (preprocessor) macro for another symbol.
The new macro is released under GPL2 (or later) + exception, and
allows to provide a custom source code to use to test for the
function.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
configure.ac
|
| |
| |
| |
| |
| | |
As many 0pointer projects use the same code, move it out on its own
macro, and use that. The macro can then be shared across projects.
|
| |
| |
| |
| | |
Use eval to make sure the correct variable name is tested.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of writing custom code to check for cflags checking, import a
copy of attributes.m4 from xine-lib's repository and use the
CC_CHECK_CFLAGS macro.
The advantage lies not only in being able to reduce the custom code in
configure.ac, but also in the fact that the CC_CHECK_CFLAGS macro
caches the results, making ./configure -C quite faster on second run.
Check for the CFLAGS for any compiler and not just GCC, if the
compiler does support the flag it is better to u se it anyway,
otherwise it will be skipped.
|
| |
| |
| |
| |
| |
| | |
Instead of just checking if the compiler supports -std=c99 option,
make use of the autoconf macro for discovering C99. This way other
non-GCC compiler could be used in C99 mode too.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Make this change because recent versions of libtool (2.2 series) copy
over their m4 macro files if an m4/ directory is present, and because
futher m4/ macro files might be added too.
Also make sure the macro directory is announced to autoconf and is
picked up by aclocal.
|
| |
| |
| |
| |
| |
| |
| | |
In recent versions of autoconf, the AC_HEADER_ASSERT check not only
makes sure that the assert.h header is found but it also allows the
user to decide whether to enable or disable assertions at ./configure
(rather than having to pass -DNDEBUG manually).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Install and distribute README.html and style.css in the html
directory.
Install and distribute README in the doc directory.
The htmldir and docdir entries are added by recent versionf of
autoconf and are configurable, so that distributions don't need to
handle installation of these manually.
|
| |
| |
| |
| |
| | |
Replaces AC_GNU_SOURCE with AC_USE_SYSTEM_EXTENSIONS and
AC_HELP_STRING with AS_HELP_STRING (and quotes its parameters).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As it turns there were two issues with the current logic how we shut
down the worker threads:
- We asked the threads to shutdown by closing the socket that is
the communication from the context to the worker thread. This is racy
because other threads might allocate the same fd immediately after it
was closed and our worker thread ends up reading from that new fd
under some circumstances.
- To avoid blocking on shutdown we only detached the thread -- not
waiting for its termination. This will cause an immediate segfault
when the libasyncns gets unloaded from memory, e.g. because it was
loaded by DSO.
We have to acknowledge thati we need to make sure all name lookups are
terminated properly on destruction and that there is simply no clean way
to cancel name loops unless they are done out-of-process.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Hi,
The asyncns-test.c file needed the same fix but 'make check' still
fails with the following error:
Undefined symbols:
"_res_9_dn_expand", referenced from:
_main in asyncns-test.o
_main in asyncns-test.o
_main in asyncns-test.o
ld: symbol(s) not found
I haven't looked into where they are supposed to be defined though
(about to run off for dinner here).
Attaching small patch for async-test.c (also moved the header check
into your already existing AC_CHECK_HEADERS).
Cheers,
Micke
Signed-off-by: Lennart Poettering <lennart@poettering.net>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Hi Lennart,
I have a copy of libasyncns in Loudmouth and just updated it to the
version in 0.6 which required the following patch in order to build on
Mac OS X.
* arpa/nameser_compat.h seems to get included by nameser.h on Linux but
not on Mac OS X.
* Removed an unused variable that caused the compiler to complain when
building with warnings
* Both Mac OS X and Linux seems to define NSIG (on Linux to _NSIG and on
Mac OS X to __DARWIN_NSIG.
Thanks for your nice work on the lib and hope the patch may be of some
use.
Cheers,
Micke
Signed-off-by: Lennart Poettering <lennart@poettering.net>
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
Thébault)
|
| |
|
| |
|
|
|
|
| |
breakage
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|