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: Tue, 24 Mar 2020 10:13:17 +0000 [thread overview]
Message-ID: <bug-12686-163-nVRQf8eC4v@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 #7 from Juan <jrmcorreo-linux@yahoo.es> ---
Hi again,
I tried changing value for the variable BR2_JLEVEL from 0 to 1 with no success.
About Makefile, the 358 line is next one:
357: install_dev: install_runtime_libs
358: @[ -n "$(INSTALLTOP)" ] || (echo INSTALLTOP should not be empty; exit
1)
359: @$(ECHO) "*** Installing development files"
360: @$(PERL) $(SRCDIR)/util/mkdir-p.pl
$(DESTDIR)$(INSTALLTOP)/include/openssl
361: @ :
If you want I can attach the whole Makefile (1.2 MB), but my point is that only
will serve to waste disk space on server.
About environment variables, I see no other value related to building
environment except PATH including entry to perl5, also PERL_LOCAL_LIB_ROOT and
PERL_LOCAL_LIB_ROOT entries.
Thank you and best regards
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-24 10:13 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 [this message]
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-nVRQf8eC4v@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.