Re: Oprofile cross compilation for arm

On Tue, Oct 07, 2014 at 02:59:58PM +0100, Sabra Gargouri wrote:
> Hi,
> Thank you Maynard for your support!
> I have first executed make  command from within my kernel source tree:
>      make headers_install INSTALL_HDR_PATH=<kernel-hdrs-install-dir> and then pass <kernel-hdrs-install-dir> to oprofile's '--with-kernel' configure option.
> 
> ./configure --with-kernel-support --with-kernel=/home/sdk-test/Downloads/kernel-headers --host=i686-linux --build=arm-cortex-linux-gnueabi --with-extra-libs=/home/sdk-test/Downloads/popt-1.16/.libs/:/home/sdk-test/Downloads/binutils-2.24/libiberty/:/home/sdk-test/Downloads/binutils-2.24/bfd/ --with-binutils=/home/sdk-test/Downloads/binutils-2.24/ --with-extra-includes=/home/sdk-test/Downloads/popt-1.16/:/home/sdk-test/Downloads/binutils-2.24/bfd/

I've not done cross-compilation of oprofile for a while now -- ARMv7 CPUs
tend to be quick enough to build things natively without much pain.

Are we sure that the problem being reported is due to the cross-compilation
step? Does a native compilation appear to fix the problem?

Sorry for the vague questions, but there's really not a lot to go on here.

Will

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk