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 <[email protected]> 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 after installing a new OS, I wouldn't have the problem. > > Much obliged, folks. > > > > > On Thursday, September 4, 2014 3:58:08 PM UTC-4, William Hermans wrote: >> >> 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. >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
