sockperf build errors on Linux on IBM POWER systems
Hari N Reddy
Hi,
I am trying to compile sockperf on an IBM Power system (power7+) which is powerpc based running Linux and I am getting the following errors.
Has sockperf been ported to Linux on POWER systems?
the config command I am using is:
configure --host=powerpc
The log of configure and make are listed below:
Thanks for any pointers to get past this,
Hari
[root@p131n01 sockperf-2.5.241]# uname -a
Linux p131n01.pbm.ihost.com 2.6.32-431.el6.ppc64 #1 SMP Sun Nov 10 22:17:43 EST 2013 ppc64 ppc64 ppc64 GNU/Linux
[root@p131n01 sockperf-2.5.241]# cat /proc/version
Linux version 2.6.32-431.el6.ppc64 (mock...@ppc-003.build.bos.redhat.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-4) (GCC) ) #1 SMP Sun Nov 10 22:17:43 EST 2013
[root@p131n01 sockperf-2.5.241]# cat /etc/red*
Red Hat Enterprise Linux Server release 6.5 (Santiago)
cat /proc/cpuinfo | more
processor : 0
cpu : POWER7 (architected), altivec supported
clock : 4228.000000MHz
revision : 2.1 (pvr 004a 0201)
configure output
checking build system type... powerpc64-unknown-linux-gnu
checking host system type... powerpc64-unknown-linux-gnu
checking target system type... powerpc-unknown-none
configure:
configure: release 2.5.241
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... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for doxygen... no
checking for gcc... gcc
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 how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -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 arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking for ANSI C header files... (cached) yes
checking for clock_gettime in -lrt... yes
checking for pthread_create in -lpthread... yes
checking for dlsym in -ldl... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating src/Makefile
config.status: creating tools/Makefile
config.status: creating tests/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
make output
make all-recursive
make[1]: Entering directory `/data/sockperf/sockperf-2.5.241'
Making all in src
make[2]: Entering directory `/data/sockperf/sockperf-2.5.241/src'
g++ -DHAVE_CONFIG_H -I. -I.. -I. -Werror -Wall --param inline-unit-growth=200 -D__LINUX__ -DVERSION=2.5.241 -O3 -DNDEBUG -MT Client.o -MD -MP -MF .deps/Client.Tpo -c -o Client.o Client.cpp
In file included from Client.cpp:34:
ticks_os.h: In member function ‘int PongModeNormal::msg_sendto(int)’:
ticks_os.h:100: error: impossible register constraint in ‘asm’
make[2]: *** [Client.o] Error 1
make[2]: Leaving directory `/data/sockperf/sockperf-2.5.241/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/sockperf/sockperf-2.5.241'
make: *** [all] Error 2
Thanks and regards,
Hari
Hari N Reddy
ISV HPC Technical Consultant
IBM Systems & Technology Group, System Software
720-396-7922 (T/L 938-7922)
hnr...@us.ibm.com
Avner Ben Hanoch
Thanks Hari,
Sockperf was not ported to PPC yet. It seems that your problem is easy for solving (missing rdtsc in your platform). We recently got similar fix for ARM platform. See the patch in comment #14 in https://code.google.com/p/sockperf/issues/detail?id=47 (and perhaps there was something there for configure.ac too). Unfortunately, that patch was not entirely completed eventually (I think missing ifdef in additional place).
We don’t have compilation environment for ARM neither for PPC; hence, such fixes rely on your code and your tests.
You are encouraged to complete it for ARM and/or for PPC. The fix should be quite simple.
If you want you can send us the equivalent of #if defined(__arm__) we’ll be able to insert it to the code and leave the check for you (However, notice that as said something small was not completed even for ARM).
At any case, if you want to continue with this subject, I suggest that you open an issue in sockperf’s issues system https://code.google.com/p/sockperf/issues/list
Avner
--
You received this message because you are subscribed to the Google Groups "sockperf-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
sockperf-discu...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.