Deepstream-test1: configure: error: Python libs not found Windows requires Python modules to be explicitly linked to libpython. configure failed

OS Ubuntu 20.04 LTS, Python 3.8.2, Deepstream 5

I get the following error when I run the command $./autogen.sh PYTHON=python3

  • passing argument PYTHON=python3 to configure
  • options passed to configure: PYTHON=python3
  • check for build tools
    checking for autoconf >= 2.60 … found 2.69, ok.
    checking for automake >= 1.10 … found 1.16.1, ok.
    checking for libtoolize >= 1.5.0 … found 2.4.6, ok.
    checking for pkg-config >= 0.8.0 … found 0.29.1, ok.
  • running libtoolize --copy --force…
    libtoolize: putting auxiliary files in ‘.’.
    libtoolize: copying file ‘./ltmain.sh’
    libtoolize: putting macros in ‘m4’.
    libtoolize: copying file ‘m4/libtool.m4’
    libtoolize: copying file ‘m4/ltoptions.m4’
    libtoolize: copying file ‘m4/ltsugar.m4’
    libtoolize: copying file ‘m4/ltversion.m4’
    libtoolize: copying file ‘m4/lt~obsolete.m4’
    libtoolize: Consider adding ‘AC_CONFIG_MACRO_DIRS([m4])’ to configure.ac,
    libtoolize: and rerunning libtoolize and aclocal.
  • running aclocal -I m4 -I common/m4 …
  • running autoheader …
  • running autoconf …
  • running automake -a -c -Wno-portability…
    configure.ac:47: installing ‘./compile’
    configure.ac:13: installing ‘./missing’
    gi/overrides/Makefile.am: installing ‘./depcomp’
    plugin/Makefile.am:3: warning: ‘INCLUDES’ is the old name for ‘AM_CPPFLAGS’ (or ‘*_CPPFLAGS’)
  • running configure …
    ./configure default flags: --enable-maintainer-mode
    ./configure external flags: PYTHON=python3

checking build system type… x86_64-pc-linux-gnu
checking host system type… x86_64-pc-linux-gnu
checking target system type… x86_64-pc-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… no
checking for mawk… mawk
checking whether make sets (MAKE)... yes checking whether make supports nested variables... yes checking whether UID '1000' is supported by ustar format... yes checking whether GID '1000' is supported by ustar format... yes checking how to create a ustar tar archive... gnutar checking nano version... 0 (release) checking whether to enable maintainer-specific portions of Makefiles... yes checking whether make supports nested variables... (cached) yes checking how to print strings... printf checking whether make supports the include directive... yes (GNU style) 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 whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /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 how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop checking how to convert x86_64-pc-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 ar... ar 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 a working dd... /bin/dd checking how to truncate binary pipes... /bin/dd bs=4096 count=1 checking for mt... mt checking if mt 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... 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 for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... no 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 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 whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking for gcc option to accept ISO C99... none needed checking for gcc option to accept ISO Standard C... (cached) none needed checking for python version... 3.8 checking for python platform... linux checking for python script directory... {prefix}/lib/python3.8/site-packages
checking for python extension module directory… {exec_prefix}/lib/python3.8/site-packages checking for python >= 2.7... checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GST... yes checking for PYGOBJECT... yes okay checking for headers required to compile python extensions... found checking for pygobject overrides directory... {exec_prefix}/lib/python3.8/site-packages/gi/overrides
checking for GST… yes
configure: Using /usr/local/lib/gstreamer-1.0 as the plugin install location
checking for PYGOBJECT… yes
checking for libraries required to embed python… no
configure: error: Python libs not found. Windows requires Python modules to be explicitly linked to libpython.
configure failed

I have installed installed python3-dev and libpython3-dev and they are up to date. Could you please suggest a solution to this? Thank you.

Hi @pooja.p,
DeepStream 5.0 support Ubuntu 18.04 and python 3.6.
To avoid any unexpected issue, could you use DeepStream 5.0 support Ubuntu 18.04 and python 3.6 system?
If you don’t want to re-install your Linux system, you could use DeepStream docker - https://docs.nvidia.com/metropolis/deepstream/dev-guide/index.html#page/DeepStream%20Plugins%20Development%20Guide/deepstream_plugin_docker.html

Thanks!

Hey @mchi ! I do not want to reinstall my system since I have a lot of other applications and projects on it. Theoretically Ubuntu 20 shouldn’t be an issue since its LTS. So is python. Moreover, since I’m studying deepstream for the purpose of integrating it in my application from a developer’s perspective, using a docker file doesn’t help me understand the working of deepstream, compared to working on it locally. Is there no other way to resolve this issue?