Re: cross compiling perf

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

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

On Monday, June 20, 2016 9:56:09 AM CEST Wangnan (F) wrote:
> On 2016/6/17 19:00, Arnaldo Carvalho de Melo wrote:
> > Adding some folks to the CC list, that either worked on the make
> > infrastructure or that I know works with cross compiling environments,
> > maybe they can help.
> > 
> > More below.
> > 
> > Em Fri, Jun 17, 2016 at 11:49:28AM +0200, Milian Wolff escreveu:
> >> On Donnerstag, 16. Juni 2016 13:11:11 CEST Arnaldo Carvalho de Melo 
wrote:
> >>> Em Wed, Jun 15, 2016 at 04:24:52PM +0200, Milian Wolff escreveu:
> >>>> I'm trying to compile a more modern version of the user-space perf
> >>>> tools
> >>>> for an arm64 embedded target. So far, no cigar.
> >>>> 
> >>>> Neither tools/build/Documentation nor
> >>>> tools/perf/Documentation/Build.txt
> >>>> explain how this should be done. Right now, I'm trying the following
> >>>> from
> >>>> an SDK with an environment that already sets up CC, CFLAGS etc. pp.
> >>>> 
> >>>> [SDK] ~/milian/linux/tools/perf$ make ARCH=arm64
> >>>> CROSS_COMPILE=/home/sdk/
> >>>> sysroots/x86_64-oesdk-linux/usr/bin/aarch64-gnu-linux/aarch64-gnu-linux
> >>>> -
> >>>> CFLAGS="--sysroot=/home/sdk/sysroots/aarch64-gnu-linux
> >>>> -I/home/milian/target- prefix/include -L/home/milian/target-prefix/lib
> >>>> $CFLAGS"
> >>>> 
> >>>>    BUILD:   Doing 'make -j8' parallel build
> >>>> 
> >>>> Auto-detecting system features:
> >>>> ...                         dwarf: [ OFF ]
> >>>> ...            dwarf_getlocations: [ OFF ]
> >>>> ...                         glibc: [ OFF ]
> >>>> ...                          gtk2: [ OFF ]
> >>>> ...                      libaudit: [ OFF ]
> >>>> ...                        libbfd: [ OFF ]
> >>>> ...                        libelf: [ OFF ]
> >>>> ...                       libnuma: [ OFF ]
> >>>> ...        numa_num_possible_cpus: [ OFF ]
> >>>> ...                       libperl: [ OFF ]
> >>>> ...                     libpython: [ OFF ]
> >>>> ...                      libslang: [ OFF ]
> >>>> ...                     libcrypto: [ OFF ]
> >>>> ...                     libunwind: [ OFF ]
> >>>> ...            libdw-dwarf-unwind: [ OFF ]
> >>>> ...                          zlib: [ OFF ]
> >>>> ...                          lzma: [ OFF ]
> >>>> ...                     get_cpuid: [ OFF ]
> >>>> ...                           bpf: [ OFF ]
> >>>> 
> >>>> config/Makefile:272: *** No gnu/libc-version.h found, please install
> >>>> glibc-
> >>>> dev[el].  Stop
> 
> I think this error message is missleading. Let's see source code:
> 
> ifdef NO_LIBELF
>    ...
> else
>    ifeq ($(feature-libelf), 0)
>      ifeq ($(feature-glibc), 1)
>        LIBC_SUPPORT := 1
>      endif
>      ifeq ($(BIONIC),1)
>        LIBC_SUPPORT := 1
>      endif
>      ifeq ($(LIBC_SUPPORT),1)
>        ...
>      else
>        ifneq ($(filter s% -static%,$(LDFLAGS),),)
>          msg := $(error No static glibc found, please install glibc-static);
> else
>          msg := $(error No gnu/libc-version.h found, please install
> glibc-dev[el]);
>        endif
>      endif
>    else
>      ...
>    endif # libelf support
> endif # NO_LIBELF
> 
> So the 'libc-version.h' error message really means the failure of
> feature-glibc detector.
> There's many reasons cause libc detector fail. 'libc-version.h' in error
> message provides
> wrong clue, lead user to check this file instead of checking feature
> check result.

OK, so if it's the wrong clue, can you tell me what else to look at then?

I'm seeing

$ echo $CC
aarch64-gnu-linux-gcc --sysroot=/home/yocto/SDK/E013/sdk/sysroots/aarch64-gnu-
linux
$ echo $PWD
path/to/linux/tools/build/feature
$ $CC test-glib.c
$ echo $?
0

The above looks good, but from a make run I get:

$ cat test-glibc.make.output 
test-glibc.c:1:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.

Can I somehow figure out how it tries to compile the test-glib.c file? I.e. 
can I invoke "make" in a verbose mode that outputs all commands?

Thanks
-- 
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 --]