From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] __mcount on ARC
Date: Mon, 19 Feb 2018 09:09:39 +0100 [thread overview]
Message-ID: <20180219090939.1f050545@windsurf.lan> (raw)
In-Reply-To: <8e90a87a-7e64-6662-3309-ce0325bc686f@gmail.com>
Hello,
+Alexey in Cc.
On Sun, 18 Feb 2018 19:45:08 +0100, Zoltan Gyarmati wrote:
> I'm investigating this [1] autobuild error, where the gpsd build fails
> while profiling is enabled, due to undefined reference to `__mcount', on
> ARC arch.
>
> Ironically enough due to a bug in the gpsd build config the -pg flag is
> not passed to the linker only to the compiler, but after patching that
> one, the build issue remains.
> According to this thread [2] this happened earlier with ARC but other
> package, so is there anything particular about ARC regarding to
> profiling? Should we just disable the gpsd profiling option on ARC?
>
> [1]
> http://autobuild.buildroot.net/results/88870f5bf4aff557d8eac4e1cc5d3e397e607af0/
>
> [2]
> http://buildroot-busybox.2317881.n4.nabble.com/autobuild-buildroot-net-Build-results-for-2017-11-19-td180416.html
Alexey, could you comment on this ? I vaguely remember that profiling
was not supported on ARC at some point, but I have no idea if this is
still the case or not.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-19 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 18:45 [Buildroot] __mcount on ARC Zoltan Gyarmati
2018-02-19 8:09 ` Thomas Petazzoni [this message]
2018-02-19 8:58 ` Alexey Brodkin
2018-02-19 20:02 ` Zoltan Gyarmati
2018-02-20 15:46 ` Alexey Brodkin
2018-02-20 20:38 ` Zoltan Gyarmati
2018-02-20 20:53 ` Vineet Gupta
2018-02-21 7:06 ` Alexey Brodkin
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=20180219090939.1f050545@windsurf.lan \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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