The line where you get an error has not been modified by this commit, so it is not obvious that it is related. Please try the following:
1) Make sure you are using a fresh clone of the source code repository. 2) Use a reasonably up-to-date Linux distribution (I haven't tested on anything older than Ubuntu 14.04). regards, Anders Widell On 01/04/2017 08:20 AM, Nagendra Kumar wrote: > Hi Anders, > I am getting the following error. Is it related to the build changes: > > 1. Bootstap worked fine. > 2. ./configure --enable-tipc=yes > checking build system type... x86_64-suse-linux-gnu > checking host system type... x86_64-suse-linux-gnu > checking target system type... x86_64-suse-linux-gnu > 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 for style of include used by make... GNU > checking for gcc... gcc > 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 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... /usr/bin/grep > checking for egrep... /usr/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 minix/config.h usability... no > checking minix/config.h presence... no > checking for minix/config.h... no > checking whether it is safe to define __EXTENSIONS__... yes > checking whether to build with rpath enabled... yes > checking for a sed that does not truncate output... /usr/bin/sed > 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 for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for ar... ar > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > 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... yes > 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 elf_x86_64) 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... no > checking whether to enable the make rpm target... yes > checking whether to enable the Python AIS bindings... no > checking whether to enable the Java AIS interface mapping... no > checking whether to enable the AM4J agent... no > checking whether to use TIPC as the transport... yes > ./configure: line 11217: syntax error near unexpected token `SYSTEMD,' > ./configure: line 11217: `PKG_CHECK_MODULES(SYSTEMD, systemd, > enable_systemd=yes, enable_systemd=no)' > > > Thanks > -Nagu >> -----Original Message----- >> From: Anders Widell [mailto:[email protected]] >> Sent: 03 January 2017 01:20 >> To: [email protected] >> Subject: [devel] A new year, a new build system >> >> Hi all! >> >> I hope you have all been able to take some time off during the Christmas and >> New year holidays. >> >> With this mail I want to give you a heads-up to the fact that ticket [#2084] >> has been pushed. This means that OpenSAF now uses a non-recursive >> automake configuration, which brings many advantages - among other >> things it removes the artificial limitations on the parallelism of a >> traditional >> recursive make. The amount of parallelism you can utilise during the build >> process is now (almost) only limited by the number of CPU cores and the >> amount of memory your build server is equipped with. During the conversion >> to a non-recursive automake configuration, the autotools configuration files >> were also cleaned up. >> The result is that bootstrapping and configuration is also faster after this >> change. So in summary, the OpenSAF build time should see a significant >> improvement. >> >> Since this is a fairly large change to our build system, I expect that there >> can >> be some problems initially. Please help out to verify that the build works >> and >> produces the correct result for the configuration that you are using. The >> code freeze for OpenSAF 5.2 is planned for 2017-02-24, so there should be >> plenty of time to weed out any potential problem. >> >> Looking forwards, I should mention that we are also considering to move the >> OpenSAF code repository from Mercurial to GIT. You may have noticed that >> there is in fact already an OpenSAF GIT repository available. Keep in mind >> that we haven't switched yet though, so our main repository is still the old >> Mercurial one and that is what you should use. The GIT repository is at this >> point there just for testing purposes. >> >> regards, >> >> Anders Widell >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most engaging >> tech sites, SlashDot.org! http://sdm.link/slashdot >> _______________________________________________ >> Opensaf-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/opensaf-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
