DUO with UNIX compile failure

kcunningham — Mon, 07 Mar 2022 18:12:10 GMT

First I’m new to DOU.

I’m attempting to install DOU_UNIX on one of my AIX platforms. I have installed it on many others but I’m dealing with a compile issue. All of thre prereqs have been installed without any issues. When I attempt to run…

Nothing shows in the config.log as to the error and/or reason.

./configure --prefix=/usr && make && sudo make install

Output:
checking for a BSD-compatible install… autotools/install-sh -c
checking whether build environment is sane… yes
checking for a thread-safe mkdir -p… autotools/install-sh -c -d
checking for gawk… no
checking for mawk… no
checking for nawk… nawk
checking whether make sets $(MAKE)… yes
checking whether make supports nested variables… yes
checking whether to enable maintainer-specific portions of Makefiles… no
checking build system type… powerpc-ibm-aix7.1.0.0
checking host system type… powerpc-ibm-aix7.1.0.0
configure: autobuild project… duo_unix
configure: autobuild revision… 1.11.5
configure: autobuild hostname… lsfappdev
configure: autobuild timestamp… 20220307T180900Z
checking for style of include used by make… GNU
checking for gcc… no
checking for cc… cc
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… no
checking whether cc accepts -g… yes
checking for cc option to accept ISO C89… -qlanglvl=extc89
checking dependency style of cc -qlanglvl=extc89… xlc
checking how to run the C preprocessor… cc -qlanglvl=extc89 -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 we are using the GNU C compiler… (cached) no
checking whether cc accepts -g… (cached) yes
checking for cc option to accept ISO C89… (cached) -qlanglvl=extc89
checking dependency style of cc -qlanglvl=extc89… (cached) xlc
checking whether cc -qlanglvl=extc89 and cc understand -c and -o together… yes
checking how to print strings… print -r
checking for a sed that does not truncate output… /usr/bin/sed
checking for fgrep… /usr/bin/grep -F
checking for non-GNU ld… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… no
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… 786432
checking whether the shell understands some XSI constructs… yes
checking whether the shell understands “+=”… no
checking how to convert powerpc-ibm-aix7.1.0.0 file names to powerpc-ibm-aix7.1.0.0 format… func_convert_file_noop
checking how to convert powerpc-ibm-aix7.1.0.0 file names to toolchain format… func_convert_file_noop
checking for /usr/bin/ld option to reload object files… -r
checking for objdump… no
checking how to recognize dependent libraries… pass_all
checking for dlltool… no
checking how to associate runtime and link libraries… print -r –
checking for ar… ar
checking for archiver @FILE support… no
checking for strip… strip
checking for ranlib… ranlib
checking command to parse /usr/bin/nm -B output from cc -qlanglvl=extc89 object… ok
checking for sysroot… no
checking for mt… mt
checking if mt is a manifest tool… no
checking for dlfcn.h… yes
checking for objdir… .libs
checking for cc -qlanglvl=extc89 option to produce PIC… -DPIC
checking if cc -qlanglvl=extc89 PIC flag -DPIC works… yes
checking if cc -qlanglvl=extc89 static flag -bnso -bI:/lib/syscalls.exp works… no
checking if cc -qlanglvl=extc89 supports -c -o file.o… yes
checking if cc -qlanglvl=extc89 supports -c -o file.o… (cached) yes
checking whether the cc -qlanglvl=extc89 linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… aix7.1.0.0 ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… no
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… no
checking if -fstack-protector and -fstack-protector-all are supported… yes
configure: -fstack-protector disabled on AIX
checking whether byte ordering is bigendian… yes
checking for an ANSI C-conforming const… yes
checking for int64_t… yes
checking for ANSI C header files… (cached) yes
checking for inttypes.h… (cached) yes
checking limits.h usability… yes
checking limits.h presence… yes
checking for limits.h… yes
checking for memory.h… (cached) yes
checking for stdint.h… (cached) yes
checking for stdlib.h… (cached) yes
checking for string.h… (cached) yes
checking for unistd.h… (cached) yes
checking for pkg-config… no
checking for openssl/ssl.h in /usr/local/ssl… no
checking for openssl/ssl.h in /usr/lib/ssl… no
checking for openssl/ssl.h in /usr/ssl… no
checking for openssl/ssl.h in /usr/pkg… no
checking for openssl/ssl.h in /usr/local… no
checking for openssl/ssl.h in /usr… yes
checking whether compiling and linking against OpenSSL works… yes
checking whether X509_TEA_set_state runs… no
configure: Using privilege separation user “sshd”
configure: Using libdir “${exec_prefix}/lib”
checking for memcpy… yes
checking for memset… yes
checking for sysconf… yes
checking for getaddrinfo… yes
checking for open64… yes
checking for fopen64… yes
checking for explicit_bzero… no
checking for memset_s… yes
checking for asprintf… no
checking for getgrouplist… no
checking for strlcpy… no
checking for vsyslog… no
checking for strnlen… yes
checking for library containing inet_ntoa… none required
checking for library containing socket… none required
checking that generated files are newer than configure… done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating compat/Makefile
config.status: creating duo_unix_support/Makefile
config.status: creating lib/Makefile
config.status: creating lib/libduo.pc
config.status: creating login_duo/Makefile
config.status: creating pam_duo/Makefile
config.status: creating tests/Makefile
config.status: creating tests/unity_tests/Makefile
config.status: creating tests/unity_tests/Unity-2.4.3/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
make all-recursive
Making all in compat
Target “all” is up to date.
Making all in lib
source=‘util.c’ object=‘util.lo’ libtool=yes DEPDIR=.deps depmode=xlc /bin/sh …/autotools/depcomp /bin/sh …/libtool --tag=CC --mode=compile cc -qlanglvl=extc89 -DHAVE_CONFIG_H -I. -I… -I…/compat -I/usr/include -g -c -o util.lo util.c
libtool: compile: cc -qlanglvl=extc89 -DHAVE_CONFIG_H -I. -I… -I…/compat -I/usr/include -g -c util.c -Wp,-qmakedep=gcc,-MF.deps/util.TPlo -DPIC -o .libs/util.o
“util.c”, line 151.13: 1506-046 (S) Syntax error.
“util.c”, line 151.16: 1506-045 (S) Undeclared identifier Offset.
make: The error code from the last command is 1.

Stop.
make: The error code from the last command is 1.

Stop.
make: The error code from the last command is 2.

Stop.

Re: DUO with UNIX compile failure

Amy2 — Thu, 10 Mar 2022 20:52:38 GMT

Hi @kcunningham, welcome to the Duo Community! Thanks for sharing your question here. Since you mention having all of the prerequisites installed, you should be good from that perspective. Have you tried any of the steps in our Guide to troubleshooting IBM AIX and Duo Unix configuration issues? That’s usually a good place to start. If you’re still having trouble, I recommend contacting Duo Support for further help with this issue. They’ll be able to assist you.

topic DUO with UNIX compile failure in Managing Users

DUO with UNIX compile failure

Re: DUO with UNIX compile failure