| Summary: | recipe for target 'install_dev' failed (libcrypto.so: file format not recognized) | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Juan <jrmcorreo-linux> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2020.02 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: | defconfig file that reproduces the issue I'm facing | ||
|
Description
Juan
2020-03-20 16:34:54 UTC
Please try a complete re-build:
make clean
make
If it fails again, please provide a complete .config file (or defconfig - after make savedefconfig)...
I attach a defconfig file for one of the Sunxi A20 boards that gives me the same error. Created attachment 8411 [details]
defconfig file that reproduces the issue I'm facing
Given defconfig compiles without failure here (host: openSUSE Tumbleweed), anything special with your build system? Hi, My build system is old but compliant with requirements: - gcc/gcc++ 4.9.2-6.fc21 - make 4.0-3.fc21 except perl version (5.18.4-310.fc21), but 2019.02 compiles well in my system and perl requirements are the same... and this error does not appear to be related with perl. Best Regards 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
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 The issue you are pointing to seems to be known in OpenSSL upstream: - https://github.com/openssl/openssl/issues/6641 - https://github.com/openssl/openssl/issues/9086 So, I setup a Docker container with CentOS 7, checked out Buildroot 2020.02 and built OpenSSL 1.1.1d, without any problem. The first issue mentioned above indicates that the problem came from a perl module called Text::Template, which I do not have installed in my Docker container: # perl -e 'use Text::Template; print $Text::Template::VERSION,"\n";' Can't locate Text/Template.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at -e line 1. BEGIN failed--compilation aborted at -e line 1. Since you mentioned you had some Perl-related environment variables defined, perhaps there is an issue with this ? Since we're not able to reproduce, we won't be able to help a lot here. Could you work on some way of reproducing this? 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 |