summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorIvan Maidanski <ivmai@mail.ru>2018-05-18 22:00:36 +0300
committerIvan Maidanski <ivmai@mail.ru>2018-05-18 22:00:36 +0300
commit658f6393ffa12798c1cacfa3fa688247289e8544 (patch)
tree9ee90142d83e0efd07ca45dee3777ded198c9341 /README.md
parenta043dadec3c3f97e5899cf7d81e8f0dea9a347de (diff)
downloadbdwgc-658f6393ffa12798c1cacfa3fa688247289e8544.tar.gz
Do not use PKG_CHECK_MODULES in configure
Issue #200 (bdwgc). Presence of libatomic_ops is now detected only by checking the installed headers, but libatomic_ops is no longer needed for most of the clients which have atomic intrinsics support by the compiler. * README.md (Installation and Portability): Remove information about "syntax error near unexpected token ATOMIC_OPS". * autogen.sh: Update comment removing pkg-config from the requirements. * configure.ac (PKG_CHECK_MODULES(ATOMIC_OPS)): Comment out; update the comment.
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 0 insertions, 4 deletions
diff --git a/README.md b/README.md
index c25e82a0..6b4ae5cc 100644
--- a/README.md
+++ b/README.md
@@ -192,10 +192,6 @@ build of `master` branch of the collector could look like:
Cloning of `libatomic_ops` is now optional provided the compiler supports
atomic intrinsics.
-If you are getting "syntax error near unexpected token ATOMIC_OPS" during
-configure execution, this means pkg.m4 cannot be found, most probably
-you should run `pkg-config` once before running `./autogen.sh` (autoreconf).
-
Below we focus on the collector build using classic makefile.
For the Makefile.direct-based process, typing `make check` instead of `make`
will automatically build the collector and then run `setjmp_test` and `gctest`.