From: matthew.khouzam@ericsson.com (Matthew Khouzam)
Subject: [ltt-dev] building ust for android/arm
Date: Wed, 20 Apr 2011 19:38:08 -0400 [thread overview]
Message-ID: <4DAF6E60.8010409@ericsson.com> (raw)
Message-ID: <20110420233808.IH2lJ4BW4XveCUPyS_GWJjLTAjSlti_jKubyoHxUlXM@z> (raw)
In-Reply-To: <BANLkTinQ5WAPzwDD-iREO9bR5cLTQOGFtw@mail.gmail.com>
My advice, is kinda silly, but, Mathieu Desnoyers is saying use a newer
version, and the version you are using is not working, I would at least
try out a new version.
What kernel are you using?
If you're on 2.6.16 We actually got it +- working with UST 0.12.
git://git.dorsal.polymtl.ca/~mattkhouzam/ust_documentation
Note: you cannot tell which core is being used if you apply the changes
in the document, so if you are using a multi-cored cpu, you really
really should consider updating your kernel.
Keep us posted with the results,
Matthew
On 11-04-20 01:37 PM, Xing Fan wrote:
> I am building lttng ust-0.6 for android/Arm platform.
>
> However, I have problems to build libust.so. The error msg is: make:
> *** No rule to make target `build/core/libust-initializer.c', needed
> by
> `out/target/product/u8500/obj/SHARED_LIBRARIES/libust_intermediates/libust-initializer.o'.
> Stop.
>
> It is very strange that the compiler tries to pick up
> libust-initializer.c from build/core folder, even though I have
> specified that the source file is in my LOCAL_PATH;
>
> Anyone has clue how to write a Android.mk for this?
>
> /Stella
>
>
>
> My Android.mk file looks like this:
> ===========================================================
> include $(call all-subdir-makefiles)
>
> LOCAL_PATH := $(call my-dir)
>
> include $(CLEAR_VARS)
> LOCAL_MODULE := libust
> LOCAL_SRC_FILES := libust-initializer.c
> LOCAL_C_INCLUDES += \
> $(LOCAL_PATH) \
> $(LOCAL_PATH)/include \
> external/userspace-rcu-0.4.6
> include $(BUILD_SHARED_LIBRARY)
> ===============================================================
>
>
> The Makefile.am looks like this
> =========================================================================
>
> ACLOCAL_AMFLAGS = -I config
>
> # The order here is tricky. SUBDIRS applies both to compilation and
> # installation. Programs depending on the libs must be built after
> # libust and '.' (that contains the linker script). However, '.'
> # must be installed after libust so it can overwrite libust.so with
> # the linker script.
> SUBDIRS = snprintf libustcomm libust . tests libustinstr-malloc
> libustd ustd ustctl libustfork include doc
>
> EXTRA_DIST = libust.ldscript.in <http://libust.ldscript.in>
> libust-initializer.c
> dist_bin_SCRIPTS = usttrace
>
> ldscriptsdir = $(libdir)
> ldscripts_DATA = libust.so libust-initializer.o
>
> CLEANFILES = $(ldscripts_DATA) ./tests/libust-initializer.Po
>
> libust.so: libust.ldscript.in <http://libust.ldscript.in>
> $(SED) -e "s@\@FORMAT\@@$(LIBFORMAT)@" < $< > $@
>
> # It is very important to compile the initializer with PIC otherwise we
> # may get obscure errors when linking to shared libraries.
> libust-initializer.o: libust-initializer.c
> $(CC) $(CFLAGS) -fno-strict-aliasing -fPIC -c
> -I$(top_srcdir)/include -o $@ $<
> ===========================================================
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110420/1d692c64/attachment-0002.htm>
next prev parent reply other threads:[~2011-04-20 23:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 17:37 Xing Fan
2011-04-20 17:37 ` Xing Fan
2011-04-20 17:37 ` Xing Fan
2011-04-20 18:12 ` Mathieu Desnoyers
2011-04-20 19:38 ` Xing Fan
2011-04-20 19:38 ` Xing Fan
2011-04-20 19:38 ` Xing Fan
2011-04-20 20:39 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP138D8FC21BF014372219BA96930@phx.gbl>
2011-04-20 21:12 ` Karim Yaghmour
2011-04-20 21:21 ` Xing Fan
2011-04-20 21:21 ` Xing Fan
2011-04-20 21:21 ` Xing Fan
2011-04-20 21:31 ` Mathieu Desnoyers
2011-04-20 23:20 ` Karim Yaghmour
2011-04-20 23:38 ` Matthew Khouzam [this message]
2011-04-20 23:38 ` Matthew Khouzam
2011-04-20 23:38 ` Matthew Khouzam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DAF6E60.8010409@ericsson.com \
--to=matthew.khouzam@ericsson.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox