From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/3] package/perl-crypt-openssl-random: bump version to 0.15
Date: Tue, 21 Aug 2018 23:43:17 +0200 [thread overview]
Message-ID: <20180821234317.33aba729@windsurf> (raw)
In-Reply-To: <t3bu4fx95s.ln2@ID-313208.user.individual.net>
Hello,
On Tue, 21 Aug 2018 23:00:13 +0200, Bernd Kuhls wrote:
> I did not forget about answering your question, was just busy with the
> security bump for libX11 ;)
Hehe, OK :-)
> In fact you were right about that only the host package is needed.
> I guess during the build tests I mixed up the target and host versions,
> first I used the target package, which caused an error in the other
> packages, then I tried the host package, which was broken as well (but I
> kept its files in the host install of perl), then switched back to the
> target package, still broken, and at last I added the "OPENSSL_PREFIX="
> hack to the target package which, together with the still installed host
> files, produced working builds of perl-crypt-openssl-{random, rsa}. But I
> did not notice that really the host files were, together with the hack,
> were responsible for the sucessful build.
OK, thanks for the additional explanation, makes sense. I'll give it a
test build.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-21 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 18:15 [Buildroot] [PATCH/next 1/3] package/perl-crypt-openssl-guess: new package Bernd Kuhls
2018-08-19 18:15 ` [Buildroot] [PATCH/next 2/3] package/perl-crypt-openssl-random: bump version to 0.15 Bernd Kuhls
2018-08-19 21:15 ` Thomas Petazzoni
2018-08-19 21:25 ` Thomas Petazzoni
2018-08-21 21:00 ` Bernd Kuhls
2018-08-21 21:43 ` Thomas Petazzoni [this message]
2018-08-19 18:15 ` [Buildroot] [PATCH/next 3/3] package/perl-crypt-openssl-rsa: bump version to 0.30 Bernd Kuhls
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=20180821234317.33aba729@windsurf \
--to=thomas.petazzoni@bootlin.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