Disable profiling
Closed this issue · 6 comments
GoogleCodeExporter commented
Explaination of new feature
Disable profiling when building for an uClibc target via config option or libc
library detection.
Justification of new feature
uClibc no longer supports profiling using gcc -pg, so building the curernt
iperf3 surce using this libc fails.
Ref.:
https://www.kernel.org/pub/linux/libs/uclibc/Glibc_vs_uClibc_Differences.txt
(at document end).
Original issue reported on code.google.com by gvall...@gmail.com on 7 May 2013 at 11:47
Attachments:
GoogleCodeExporter commented
Please submit a patch to fix this and we'll look into incorporating it.
Original comment by jdu...@es.net on 8 May 2013 at 9:20
GoogleCodeExporter commented
please submit a patch
Original comment by bltier...@es.net on 8 May 2013 at 9:34
- Added labels: Milestone-3.1a1, Priority-Medium
GoogleCodeExporter commented
no one submitted a patch, and we can't replicate, so closing.
Original comment by bltier...@es.net on 23 Jul 2013 at 6:17
- Changed state: WontFix
GoogleCodeExporter commented
It's still an issue. As a workaround, changing the Makefile to remove "-pg"
from the profile LD and C flags fixes it, at the obvious expense of not
actually producing a profiled binary.
Is there a way (via configure or similar) to disable the profiled build, and
just have a plain binary?
Original comment by ara...@gmail.com on 19 Aug 2013 at 1:21
GoogleCodeExporter commented
I want to compile iperf in Openwrt environment. Using the uclibc-0.9.33.2, it
seems it could't compiled. I have to modify the Makefile.am to delete "-pg".
The embedded system resource is limited, so "-pg" couldn't add if want to be
used in Openwrt.
Original comment by wintonli...@gmail.com on 13 Jan 2014 at 6:13
Attachments:
GoogleCodeExporter commented
I'm unable to try at this time but the patch seem reversed, right?
Original comment by gvall...@gmail.com on 13 Jan 2014 at 12:24