Tim, yeah I do not know about that but using ldd as described above will
pretty much tell you what your systems tools expect at any rate.
On Thu, Sep 4, 2014 at 2:49 PM, Tim Cole wrote:
> I have no idea why, but I've got both an arm-linux-gnueabihf directory and
> an arm-linux-gnueabi (i.e no "
On Thu, Sep 4, 2014 at 4:49 PM, Tim Cole wrote:
> I have no idea why, but I've got both an arm-linux-gnueabihf directory and
> an arm-linux-gnueabi (i.e no "hf') directory. From what you've said, I'd
> guess I've installed something I shouldn't have installed. Presumably, if I
> check immediately
I have no idea why, but I've got both an arm-linux-gnueabihf directory and
an arm-linux-gnueabi (i.e no "hf') directory. From what you've said, I'd
guess I've installed something I shouldn't have installed. Presumably, if I
check immediately after installing a new OS, I wouldn't have the problem
Heh, another way I just figured out ( never noticed it before ) is to just
do . .
$ ls /lib/
there is a arm-linux-gnueabihf directory and a ld-linux-armhf.so.3 file.
Both of these should make it painfully obvious.
On Thu, Sep 4, 2014 at 12:46 PM, William Hermans wrote:
> *Find any local binar
>
> *Find any local binary like /bin/ls and do an ld on it. It links to an ld
> library with armel or armhf in the name.*
>
You would want to use ldd, probably not ld.
Usage: ldd /bin/ls /* going by above example */
*root@arm:~# ldd /bin/ls*
> *libselinux.so.1 => /lib/arm-linux-gnueabih
If the architecture is armhf that's hardfloat and requires a minimum of
armv5. armel is softfloat and can run on arm7tdmi (armv4).
Find any local binary like /bin/ls and do an ld on it. It links to an ld
library with armel or armhf in the name.
You'll find armel libraries in there too along w
