New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3810 - Build of x86_64 target fails on x86_64 host (libtool erroneously picks /usr/lib64/libc.so) #7002
Comments
zhubr:
|
zhubr: Uh, apparently the problem is quite an opposite to what I initially supposed. The failure happens in libtool at this step: (cd .libs && rm -f libpcreposix.so.0.0.6U && mv -f libpcreposix.so.0.0.6 libpcreposix.so.0.0.6U) So apparenly the system 'mv' command fails to operate, likely because libtool attempted to prevent finding local system libraries so much that even 'mv' somehow starts failing. Maybe have to look at some env vars... |
zhubr: Ok, found it. |
zhubr: Ok, I've created some fix. 190-fix-more-libtool.patch |
bjonglez: See https://openwrt.org/submitting-patches Note that changes to 19.07 need a very good reason to get accepted, but you can start by submitting a fix for the master branch. |
OpenWrt 19.07 release is EOL, try to reproduce the issue with latest supported release and feel free to ask for issue reopening if the problem is still present, thanks. |
I tried to build openwrt based on Centos7, The following error occurs.
|
zhubr:
I'm building openwrt 19.08.7 x86_64 target on an x86_64 linux box, and building fails in libpcre, with a libtool complaining that it tried to relink libpcreposix.la, and for that it found /usr/lib64/libc.so with an invalid ELF header. The complaint is true somewhat, because indeed /usr/lib64/libc.so is not an ELF on my system, but obviously it should not even be trying to pick a local system library at the first place.
There is a very old similar bugreport (solved long ago) --
https://dev.archive.openwrt.org/ticket/8399
Note: 32-bit x86 builds complete successfully on this same box.
The text was updated successfully, but these errors were encountered: