From: Peter Wang Date: Fri, 12 Jan 2018 16:50:47 +0000 (+0300) Subject: Remove obsolete advice about linking with _DYNAMIC=0 (Linux) X-Git-Tag: v8.0.0~428 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=29ac0186104fc287f592a71e14cc863889b9fb3e;p=platform%2Fupstream%2Flibgc.git Remove obsolete advice about linking with _DYNAMIC=0 (Linux) Issue #196 (bdwgc). The mentioned GCC option is not needed since gc-5.0alpha3 (when _DYNAMIC symbol was declared as weak in dyn_load.c). Even more, the advice is problematic for Alpine Linux (and probably other systems using musl) as building a program with gcc -static produces a binary containing a _DYNAMIC symbol with a non-zero address, and forcing the address to 0 causes a crash during GC initialization. * doc/README.linux: Remove note that static executable should be linked with the gcc option "-Wl,-defsym,_DYNAMIC=0". --- diff --git a/doc/README.linux b/doc/README.linux index 0d4bb6c..fa2cd22 100644 --- a/doc/README.linux +++ b/doc/README.linux @@ -8,8 +8,7 @@ See below for M68K specific notes. Incremental GC is generally supported. -Dynamic libraries are supported on an ELF system. A static executable -should be linked with the gcc option "-Wl,-defsym,_DYNAMIC=0". +Dynamic libraries are supported on an ELF system. The collector appears to work reliably with Linux threads, but beware of older versions of glibc and gdb.