On Mon, Dec 22, 2014 at 1:09 PM, Cyd Haselton <chaselton@xxxxxxxxx> wrote: > On Mon, Dec 22, 2014 at 1:05 PM, Andrew Haley <aph@xxxxxxxxxx> wrote: >> On 12/22/2014 06:40 PM, Cyd Haselton wrote: >>>> What does your /usr/lib/libc.so look like? I'd expect to see >>>> > something like this: >>>> > >>>> > /* GNU ld script >>>> > Use the shared library, but some functions are only in >>>> > the static library, so try that secondarily. */ >>>> > OUTPUT_FORMAT(elf64-x86-64) >>>> > GROUP ( /lib64/libc.so.6 /usr/lib64/libc_nonshared.a AS_NEEDED ( /lib64/ld-linux-x86-64.so.2 ) ) >>> >>> I'm not quite sure what you're asking; I'm using a sysroot with the >>> build compiler and the libc.so is not a script but an actual library. >>> Were you asking about the build link script or the stage1 link script? >> >> I'm asking about the file /usr/lib/libc.so. >> >> If it's a script which looks like the file above you'll get >> the function definitions you need when you link against libc, >> even though dlopen is defined in ld-blah.so. >> >> Andrew. >> > > There's no /usr/lib/libc.so in the environment in which I'm working on > my Android device. > > The script excerpt you included in your original email looks familiar > though. Is it possible the script is located elsewhere, with a > different name? Or, if not, is there a workaround? I'm assuming there is as I've built versions previous to 4.8.x on-device...
