From: Lee Essen <lee.essen@nowonline.co.uk>
To: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] Thoughts around dtrace linking...
Date: Wed, 21 Mar 2012 10:45:11 +0000 [thread overview]
Message-ID: <4F69B137.3070709@nowonline.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
Hi,
I've been trying to find a sensible way to solve the Solaris/Illumos
dtrace requirement to pass all the objs to the dtrace command so that
the resultant object file contains all the symbols needed to properly
link the relevant binary.
The easiest way to do this is just prior to linking the binary, so
something like this (in rules.mak):
LINK = $(call quiet-command,$(CC) $(QEMU_CFLAGS) $(CFLAGS)
$(LDFLAGS) -o $@ $(sort $(1)) $(LIBS)," LINK $(TARGET_DIR)$@")
DTRACE = $(call quiet-command,dtrace $(CONFIG_DTRACE_FLAGS) -o
$(1)-dtrace.o -G -s $(2) $(3), " GEN $(TARGET_DIR)$(1)-dtrace.o")
%$(EXESUF): %.o
$(call DTRACE,$*,trace-dtrace.dtrace,$^)
$(call LINK,$^ $*-dtrace.o)
Obviously with the relevant tests around it to check the trace backend,
and also an adjustment in Makefile.target to cause the right thing to
happen for each target.
Or, is there a better way?
How compatible is this with FreeBSD - it doesn't sound like it's needed
at all?
Regards,
Lee.
[-- Attachment #2: Type: text/html, Size: 1426 bytes --]
next reply other threads:[~2012-03-21 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 10:45 Lee Essen [this message]
2012-03-21 13:01 ` [Qemu-devel] Thoughts around dtrace linking Andreas Färber
2012-03-21 13:37 ` Lee Essen
2012-03-22 16:28 ` Stefan Hajnoczi
2012-03-22 17:00 ` Lee Essen
2012-03-23 8:08 ` Stefan Hajnoczi
2012-03-23 14:11 ` Lee Essen
2012-03-26 10:14 ` Stefan Hajnoczi
2012-03-26 15:28 ` Lee Essen
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=4F69B137.3070709@nowonline.co.uk \
--to=lee.essen@nowonline.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.