Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 343526 Details for
Bug 463606
app-crypt/p11-kit-0.17.4 should depend on >=dev-libs/libtasn1-2.14
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Build log
build.log (text/plain), 9.53 KB, created by
nvinson234
on 2013-03-28 12:56:49 UTC
(
hide
)
Description:
Build log
Filename:
MIME Type:
Creator:
nvinson234
Created:
2013-03-28 12:56:49 UTC
Size:
9.53 KB
patch
obsolete
> * Package: app-crypt/p11-kit-0.17.4 > * Repository: gentoo > * Maintainer: crypto@gentoo.org > * USE: amd64 elibc_glibc kernel_linux userland_GNU > * FEATURES: preserve-libs sandbox >>>> Unpacking source... >>>> Unpacking p11-kit-0.17.4.tar.gz to /var/tmp/portage/app-crypt/p11-kit-0.17.4/work >>>> Source unpacked in /var/tmp/portage/app-crypt/p11-kit-0.17.4/work >>>> Preparing source in /var/tmp/portage/app-crypt/p11-kit-0.17.4/work/p11-kit-0.17.4 ... > * Running elibtoolize in: p11-kit-0.17.4/ > * Applying portage/1.2.0 patch ... > * Applying sed/1.5.6 patch ... > * Applying as-needed/2.4.2 patch ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/app-crypt/p11-kit-0.17.4/work/p11-kit-0.17.4 ... >>>> Working in BUILD_DIR: "/var/tmp/portage/app-crypt/p11-kit-0.17.4/work/p11-kit-0.17.4_build" > * econf: updating p11-kit-0.17.4/config.sub with /usr/share/gnuconfig/config.sub > * econf: updating p11-kit-0.17.4/config.guess with /usr/share/gnuconfig/config.guess >/var/tmp/portage/app-crypt/p11-kit-0.17.4/work/p11-kit-0.17.4/configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-silent-rules --disable-dependency-tracking --docdir=/usr/share/doc/p11-kit-0.17.4 --disable-debug >checking for x86_64-pc-linux-gnu-gcc... x86_64-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 x86_64-pc-linux-gnu-gcc accepts -g... yes >checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed >checking how to run the C preprocessor... x86_64-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 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 dependency style of x86_64-pc-linux-gnu-gcc... none >checking whether build environment is sane... yes >checking whether to enable maintainer-specific portions of Makefiles... yes >checking whether make supports nested variables... yes >checking build system type... x86_64-pc-linux-gnu >checking host system type... x86_64-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 x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld >checking if the linker (/usr/x86_64-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 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/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r >checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump >checking how to recognize dependent libraries... pass_all >checking for x86_64-pc-linux-gnu-dlltool... no >checking for dlltool... no >checking how to associate runtime and link libraries... printf %s\n >checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar >checking for archiver @FILE support... @ >checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip >checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib >checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok >checking for sysroot... no >checking for x86_64-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 x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no >checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC -DPIC >checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes >checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes >checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes >checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... (cached) yes >checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/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 whether NLS is requested... yes >checking for msgfmt... /usr/bin/msgfmt >checking for gmsgfmt... /usr/bin/gmsgfmt >checking for xgettext... /usr/bin/xgettext >checking for msgmerge... /usr/bin/msgmerge >checking for ld used by GCC... /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64 >checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) is GNU ld... yes >checking for shared library run path origin... done >checking for CFPreferencesCopyAppValue... no >checking for CFLocaleCopyCurrent... no >checking for GNU gettext in libc... yes >checking whether to use NLS... yes >checking where the gettext function comes from... libc >checking for x86_64-pc-linux-gnu-gcc... (cached) x86_64-pc-linux-gnu-gcc >checking whether we are using the GNU C compiler... (cached) yes >checking whether x86_64-pc-linux-gnu-gcc accepts -g... (cached) yes >checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed >checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E >checking whether x86_64-pc-linux-gnu-gcc and cc understand -c and -o together... yes >checking for CFPreferencesCopyAppValue... (cached) no >checking for CFLocaleCopyCurrent... (cached) no >checking for GNU gettext in libc... (cached) yes >checking whether to use NLS... yes >checking where the gettext function comes from... libc >checking for win32... no >checking whether byte ordering is bigendian... no >checking for stdbool.h that conforms to C99... yes >checking for _Bool... yes >checking for pthread_mutex_lock in -lpthread... yes >checking for library containing dlopen... -ldl >checking for library containing nanosleep... none required >checking for struct dirent.d_type... yes >checking for getprogname... no >checking for getexecname... no >checking for basename... yes >checking for mkstemp... yes >checking for mkdtemp... yes >checking for strnstr... no >checking for memdup... no >checking for strndup... yes >checking for asprintf... yes >checking for vasprintf... yes >checking for vsnprintf... yes >checking for timegm... yes >checking for gmtime_r... yes >checking whether program_invocation_short_name is declared... no >checking whether program_invocation_short_name is available... yes >checking whether __progname is declared... no >checking for dgettext in -lintl... no >checking for x86_64-pc-linux-gnu-pkg-config... /usr/bin/x86_64-pc-linux-gnu-pkg-config >checking pkg-config is at least version 0.9.0... yes >checking for LIBTASN1... no >configure: error: libtasn1 not found. Building without it results in significant loss of functionality. To proceed use --without-libtasn1 > >!!! Please attach the following file when seeking support: >!!! /var/tmp/portage/app-crypt/p11-kit-0.17.4/work/p11-kit-0.17.4_build/config.log > * ERROR: app-crypt/p11-kit-0.17.4 failed (configure phase): > * econf failed > * > * Call stack: > * ebuild.sh, line 93: Called src_configure > * environment, line 3056: Called autotools-utils_src_configure > * environment, line 569: Called econf '--docdir=/usr/share/doc/p11-kit-0.17.4' '--disable-debug' > * phase-helpers.sh, line 521: Called die > * The specific snippet of code: > * die "econf failed" > * > * If you need support, post the output of `emerge --info '=app-crypt/p11-kit-0.17.4'`, > * the complete build log and the output of `emerge -pqv '=app-crypt/p11-kit-0.17.4'`. > * The complete build log is located at '/var/tmp/portage/app-crypt/p11-kit-0.17.4/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/portage/app-crypt/p11-kit-0.17.4/temp/environment'. > * Working directory: '/var/tmp/portage/app-crypt/p11-kit-0.17.4/work/p11-kit-0.17.4_build' > * S: '/var/tmp/portage/app-crypt/p11-kit-0.17.4/work/p11-kit-0.17.4'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 463606
: 343526 |
343528