-
Notifications
You must be signed in to change notification settings - Fork 146
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
compile error: objdump: ... : file format not recognized #125
Comments
installed elfutils but th error persists |
I encountered the same issue when upgrading to 4.19.11-arch1-1-ARCH. Downgrading both elfutils and libelf to 0.174-1 (+ adding them to IgnorePkg) and then upgrading linux, linux-headers, etc. worked for me. After rebooting, the driver compiled just fine. |
yes, that works, but what should we do next? |
Complain to ARCH. They are the ones that screwed something up. |
So, I had a similar issue trying to install this drive in KaOS: |
This is more likely to be a compiler problem. Do they have the same version of gcc? |
So far as I can tell, they seem to be the same version: |
make.log
strange error appeared after arch linux update to 4.19.11-arch1-1-ARCH kernel, see make.log attached (in russian)
error translates to
objdump: /var/lib/dkms/rtl8723bu/4.3.6.11_12942.20141204_BTCOEX20140507-4E40/build/core/.tmp_rtw_security.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/rtl8723bu/4.3.6.11_12942.20141204_BTCOEX20140507-4E40/build/core/.tmp_rtw_security.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/rtl8723bu/4.3.6.11_12942.20141204_BTCOEX20140507-4E40/build/core/.tmp_rtw_security.o: file format not recognized
and so on
The text was updated successfully, but these errors were encountered: