From: "Alex Bennée" <alex.bennee@linaro.org>
To: oussema ben khedher <oussemakeder@yahoo.fr>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] how to enable trace
Date: Mon, 13 Mar 2017 10:19:38 +0000 [thread overview]
Message-ID: <87bmt5qy11.fsf@linaro.org> (raw)
In-Reply-To: <928382347.7043935.1489394441716@mail.yahoo.com>
oussema ben khedher <oussemakeder@yahoo.fr> writes:
> i used simple trace back end to trace guest code running in qemu but when i tried to recompile and disable this trace i have always this problem
> undefined reference to `trace_record_write_u64'
> thanks for your help
It's always worth doing a make clean if you change you configure
options.
What was your configure command and what exactly did the compiler say?
--
Alex Bennée
prev parent reply other threads:[~2017-03-13 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <928382347.7043935.1489394441716.ref@mail.yahoo.com>
2017-03-13 8:40 ` [Qemu-devel] how to enable trace oussema ben khedher
2017-03-13 10:19 ` Alex Bennée [this message]
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=87bmt5qy11.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=oussemakeder@yahoo.fr \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).