From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] openssl: add ocf support
Date: Mon, 24 Jan 2011 17:35:53 +0100 [thread overview]
Message-ID: <20110124173553.61328a62@surf> (raw)
In-Reply-To: <20110117214924.564878A3BF@busybox.osuosl.org>
On Mon, 17 Jan 2011 22:27:41 +0100
Peter Korsgaard <jacmet@sunsite.dk> wrote:
> +define OPENSSL_INSTALL_CRYPTODEV_H
> +$(INSTALL) -D package/openssl/ocf-cryptodev-20101223.h \
> + $(STAGING_DIR)/usr/include/crypto/cryptodev.h
> +endef
> +
> +OPENSSL_POST_EXTRACT_HOOKS += OPENSSL_INSTALL_CRYPTODEV_H
> +endif
This is not a problem today, but it will break horribly when we'll try
to merge the packaging work from Lionel, because here we are installing
a file to the $(STAGING_DIR) outside of a package staging installation
step.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-24 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:27 [Buildroot] [git commit master 1/1] openssl: add ocf support Peter Korsgaard
2011-01-24 16:35 ` Thomas Petazzoni [this message]
2011-01-24 20:07 ` Peter Korsgaard
2011-01-27 15:08 ` Gustavo Zacarias
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=20110124173553.61328a62@surf \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox