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: Mon, 23 Mar 2020 18:50:27 +0000 [thread overview]
Message-ID: <bug-12686-163-9dd76fMIbu@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 #6 from Peter Seiderer <ps.report@gmx.net> ---
Two last (from my side) options/suggestions:
- maybe a parallel build issue, try to re-build libopenssl with BR2_JLEVEL=1
set in the .config file
- check your environment variables, your log excerpt shows something
with
Makefile:358: recipe for target 'install_dev' failed
and
buildrootpath/host/bin/arm-buildroot-linux-gnueabihf-ar:
/buildrootpath/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/libcrypto.so:
file format not recognized
In my Makefile (build/libopenssl-1.1.1d/Makefile) the target install_dev
is form line 310 to 355 and contains install/cp/$(RANLIB)/chmod/mv commands for
.new files....no 'ar' call...and RANLIB is specified as
RANLIB=$(CROSS_COMPILE)<my_working_dir>/host/bin/arm-buildroot-linux-gnueabihf-ranlib
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-23 18:50 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 [this message]
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
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-9dd76fMIbu@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