All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trent Piepho <tpiepho@impinj.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libp11: Add new package for OpenSSL PKCS#11 engine
Date: Thu, 4 Apr 2019 21:10:50 +0000	[thread overview]
Message-ID: <1554412249.27243.12.camel@impinj.com> (raw)
In-Reply-To: <20190404214556.10f7ef0d@windsurf>

On Thu, 2019-04-04 at 21:45 +0200, Thomas Petazzoni wrote:
> 
> > Library for using PKCS#11, which includes an engine for OpenSSL that
> > lets it use PKCS#11 modules.  Which is really what this package is
> > about, not that libp11 library itself, which has no users outside the of
> > OpenSSL engine.
> > 
> > 
> It also needs host-pkgconf, because pkg-config is used to detect
> OpenSSL.

I had assumed this was implicit in an autotools-package, but I see that
it is not.

> 
> Then, even with this fixed, the package didn't build because it was
> installing its OpenSSL modules in the wrong folder, as pkg-config
> --variable enginesdir libcrypto returned a bogus value. I fixed that by
> passing --with-enginesdir.

This is interesting, as when I made this patch for an older buildroot,
pkgconfig would return the correct value.  It was not prefixed with the
stage.  This is a new behavior.

And it looks like this already hit a bunch of packages with things like
the x11 app-defaults dir.  Since "libdir" is in the whitelist of paths
to prefix, it also hits enginesdir since the latter is based on libdir.

Maybe that pkg-config whitelist should not affect variables that use
libdir and only prefix libdir itself?

  reply	other threads:[~2019-04-04 21:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 18:13 [Buildroot] [PATCH v2] libp11: Add new package for OpenSSL PKCS#11 engine Trent Piepho
2018-12-29  5:36 ` Frank Hunleth
2018-12-31 20:10   ` Trent Piepho
2019-04-04 19:45 ` Thomas Petazzoni
2019-04-04 21:10   ` Trent Piepho [this message]
2019-04-05  7:49     ` Thomas Petazzoni
2019-04-05 17:57       ` Trent Piepho
2019-04-05 19:29         ` jonsmirl at gmail.com
2019-04-06 11:57           ` Thomas Petazzoni
2019-04-06 14:39             ` jonsmirl at gmail.com
2019-04-26  8:12         ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1554412249.27243.12.camel@impinj.com \
    --to=tpiepho@impinj.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.