From: Eric Schwarz <eas@sw-optimization.com>
To: buildroot@busybox.net
Subject: [Buildroot] libopenssl in buildroot-2018.02
Date: Tue, 27 Mar 2018 15:38:24 +0200 [thread overview]
Message-ID: <b06bcfe21263864b9b35fdea9f15e99f@sw-optimization.com> (raw)
Hello,
the patches to be downloaded for the openssl-1.0.2n.tar.gz package are
defined in
./package/libopenssl/libopenssl.mk
by
LIBOPENSSL_PATCH
The patches are stored with some suffix after the "patch" extension.
When those are checked-in using SVN and checked-out under Windows it
won't work since there are "?" in the filename.
*
openssl-1.0.2a-parallel-install-dirs.patch?id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
*
openssl-1.0.2a-parallel-obj-headers.patch?id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
*
openssl-1.0.2a-parallel-symlinking.patch?id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
*
openssl-1.0.2d-parallel-build.patch?id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d
Apart, why have not those patches yet been applied to openssl master?
Cheers
Eric
next reply other threads:[~2018-03-27 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 13:38 Eric Schwarz [this message]
2018-03-30 19:49 ` [Buildroot] libopenssl in buildroot-2018.02 Arnout Vandecappelle
2018-03-30 20:04 ` Peter Korsgaard
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=b06bcfe21263864b9b35fdea9f15e99f@sw-optimization.com \
--to=eas@sw-optimization.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