../source/configure: line 15969: PKG_PROG_PKG_CONFIG: command not found

[tonycurtis]

Running configure on master branch (first time after autogen)

90  checking if g++ static flag -static works... no
91  checking if g++ supports -c -o file.o... yes
92  checking if g++ supports -c -o file.o... (cached) yes
93  checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
94  checking dynamic linker characteristics... (cached) GNU/Linux ld.so
95  checking how to hardcode library paths into programs... immediate
96  checking for ANSI C header files... (cached) yes
97  checking for cos in -lm... yes
../source/configure: line 15969: PKG_PROG_PKG_CONFIG: command not found
98  checking for shm_open in -lrt... yes
99  checking whether asprintf is declared... yes
100 checking whether strdupa is declared... yes
101 checking whether basename is declared... yes
102 checking whether CPU_ZERO is declared... yes
103 checking whether CPU_ISSET is declared... yes
104 checking for library containing pthread_create... -lpthread
105 checking whether F_SETOWN_EX is declared... yes
106 checking whether __ppc_get_timebase_freq is declared... no
107 checking sys/platform/ppc.h usability... no
108 checking sys/platform/ppc.h presence... no
109 checking for sys/platform/ppc.h... no
110 checking for compress2 in -lz... yes

[mike-dubman]

yep, this comes from checking for cross-compiler environment.
We compile packages with different crosscompilers during jenkins.
The following autotools code checks if pkg-config exists in crosscompile and trying to use it if underlying lib uses pkg-config service, otherwise in CT env the lib can find native pkg-config and it is bad.(ppc CT will use x86 locations of libs).
We did not find a better way (yet).
Suggestions are welcome, the error can be ignored

PKG_PROG_PKG_CONFIG
PKG_CONFIG="pkg-config"
if test -n "${host}" ; then
   PKG_CONFIG=${host}-${PKG_CONFIG}
fi

[yosefe]

@shamisp - is it being addressed in #59?