* Package: app-admin/setools-3.3.7-r3 * Repository: gentoo * Maintainer: selinux@gentoo.org * USE: elibc_glibc kernel_linux python selinux userland_GNU x86 * FEATURES: sandbox selinux sesandbox * Applying various (Fedora-provided) setools fixes... * 0001-add-setools-seinfo-and-sesearch-python-bindings.patch ... [ ok ] * 0002-setools-should-exit-with-an-error-status-if-it-gets-.patch ... [ ok ] * 0003-Since-we-do-not-ship-neverallow-rules-all-always-fai.patch ... [ ok ] * 0004-Fix-man-pages-and-getoptions.patch ... [ ok ] * 0005-Fix-sepol-calls-to-work-with-latest-libsepol.patch ... [ ok ] * 0006-Changes-to-support-named-file_trans-rules.patch ... [ ok ] * 0007-Remove-unused-variables.patch ... [ ok ] * 0008-Fix-output-to-match-policy-lines.patch ... [ ok ] * Done with patching * Applying various (Gentoo) setool fixes... * 0001-fix-implicit-def-fstat.patch ... [ ok ] * 0002-fix-implicit-defines-from-fedora-patches.patch ... [ ok ] * 0003-make-python-optional-again.patch ... [ ok ] * 0004-support-python3-builds.patch ... [ ok ] * 0005-update-on-py_functions-for-python3.patch ... [ ok ] * 0006-import_submodules_correctly.patch ... [ ok ] * Done with patching * Running eautoreconf in '/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7' ... * Running libtoolize --install --copy --force --automake ... [ ok ] * Running aclocal -I m4 ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ ok ] * Running elibtoolize in: setools-3.3.7/ * Applying portage/1.2.0 patch ... * Applying sed/1.5.6 patch ... configure: loading site script /usr/share/config.site configure: loading site script /usr/share/crossdev/include/site/linux configure: loading site script /usr/share/crossdev/include/site/linux-gnu configure: loading site script /usr/share/crossdev/include/site/i686-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 i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-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 i686-pc-linux-gnu-gcc accepts -g... yes checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed checking dependency style of i686-pc-linux-gnu-gcc... gcc3 checking how to run the C preprocessor... i686-pc-linux-gnu-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 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 for i686-pc-linux-gnu-gcc option to accept ISO C99... -std=gnu99 checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++ checking whether we are using the GNU C++ compiler... yes checking whether i686-pc-linux-gnu-g++ accepts -g... yes checking dependency style of i686-pc-linux-gnu-g++... gcc3 checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by i686-pc-linux-gnu-gcc -std=gnu99... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/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 how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r checking for i686-pc-linux-gnu-objdump... i686-pc-linux-gnu-objdump checking how to recognize dependent libraries... pass_all checking for i686-pc-linux-gnu-dlltool... no checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar checking for archiver @FILE support... @ checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib checking command to parse /usr/bin/nm -B output from i686-pc-linux-gnu-gcc -std=gnu99 object... ok checking for sysroot... no checking for i686-pc-linux-gnu-mt... no checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... yes checking for objdir... .libs checking if i686-pc-linux-gnu-gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no checking for i686-pc-linux-gnu-gcc -std=gnu99 option to produce PIC... -fPIC -DPIC checking if i686-pc-linux-gnu-gcc -std=gnu99 PIC flag -fPIC -DPIC works... yes checking if i686-pc-linux-gnu-gcc -std=gnu99 static flag -static works... yes checking if i686-pc-linux-gnu-gcc -std=gnu99 supports -c -o file.o... yes checking if i686-pc-linux-gnu-gcc -std=gnu99 supports -c -o file.o... (cached) yes checking whether the i686-pc-linux-gnu-gcc -std=gnu99 linker (/usr/i686-pc-linux-gnu/bin/ld) 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... yes checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E checking for ld used by i686-pc-linux-gnu-g++... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking for i686-pc-linux-gnu-g++ option to produce PIC... -fPIC -DPIC checking if i686-pc-linux-gnu-g++ PIC flag -fPIC -DPIC works... yes checking if i686-pc-linux-gnu-g++ static flag -static works... yes checking if i686-pc-linux-gnu-g++ supports -c -o file.o... yes checking if i686-pc-linux-gnu-g++ supports -c -o file.o... (cached) yes checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether ln -s works... yes checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking for bison... bison -y checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking whether byte ordering is bigendian... no checking for rand_r... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for debugging support... disabled checking for how to link against libraries... shared checking for profiling support... disabled checking for swig... /usr/bin/swig checking for python... /usr/bin/python checking for the distutils Python package... yes checking for Python include path... -I/usr/include/python2.7 checking for Python library path... ('-L/usr/lib/python2.7', '-lpython2.7') checking for Python site-packages path... /usr/lib/python2.7/site-packages checking python extra libraries... ('', '-lpthread -ldl -lutil') checking python extra linking flags... -Xlinker -export-dynamic checking consistency of all components of python development environment... no configure: error: Could not link test program to Python. Maybe the main Python library has been installed in some non-standard library path. If so, pass it to configure, via the LDFLAGS environment variable. Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib" ============================================================================ ERROR! You probably have to install the development version of the Python package for your distribution. The exact name of this package varies among them. ============================================================================ !!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7/config.log * ERROR: app-admin/setools-3.3.7-r3 failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 85: Called src_configure * environment, line 7150: Called econf '--with-java-prefix=/etc/java-config-2/current-system-vm' '--disable-selinux-check' '--disable-bwidget-check' '--enable-swig-python' '--disable-swig-java' '--disable-swig-tcl' '--disable-gui' '--disable-debug' * phase-helpers.sh, line 467: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of `emerge --info '=app-admin/setools-3.3.7-r3'`, * the complete build log and the output of `emerge -pqv '=app-admin/setools-3.3.7-r3'`. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info /usr/lib/portage/bin/isolated-functions.sh: line 214: wait: `econf failed': not a pid or valid job spec * The complete build log is located at '/var/tmp/portage/app-admin/setools-3.3.7-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-admin/setools-3.3.7-r3/temp/environment'. * Working directory: '/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7' * S: '/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7'