it seems like the latest version of autoconf os 2.69 which I have and my OS info is below. Thank you guys for the help. My current work around to skip the unit testing is tedious and I would rather not skip it if possible.
autoconf (GNU Autoconf) 2.69 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+/Autoconf: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. pi@ocfPi:~/iot/1.3_iotivity/iotivity $ sudo apt-get install autoconf Reading package lists... Done Building dependency tree Reading state information... Done autoconf is already the newest version. autoconf set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 74 not upgraded. pi@ocfPi:~/iot/1.3_iotivity/iotivity $ uname -a Linux ocfPi 4.9.24+ #993 Wed Apr 26 17:56:54 BST 2017 armv6l GNU/Linux ________________________________ From: Nash, George <[email protected]> Sent: Friday, July 14, 2017 9:25:58 AM To: Mats Wichmann; [email protected]; rami alshafi; [email protected] Subject: RE: [dev] Raspberry pi build error The area you are failing in is when the code is trying to build google test. It uses gnu auto tools to generate a make file then runs the make file to build the google test libraries. Check that you have the latest autoconf installed. George From: [email protected] [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Thursday, July 13, 2017 6:47 PM To: [email protected]; rami alshafi <[email protected]>; [email protected] Subject: Re: [dev] Raspberry pi build error your OS info would be more helpful given the type of problem (and autoconf version). and don't worry if you need to turn off unit tests. On July 13, 2017 6:58:42 PM MDT, rami alshafi <[email protected]<mailto:[email protected]>> wrote: I keep running to this error when building IoTivity (1.3-rel branch commit 5bebafb64d by George Nash: [IOT-2207]) on the raspberry pi which seems to be related to unit testing. my workaround so far is to skip building unit testing. *** Checking for installation of google unit test %s *** 1.7.0 Unzipping to : /home/pi/iot/1.3_iotivity/iotivity/extlibs/gtest/googletest-release-1.7.0 Unpacking /home/pi/iot/1.3_iotivity/iotivity/extlibs/gtest/release-1.7.0.zip ... Configuring google unit test Configuring using [/home/pi/iot/1.3_iotivity/iotivity/extlibs/gtest/googletest-release-1.7.0/autoreconf -i] ... configure.ac:30: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/bin/autoconf failed with exit status: 1 Unknown error information about my pi (1 B+) is below pi@ocfPi:~/iot/1.3_iotivity/iotivity<mailto:pi@ocfPi:~/iot/1.3_iotivity/iotivity> $ cat /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) BogoMIPS : 697.95 Features : half thumb fastmult vfp edsp java tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7 Hardware : BCM2835 Revision : 0010 Serial : 00000000a1fa6733 Thanks, -Rami -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
