Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 505164 - app-crypt/p11-kit-0.20.2 - configure:17081: error: could not find. Use --with-trust-paths=/path to set, or --without-trust-paths to disable
Summary: app-crypt/p11-kit-0.20.2 - configure:17081: error: could not find. Use --with...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: Normal normal (vote)
Assignee: Crypto team [DISABLED]
URL: http://forums.gentoo.org/viewtopic-p-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-20 12:53 UTC by jan vereecke
Modified: 2014-03-24 11:53 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
config.log (config.log,93.05 KB, text/plain)
2014-03-20 13:00 UTC, jan vereecke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jan vereecke 2014-03-20 12:53:17 UTC
emerge I try to compile the ebuild app-crypt/p11-kit-0.20.2 with use flag 'trust' (the error does not happen using 

 During configuration file, I get the following error: 

 checking for trust module paths... configure: error: could not find. Use --with-trust-paths=/path to set, or --without-trust-paths to disable. 

When I run the ebuild:
ebuild /mnt/portage/portage/app-crypt/p11-kit/p11-kit-0.20.2.ebuild prepare
ebuild /mnt/portage/portage/app-crypt/p11-kit/p11-kit-0.20.2.ebuild configure

The same error happens

when I run 
ebuild /mnt/portage/portage/app-crypt/p11-kit/p11-kit-0.20.2.ebuild prepare
cd /var/tmp/portage/app-crypt/p11-kit-0.20.2/work/p11-kit-0.20.2 
 # next copy and paste the command from the output from ebuild ... configure 
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-silent-rules --disable-dependency-tracking --enable-trust-module --disable-debug --with-libtasn1

The command succeeds

Reproducible: Always

Steps to Reproduce:
1.USE="asn1 trust" emerge app-crypt/p11-kit-0.20.2
2.
3.
Actual Results:  
configure fails. the last lines are: 


checking for LIBTASN1... yes
checking for LIBFFI... yes
checking if trust module is enabled... yes
checking for trust module paths... configure: error: could not find. Use --with-trust-paths=/path to set, or --without-trust-paths to disable


Expected Results:  
The command should succeed in the same way manual execution of 
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-silent-rules --disable-dependency-tracking --enable-trust-module --disable-debug --with-libtasn1
succeeds:

checking for LIBTASN1... yes
checking for LIBFFI... yes
checking if trust module is enabled... yes
checking for trust module paths... /etc/ssl/certs/ca-certificates.crt
checking for gtkdoc-check... no
checking for gtkdoc-rebase... /usr/bin/gtkdoc-rebase
checking for gtkdoc-mkpdf... no
checking for gtkdoc-scan... no
checking for xsltproc... /usr/bin/xsltproc
checking whether to build documentation... no
checking for debug mode... no (no debug output, NDEBUG)
checking for more warnings... checking whether gcc understands -Wmissing-include-dirs... yes
checking whether gcc understands -Wundef... yes
checking build strict... no
checking whether to build with gcov testing... no
checking that generated files are newer than configure... done
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating common/Makefile
config.status: creating common/tests/Makefile
config.status: creating doc/Makefile
config.status: creating doc/manual/Makefile
config.status: creating po/Makefile.in
config.status: creating p11-kit/Makefile
config.status: creating p11-kit/tests/Makefile
config.status: creating p11-kit/p11-kit-1.pc
config.status: creating p11-kit/pkcs11.conf.example
config.status: creating trust/Makefile
config.status: creating trust/trust-extract-compat
config.status: creating trust/tests/Makefile
config.status: creating trust/tests/test-extract
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
configure: build options:

    Host:                            i686-pc-linux-gnu
    Debug build:                     no (no debug output, NDEBUG)
    Strict build:                    no
    Build documentation:             no (no manual or reference)
    System global config:            /etc/pkcs11/pkcs11.conf
    System module config directory:  /etc/pkcs11/modules
    Package module config directory: ${pkgdatadir}/modules
    User global config:              ~/.config/pkcs11/pkcs11.conf
    User module config directory:    ~/.config/pkcs11/modules
    Load relative module paths from: ${exec_prefix}/lib/pkcs11

    With libtasn1 dependency:        yes
    With libffi:                     yes
    With hash implementation:        internal

    Build trust module:              yes
    Trust module paths:              /etc/ssl/certs/ca-certificates.crt
Comment 1 jan vereecke 2014-03-20 13:00:46 UTC
Created attachment 373090 [details]
config.log
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2014-03-20 14:04:17 UTC
Expects a DEPEND on app-misc/ca-certificates for /etc/ssl/certs/ca-certificates.crt, however oddly it seems, or ./configure --with-trust-paths=[path]
Comment 3 Rafał Mużyło 2014-03-20 15:29:07 UTC
Actually, given what has been established in the forum thread, I see two possibilities:

1. the logic in configure.ac is messed up (perhaps it's one of those cases where AS_IF is required ?)

2. sandbox is for some reason preventing 'test -f /etc/ssl/certs/ca-certificates.crt' from succeeding

While number 2 looks more likely given the result, it would be a far more strange reason.
Comment 4 jan vereecke 2014-03-24 10:18:19 UTC
I have found the cause of the issue:

ls -ld /etc/ssl 
was set to 
drwxr-xr-- 5 root root 4096 18 feb 17:41 /etc/ssl

due to this, test -f /etc/ssl/certs/ca-certificates.crt, when run as portage fails.

chown o+x /etc/ssl

resolved the issue.

Bug can be closed.