From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: profiling howto?
Date: Thu, 03 Feb 2011 14:25:09 +0000 [thread overview]
Message-ID: <1296743109.15389.1.camel@phil-desktop> (raw)
In-Reply-To: <1296735116.2258.44.camel@phil-desktop>
On Thu, 2011-02-03 at 12:11 +0000, Phil Blundell wrote:
> On Thu, 2011-02-03 at 13:07 +0100, Steffen Sledz wrote:
> > conftest.c:(.text+0xc): undefined reference to `mcount'
>
> That looks like your C library was either built without profiling
> support, or is using a different profiling ABI. (I think there was a
> change in this area for ARM EABI sometime around gcc 4.4, and glibc
> might not have caught up with it.)
Oh, I just noticed that it's glibc itself you're trying to build with
profiling on. You need to not do that, or at least not by the mechanism
you're trying to use. If you really want to profile glibc itself then
there is an --enable-profile configure option which will do the right
thing. Otherwise, you need to suppress the PROFILE_OPTIMIZATION when
building glibc.
p.
next prev parent reply other threads:[~2011-02-03 14:36 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
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 [this message]
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=1296743109.15389.1.camel@phil-desktop \
--to=philb@gnu.org \
--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 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.