From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: profiling howto?
Date: Thu, 03 Feb 2011 09:30:14 +0100 [thread overview]
Message-ID: <4D4A6796.1070006@dresearch.de> (raw)
In-Reply-To: <4D49552D.3010705@dresearch.de>
Am 02.02.2011 13:59, schrieb Steffen Sledz:
> Am 02.02.2011 10:54, schrieb Steffen Sledz:
>> Has anybody some instructions/hints how to enable profiling
>> support for selected libs and/or binaries in OE?
>
> The local.conf.sample does contain this section:
>
> # Uncomment these to build a package such that you can use gprof to profile it.
> # NOTE: This will only work with 'linux' targets, not
> # 'linux-uclibc', as uClibc doesn't provide the necessary
> # object files. Also, don't build glibc itself with these
> # flags, or it'll fail to build.
> #
> # PROFILE_OPTIMIZATION = "-pg"
> # SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}"
> # LDFLAGS =+ "-pg"
>
> This seems to do the work for the complete image.
Hmmmm? Unfortunately not in all cases. Enabling the options mentioned above and making a clean build results in
| ...
| checking for .preinit_array/.init_array/.fini_array support... no
| configure: error: Need linker with .init_array/.fini_array support.
| ERROR: Function do_configure failed
NOTE: package glibc-2.9-r36.3: task do_configure: Failed
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/sledz/work/openembedded/recipes/glibc/glibc_2.9.bb do_configure failed
ERROR: Task 127 (/home/sledz/work/openembedded/recipes/glibc/glibc_2.9.bb, do_configure) failed with 256
Any ideas?
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-02-03 8:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 9:54 profiling howto? Steffen Sledz
2011-02-02 10:11 ` Holger Freyther
2011-02-02 11:12 ` Henning Heinold
2011-02-02 12:59 ` Steffen Sledz
2011-02-02 13:12 ` Holger Freyther
2011-02-03 8:05 ` Steffen Sledz
2011-02-03 9:00 ` Holger Freyther
2011-02-03 10:44 ` Steffen Sledz
2011-02-03 8:30 ` Steffen Sledz [this message]
2011-02-03 8:54 ` Jan Paesmans
2011-02-03 10:52 ` Steffen Sledz
2011-02-03 11:30 ` Holger Freyther
2011-02-03 11:50 ` Steffen Sledz
2011-02-03 11:53 ` Holger Freyther
2011-02-03 12:07 ` Steffen Sledz
2011-02-03 12:14 ` Holger Freyther
2011-02-03 13:06 ` Steffen Sledz
2011-02-03 13:10 ` Holger Freyther
2011-02-04 12:09 ` Steffen Sledz
2011-02-03 14:25 ` Phil Blundell
[not found] ` <1296735116.2258.44.camel@phil-desktop>
2011-02-03 14:25 ` Phil Blundell
2011-02-03 22:34 ` Khem Raj
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=4D4A6796.1070006@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@lists.openembedded.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