On Wed, Jan 5, 2011 at 7:11 AM, Phil Blundell <[email protected]> wrote: > On Wed, 2011-01-05 at 08:48 -0600, Russell Morris wrote: >> Just to confirm - have you run these on an armv4t target? Only asking >> because my build completes fine, but the executables don't seem to run on >> the target. > > What exactly happens when you try to run those executables? Have you > inspected them to see if they look like the right kind of thing, and/or > compared them to working ones? > > p. > >
yes as Phil asked you should try to localize the offending code in the faulty binary. So try to enable kernel debugging messages so it tells you where its faulting. Secondly if you can take a working system and see if the new binary faults in same way ? if not then link the binary statically and run it again on working system and see if it faults again. If it does then you can debug it > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
