**** BEGIN LOGGING AT Thu Sep 21 03:00:02 2017 Sep 21 07:05:24 I have source build by cmake. recipe installs program binary and source for kernel module. how can I build kernel module right after do_install step of the recipe? Sep 21 16:02:49 is the cross toolchain for armhf built into binaries during a yocto bitbake build for an armhf target? Sep 21 16:12:06 zarzar: you're question is equivalent to: Does oe core build the toolchain from source? The answer is yes unless: 1) you have built already and we can pull the toolchain from sstate or 2) you are using a yocto distro tha ships the toolchain as a binary. Sep 21 16:14:11 vmeson: ok i am building the first time for beagleboard, i want to use the built gnueabihf cross toolchain in eclipse (already set up but with a newer toolchain version) Sep 21 16:15:03 vmeson: do you know where i would find the built toolchain once my build is complete? Sep 21 16:17:12 vmeson: you said sstate is that the same as sstate-cache? Sep 21 16:21:33 zarzar, make sure peopl eknow you are using dora, things are different then Sep 21 16:22:19 Crofton: ok will do, my mistake Sep 21 16:22:33 using dora 1.5. FYI Sep 21 16:23:13 there have been alot of changes that may impact your answer Sep 21 16:25:09 ok Sep 21 16:40:06 zarzar: yes, sstate = sstate-cache. Dora? ugh... Also, hooking up an external compiler isn't something I've done, sorry. Sep 21 16:41:19 vmeson: if the binaries are built i think i can just copy them to wherever is convenient and add the path to eclipse cross settings Sep 21 16:42:26 zarzar: sure but you've got to get bitbake to use those binaries unless you're 'just' talking about developing your application. Sep 21 16:42:41 vmeson: yes my own application Sep 21 16:43:31 so pretty easy with the binaries, i have a newer Vm with a nice eclipse setupwith remote debugging, i just don't have the right compiler version for the project Sep 21 16:45:26 zarzar: I was hoping you could use http://autobuilder.yoctoproject.org/pub/releases/CURRENT/toolchain/x86_64/ Sep 21 16:45:46 for prebuilt toolchain but it only goes back untill current release and next one Sep 21 16:46:51 khem: np i think this will work, pulling built binaries from a dora build for the target board Sep 21 16:47:05 yes Sep 21 16:47:17 although keep in mind there are point releases Sep 21 16:47:27 so what you might get will be latest dora Sep 21 16:47:39 i just need to make sure the settings are right, like NEON VFP etc... Sep 21 16:47:40 unless you know the exact dora release that was used Sep 21 16:47:45 ok Sep 21 16:47:54 that should be doable Sep 21 16:48:10 khem: i don't know the exact release except by the gcc version 4.8.1 Sep 21 16:48:50 i'm not sure if the NEON VFP settings affect the toolchain build Sep 21 16:49:51 it does Sep 21 16:50:01 oh ok Sep 21 16:50:18 thanks khem, will have to do more research then Sep 21 16:51:04 would be nice if that were a compiler flag instead of part of the build Sep 21 16:56:14 zarzar: generally it is a compiler flag, sometime back we retracted with gcc configure options to make it hard float by default not sure if it was after dora Sep 21 16:56:35 we do depend on compiler flags to decide on these flags Sep 21 16:56:49 but the problem is that we do not ship multilibs for compiler runtime Sep 21 16:57:34 so in practice you can only build for certain ABI combinations that the OE was configured for Sep 21 16:57:48 khem: i may have missed some of your messages just now Sep 21 16:57:51 but it lets you insert external toolchains Sep 21 16:58:02 seemed to be a freenode issue Sep 21 16:59:19 i saw "it does" then "but the problem is that we do not ship multilibs for compiler runtime" Sep 21 16:59:29 did i miss some? Sep 21 17:05:31 looks like there are hundreds of versions of the cross toolchain built Sep 21 17:05:54 https://pastebin.com/nnN8JfM9 Sep 21 17:06:02 dora Sep 21 17:06:03 09:56:35 ↪ │ we do depend on compiler flags to decide on these flags Sep 21 17:06:05 09:56:40 ▬▬▶ │ zarzar1 (~zarzar@184.75.233.58) has joined #oe Sep 21 17:06:27 ok thanks Sep 21 17:07:24 zarzar1: it builds components into individual packages Sep 21 17:07:30 so its one cross compiler in the end Sep 21 17:07:51 we have two phased bootstrap Sep 21 17:08:19 first is called -initial which is then used to jump start full cross compiler build Sep 21 17:08:37 its better than in past where we needed 3 phases :) Sep 21 17:09:14 hmmm not sure how to wade through all this Sep 21 17:09:36 what do you need to do ? Sep 21 17:09:52 in nutshell Sep 21 17:10:28 i guess i expected to find the toolchain binaries somewhere in sstate-cache Sep 21 17:12:46 i'm also surprised to see gnueabi instead of gnueabihf Sep 21 17:39:28 khem: in a nutshell i need binaries of the version 4.8.1 cross toolchain built with dora for i.mx6 target (for now as a learning process the target is beagleboard) Sep 21 17:39:54 zarzar1: ok then checkout dora version from git Sep 21 17:40:13 zarzar1: and then choose MACHINE=beaglebone bitbake meta-toolchain Sep 21 17:40:25 that should give you SDK Sep 21 17:41:18 khem: i don;t need the sdk, just toolchain binaries, if the machine "beaglebone bitbake meta-toolchain" Sep 21 17:41:18 now if the SDK comes out with say soft-float then we can change the default_tune and keep generating SDK unless it matches to what you need Sep 21 17:43:07 yeah SDK contains more than what you need it essential is cross compiler Sep 21 17:43:09 khem: haha i see, i bitbake the meta-toochain sorry Sep 21 17:43:19 sweet! Sep 21 17:43:37 beaglebone or beagleboard ? Sep 21 17:43:39 you can share a binary from your platform then we can reverse engineer how it was built Sep 21 17:43:50 doesnt matter Sep 21 17:44:21 beaglebone might be better but whatvever is available in dora of the two Sep 21 17:44:57 beagleboard is in dora, not sure if that is the same processor as beaglebone Sep 21 17:56:35 similar enough, all are arm-v7a i think Sep 21 18:22:59 hi khem, build of meta toolchain is complete Sep 21 18:23:07 they should be same as far as your issue is concerned Sep 21 18:23:21 ok install it and try to build Sep 21 18:24:00 is this the ADT? Sep 21 18:24:52 sort of yes Sep 21 18:25:04 it should have a self isntalled called *.sh Sep 21 18:25:22 khem i think i am off in the weeds, since dora does not have beaglebone support i built for the wrong arch: armel Sep 21 18:25:31 i need to build for armhf Sep 21 18:25:47 thats ok Sep 21 18:25:57 so i would need to figure out how to build for it in order to get the toolchain i need Sep 21 18:26:00 you can make that change in beagleboard.conf Sep 21 18:26:02 ok cool Sep 21 18:26:05 sweet Sep 21 18:26:32 just set DEFAULTTUNE = "cortexa8hf-neon" Sep 21 18:27:48 is this what i should follow: http://www.yoctoproject.org/docs/1.5/adt-manual/adt-manual.html#optionally-building-a-toolchain-installer Sep 21 18:29:31 yes Sep 21 18:30:54 so i think i want to change the settings then rebuild Sep 21 18:31:21 before i run the script, correct? Sep 21 18:35:41 khem: here is the beagleboard.conf https://pastebin.com/9uMgh2m0 Sep 21 18:36:17 commented out: #DEFAULTTUNE ?= "cortexa8hf-neon" Sep 21 18:36:29 uses this instead: include conf/machine/include/tune-cortexa8.inc Sep 21 18:38:30 here is tune-cortexa8.inc: https://pastebin.com/KkZA923h Sep 21 18:42:09 should i comment out the include line and use DEFAULTTUNE = "cortexa8hf-neon" instead? Sep 21 18:48:26 just uncomment DEFAULTTUNE assignment Sep 21 18:49:49 ok Sep 21 19:48:06 khem: build is done, genrated: poky-eglibc-x86_64-meta-toolchain-cortexa8hf-vfp-neon-toolchain-1.5.4.sh Sep 21 19:53:36 khem: it still builds gnueabi instead of gnueabihf, not sure why Sep 21 20:09:09 thats ok Sep 21 20:09:38 OE does not use the gnueabihf like debian and others Sep 21 20:09:54 OE uses the cmdline option instead Sep 21 20:10:15 -mfloat-abi=hard to control the calling convention ABI Sep 21 20:11:06 i tried moving the arm-poky-linux-gnueabi folder that contains arm-poky-linux-gnueabi-* to my ubuntu 16lts but i cannot invoke the any with -v for version Sep 21 20:11:56 build in eclipse fails also Sep 21 20:12:44 arm-poky-linux-gnueabi-g+= file not found even when invoking from command line in folder Sep 21 20:13:07 arm-poky-linux-gnueabi-gcc -v : file not found Sep 21 20:17:56 the executables (g++) may be linked against an incompatible runtime library https://unix.stackexchange.com/a/43516 Sep 21 20:36:12 * armpit hates code freezes Sep 21 20:38:14 khem: the toolchain only works on the ubuntu 12LTS VM, i would have to change build parameters somehow to statically link Sep 21 20:41:47 * khem hugs armpit Sep 21 20:42:15 zarzar1: take the .sh installer to newer ubuntu and try it Sep 21 20:42:34 manual copy is always problematic, installer does some relocation stuff Sep 21 20:42:45 just the sh file? Sep 21 20:50:24 it works! Sep 21 20:51:04 at least ./arm-poky-linux-gnueabi-g++ -v works, testing build in eclipse now Sep 21 20:53:03 in eclipse there are now include issues, iostream not found Sep 21 20:54:07 zarzar1: you should really be using the compiler command line that the environment setup script uses which will ensure the proper sysroot is used Sep 21 20:54:13 i.e. ${CC} Sep 21 20:54:14 you need to source environment script Sep 21 20:54:30 s/uses/sets/ Sep 21 20:54:52 bluelightning the goal was to use eclipse build and debugging Sep 21 20:55:21 where do i find the compiler command line? Sep 21 20:55:26 zarzar1: yep and that's fine, but you can't just run the compiler without specifying the sysroot in particular or you will hit issues like the one you are hitting now Sep 21 20:55:35 oh yea Sep 21 20:55:36 zarzar1: there is an ecipse plugin for ADT Sep 21 20:55:57 not for 1.5 and eclipse oxygen Sep 21 20:56:00 basically, use the env setup script or use the same command line the script sets, one of the two Sep 21 20:56:25 right, source the script in shell Sep 21 20:56:41 trying to use 4.8.1 cross toolchain from dora + eclipse oxygen Sep 21 20:56:45 then echo $CC and friends fill them in into the eclipse project Sep 21 20:57:40 i have no idea where the scripts are Sep 21 20:58:28 zarzar1: it's environment-setup-* in the directory where you installed the toolchain Sep 21 20:58:50 environment-setup-cortexa8hf-vfp-neon-poky-linux-gnueabi? Sep 21 20:58:59 that would be it yes Sep 21 20:59:04 sweet Sep 21 21:11:13 there is a CPP and CXX variable Sep 21 21:12:48 never mind CPP = preprocessor Sep 21 21:22:26 so the build succeeds now but i cannot debug the output Sep 21 21:34:14 the executable is not for the right arch Sep 21 21:34:19 does not run Sep 21 21:35:00 thanks for the help, i think i will have to try a different approach Sep 21 21:40:07 on second thought it is possible i do not have the flags and options in the right spots though Sep 21 21:59:23 zarzar1: what cmdline options were used to compile your app ? Sep 21 22:00:16 I would suggest to use all the options that env script Sep 21 22:00:20 uses **** ENDING LOGGING AT Fri Sep 22 03:00:00 2017