Lines Matching refs:linker

1 # Android linker changes for NDK developers
19 Our general practice with dynamic linker behavior changes is that they
31 * On a developer preview build, dynamic linker warnings will also show up
40 on the dynamic linker's search path. This meant that apps
44 dynamic linker's caching code cached failures too, so it was necessary
66 linker divides other libraries into the global group and the local
71 libraries. The M dynamic linker searches the global group followed by
80 `libfoo.so` instead, letting the dynamic linker find the correct library
97 symbol lookup and is now supported by the dynamic linker in API 23 and
104 The dynamic linker now understands the difference
113 `"dir2/libx.so"` --- the dynamic linker couldn’t tell the difference
155 rule is enforced by the dynamic linker, so non-public libraries
198 *Potential problems*: starting from API 24 the dynamic linker will not
220 headers. These headers must be present now, because the dynamic linker
270 because the Android dynamic linker trusts the entry/flag.
274 linker has issued warnings about text relocations since Android K
292 linker.
294 Before API 23, Android's dynamic linker ignored the full path, and
296 up the required libraries. Since API 23 the runtime linker will honor
320 only. It is better to let the runtime linker to find and load those
346 the -soname linker option).
372 dynamic linker what permissions to give the corresponding page in
389 In API level 26 and above the dynamic linker checks more values in
404 linker activity for debuggable apps by setting a property corresponding
414 calls of dlerror(3) but to any time the dynamic linker writes to its
415 internal error buffer, so you'll see any errors the dynamic linker would
450 the dynamic linker to choose optimized assembler routines at run time