Re: cross compiling perf

[Milian Wolff <milian.wolff@kdab.com>]

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

On Thursday, August 4, 2016 10:22:25 AM CEST Arnaldo Carvalho de Melo wrote:
> Em Wed, Aug 03, 2016 at 10:56:20PM +0200, Milian Wolff escreveu:
> > I hope this helps others. I finally have a working up2date perf on my
> > aarch64 platform and it seems to work form my simple 5min tests so far.
> 
> Ok, that should help people, but it is way convoluted :-\
> 
> How did you obtained your cross compiler environment? Some ready made
> tarball or set of distro packages? I have an ever growing set of perf
> build cointainers that includes a few cross compilers:

The environment was provided to us as a tarball from a customer of ours, who 
probably got that from another subcontractor.

<snip>

    export INSTALLDIR=/usr/${TARGET} && \

^-- is that path potentially special cased in the build file? I mean you don't 
set the sysroot anywhere, nor do you seem to pass special include paths to 
perf. This of course works fine in a docker environment, but for "normal" 
development machines, where you compile and install stuff somewhere in $HOME, 
this won't work at all.

The above wouldn't directly explain the really strange behavior of the feature 
detection though (which enables _everything_ for me).

Bye
-- 
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]