OK, thanks for making things clear. So I also think the way to go is using the same toolchain for the kernel and the "user binaries" -> I will (try to) use the linaro toolchain.
thanks so far. regards, Ben Am Mittwoch, 28. Mai 2014 15:39:21 UTC+2 schrieb RobertCNelson: > > On Wed, May 28, 2014 at 8:36 AM, <[email protected] <javascript:>> > wrote: > > Yeah! > > "sudo dpkg -i *.deb" did do the trick. > > > > I see now that only one dpkg call specifying all deb packages at once > > resolves the dependencies but fireing dpkg -i command for each file > alone > > (even in a "for each x in"-loop) does not work. - something new learned- > > > > Many thanks, I will now try to compile my project (using qt; this means > I > > need to recompile my qteverywhere also... damn.. so much left to do...) > > > > BTW: I also stumbled upon the linaro toolchain you mention here > > ( > http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-uEnv.txtbasedbootscript) > > > > Is it an "worth considering alternative" for this > > "home-brew-self-compiled-toolchain" ? > > There's nothing wrong with the "linaro" toolchain. Some > users/customers want an exact gcc/lib/etc match with the gcc/lib/etc > on the debian image. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- 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.
