* [email protected] ([email protected]) wrote: > Hi, > > I'm trying to get ust working on Android, but got stuck: > > out/[snip]/marker.o: In function `destroy_ust_marker': > /android-lttng/external/ust-posix/libust/marker.c:1463: undefined reference > to `__start___ust_marker_ptrs' > out/[snip]/marker.o: In function `init_ust_marker': > /android-lttng/external/ust-posix/libust/marker.c:1458: undefined reference > to `__start___ust_marker_ptrs' > /android-lttng/external/ust-posix/libust/marker.c:1458: undefined reference > to `__stop___ust_marker_ptrs' > /android-lttng/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/arm-eabi/bin/ld: > out/[snip]/libust.so: hidden symbol `__stop___ust_marker_ptrs' isn't defined > /android-lttng/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/arm-eabi/bin/ld: > final link failed: Nonrepresentable section on output > > > I suspect differences between gnu and android 'ld', but since I can't figure > out where the missing symbols are supposed to come from, it's hard to work > out a fix. > > If anyone could shed some light on how and where the __start__xyz/__stop__xyz > symbols are defined I'd very happy!
See http://gnu.feld-it.at/software/libc/FAQ.html (1.10) These are automatically generated linker symbols. So either you'll have to figure out how to add support for them in your linker, or create your own linker script to support libust. We need that to do the glue between the markers/tracepoints sections and the extern symbols around the beginning and end of these sections (as visible from C). Thanks, Mathieu > > Regards, > Per > _______________________________________________ > ltt-dev mailing list > [email protected] > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com _______________________________________________ ltt-dev mailing list [email protected] http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
