From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12686] recipe for target 'install_dev' failed (libcrypto.so: file format not recognized)
Date: Wed, 27 May 2020 10:03:13 +0000 [thread overview]
Message-ID: <bug-12686-163-qVTcdRt521@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12686-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12686
--- Comment #9 from Juan <jrmcorreo-linux@yahoo.es> ---
Hello Thomas,
I'm sorry to answer too late, but due to the COVID-19 I have been compelled to
spend my time on other matters.
Today I've uninstalled the perl module and its dependencies and now I'm
compiling again buildroot 2020.02 without experiencing any error from
libopenssl.
Prior to post the bug I've searched a lot looking for the error, but i've got
no result about perl-Text-Template issues.
Let me to say your commitment with this issue exceeded the one that could be
expected. You had the possibility to answer saying it is an external issue to
buildroot and only related with libopenssl. Your answer could have been
shorter, but you made a test and provided the solution.
Thanks a lot
Juan
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-05-27 10:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 16:34 [Buildroot] [Bug 12686] New: recipe for target 'install_dev' failed (libcrypto.so: file format not recognized) bugzilla at busybox.net
2020-03-20 17:26 ` [Buildroot] [Bug 12686] " bugzilla at busybox.net
2020-03-20 18:50 ` bugzilla at busybox.net
2020-03-20 18:52 ` bugzilla at busybox.net
2020-03-20 21:35 ` bugzilla at busybox.net
2020-03-23 9:32 ` bugzilla at busybox.net
2020-03-23 18:50 ` bugzilla at busybox.net
2020-03-24 10:13 ` bugzilla at busybox.net
2020-05-17 20:20 ` bugzilla at busybox.net
2020-05-27 10:03 ` bugzilla at busybox.net [this message]
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=bug-12686-163-qVTcdRt521@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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