I installed these i386 libraries as described, so that can't be the problem. The build_kernel.sh script downloads it's own toolchain, which is gcc-linaro-4.9-2015.05-x86_64_arm-linux-gnueabihf, everything compiles without error, but as stated the architecture problem appears after installing the .deb files. Now, when I manually download the gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux toolchain as described in Robert's guide and set the system.sh to use this one, I get a constant stream of errors:
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. installing fakeroot:i386 does not help at all, the error just changes to: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. I don't know if using the x86_64 toolchain causes the "./scripts/recordmcount: 1: ./scripts/recordmcount: Syntax error: end of file unexpected" architecture mismatch, but I cannot get using the toolchain recommended in Robert's guide to work. On Sunday, December 20, 2015 at 6:00:45 PM UTC+1, William Hermans wrote: > > *Hi William* >> >> *I actually used build_deb.sh to build the .deb files I used for the >> second try, wasn't really clear maybe, sorry. There I just ran into the >> architecture problem.* >> > > Well, the top of that page for Robert's guide tells you how to deal with > 64bit host systems. e.g. <package>:386, and dpkg add-architecture, etc. > > On Sun, Dec 20, 2015 at 9:21 AM, Fabian Dalbert <[email protected] > <javascript:>> wrote: > >> Hi William >> >> I actually used build_deb.sh to build the .deb files I used for the >> second try, wasn't really clear maybe, sorry. There I just ran into the >> architecture problem. >> >> >> On Sunday, December 20, 2015 at 5:01:11 PM UTC+1, William Hermans wrote: >>> >>> Use build_deb.sh instead of build_kernel.sh, following the directions >>> exactly the same otherwise, and you should be presented with 3-4 debs in >>> the deploy directory when done. One of those will be a kernel headers *deb >>> for which you can easily move to the target, and dpkg -i <packagename> to >>> install. >>> >>> On Sun, Dec 20, 2015 at 7:47 AM, Fabian Dalbert <[email protected]> >>> wrote: >>> >>>> Hi >>>> >>>> I am working on a kernel module for the beaglebone black and trying to >>>> make use of preempt rt to improve timing. I tweaked some settings in the >>>> 4.1.13-ti-rt-r36 kernel and compiled it using Robert Nelson's instructions >>>> here <https://eewiki.net/display/linuxonarm/BeagleBone+Black>. >>>> The kernel runs on the beaglebone, however I cannot seem to get the >>>> headers right to install my kernel module. I first installed the kernel >>>> directly to the sd-card using the install_kernel.sh script. This does not >>>> install the kernel headers. Installing the headers for the exact same >>>> version from the repository lets me compile my module, however not insert >>>> it: >>>> >>>> [ 1495.737241] UARTbbMod: disagrees about version of symbol >>>> module_layout >>>> >>>> Next I installed the kernel image along with headers and firmware image >>>> as .deb files, however now I cannot compile my module as I get the >>>> following error: >>>> >>>> root@beaglebone:~/UARTbbModule# make >>>> make -C /lib/modules/4.1.13-ti-rt-r36/build M=/root/UARTbbModule modules >>>> make[1]: Entering directory `/usr/src/linux-headers-4.1.13-ti-rt-r36' >>>> ./scripts/recordmcount: 1: ./scripts/recordmcount: Syntax error: end of >>>> file unexpected >>>> make[2]: *** [/root/UARTbbModule/UARTbitbangModule.o] Error 2 >>>> make[1]: *** [_module_/root/UARTbbModule] Error 2 >>>> make[1]: Leaving directory `/usr/src/linux-headers-4.1.13-ti-rt-r36' >>>> make: *** [all] Error 2 >>>> >>>> according to some google research this seems to be a problem when >>>> cross-compiling headers on a different system architecture (my host pc has >>>> 64-bit Linux Mint 17.3 installed). >>>> >>>> Can somebody point me in the right direction on how to get the kernel >>>> headers working alongside a self-compiled kernel? >>>> >>>> Help is greatly appreciated, thanks! >>>> >>>> -- >>>> 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] <javascript:>. >> 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.
