FWTS Building on Power8 PowerKVM 3.1.0 (ppc64le)

[Colin Ian King]

On Ubuntu + Debian, libjson0-dev is used. You can see the dependencies
on the debian/control file.

Colin

On 05/03/16 19:04, Deborah McLemore wrote:
> Hi All,
> 
> I am setting up FWTS to run on Power 8 PowerKVM 3.1.0, the configure
> command complains about no json available, but its not clear to me what
> it looks for and what is lacking on this Power 8 Server.
> 
> Any suggestions ?
> 
> [root at localhost fwts]# ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... gcc3
> checking for ar... ar
> checking the archiver (ar) interface... ar
> checking build system type... powerpc64le-unknown-linux-gnu
> checking host system type... powerpc64le-unknown-linux-gnu
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking dependency style of gcc... (cached) gcc3
> checking for flex... flex
> checking lex output file root... lex.yy
> checking lex library... none needed
> checking whether yytext is a pointer... no
> checking for bison... bison -y
> checking how to print strings... printf
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for fgrep... /usr/bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking how to convert powerpc64le-unknown-linux-gnu file names to
> powerpc64le-unknown-linux-gnu format... func_convert_file_noop
> checking how to convert powerpc64le-unknown-linux-gnu file names to
> toolchain format... func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for archiver @FILE support... @
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... no
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/bin/ld -m elf64lppc) supports
> shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for inline... inline
> checking whether gcc and cc understand -c and -o together... yes
> checking for library containing json_object_from_file... no
> configure: error: no available json library
> 
> 
> 
> [root at localhost fwts]# rpm -qa | grep json
> python-jsonpointer-1.0-2.el7_1.ibm.1.noarch
> python-anyjson-0.3.3-3.el7_1.ibm.1.noarch
> json-glib-0.16.0-3.el7_1.ibm.1.ppc64le
> python-jsonpath-rw-1.2.3-2.el7_1.ibm.1.noarch
> python-jsonschema-2.3.0-1.el7_1.ibm.1.noarch
> python-simplejson-3.2.0-1.el7_1.ibm.1.ppc64le
> json-c-0.11-4.el7_1.ibm.2.ppc64le
> rubygem-json-1.7.7-25.el7_1.pkvm3_1_0.2.ppc64le
> rsyslog-mmjsonparse-7.4.7-7.el7_1.1.ibm.1.ppc64le
> python-jsonpatch-1.2-2.el7_1.ibm.1.noarch
> 
> [root at localhost fwts]# rpm -qa | grep gcc
> libgcc-4.8.3-9.el7_1.ibm.3.ppc64le
> gcc-4.8.3-9.el7_1.ibm.3.ppc64le
> 
> [root at localhost fwts]# cat /proc/version
> Linux version 3.18.22-359.el7_1.pkvm3_1_0.4000.1.ppc64le
> (mockbuild at bldple2) (gcc version 4.8.3 20140911 (IBM 4.8.3-9) (GCC) ) #1
> SMP Tue Nov 10 11:07:22 CST 2015
> 
> 
> ================================
> Deb McLemore
> IBM OpenPower - IBM Systems
> (512) 286 9980
> debmc at us.ibm.com
> ipowermc at icloud.com
> ================================
> 
>