Hello. How can i set to build a toolchain uClibc to use EABI version 0, instead of version 4, when compiling target-device's applications? On an embedded device (a camera) i have openssl libraries, but when i try to link something with them using uClibc toolchain, i get an error that the lib uses EABI version 0, and the toolchain supports version 4.
Can i somehow switch EABI in the configuration to another version? Thanks And also, how is it possible that some simple applications work on that device (if i compile them with the toolchain that follows EABI version 4, while the libraries have EABI v0)? When i try to upload EABI v4 version of Openssl library on the device, i get "Illegal intruction" error. Do i understand correctly, that most likely all the libraries on that device use EABI version 0 converntion, or it is possible that some use v0, some - v4? Thanks! -- View this message in context: http://old.nabble.com/EABI4%2C-EABI0---is-it-possible-to-switch-EABI-version-of-the-toolchain-tp28761482p28761482.html Sent from the uClibc mailing list archive at Nabble.com. _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
