| 00:51.34 | *** join/#oe hrw (~hrw@redhat/hrw) |
| 03:32.36 | *** join/#oe armpit (~armpit@2601:202:4001:9ea0:6413:eafd:1152:fa5c) |
| 04:01.48 | *** join/#oe snowkidind (~textual@216.15.40.124) |
| 05:03.07 | *** join/#oe dv_ (~quassel@62-178-118-86.cable.dynamic.surfer.at) |
| 05:15.10 | *** join/#oe sgw (~swold@134.134.139.76) |
| 05:17.16 | *** join/#oe Bunio_FH (~bunio@89-73-217-90.dynamic.chello.pl) |
| 05:19.56 | *** join/#oe yegorich (~yegorich@mail.visionsystems.de) |
| 05:30.08 | *** join/#oe hmwel (~hmw@zimbra.welvaarts.com) |
| 06:09.38 | *** join/#oe t0mmy (~tprrt@217.114.201.133) |
| 06:20.01 | *** join/#oe AndersD (~anders@213.236.250.210) |
| 06:20.14 | *** join/#oe ao2 (~ao2@host14-73-dynamic.61-82-r.retail.telecomitalia.it) |
| 06:44.31 | *** join/#oe lpotter (~quassel@2001:8003:6470:4900:ba27:ebff:febb:59b) |
| 06:47.44 | *** join/#oe eduardas_m (~eduardas@213.197.143.19) |
| 06:52.58 | *** join/#oe jbrianceau (uid10952@gateway/web/irccloud.com/x-yuatxqtyeiebnsen) |
| 07:01.45 | *** join/#oe Dvorkin_ (b072cc0c@gateway/web/freenode/ip.176.114.204.12) |
| 07:05.24 | Dvorkin_ | 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? |
| 07:10.58 | *** join/#oe khem (~khem@unaffiliated/khem) |
| 07:31.26 | *** join/#oe morphis (~morphis@pD9ED7FF5.dip0.t-ipconnect.de) |
| 07:42.02 | *** join/#oe AndersD (~anders@77.88.92.6) |
| 07:47.53 | *** join/#oe AndersD (~anders@77.88.92.6) |
| 08:08.24 | *** join/#oe t0mmy (~tprrt@217.114.201.133) |
| 08:46.04 | *** join/#oe JaMa (~martin@217.30.68.212) |
| 08:58.32 | *** join/#oe rburton (~textual@home.burtonini.com) |
| 08:59.49 | *** join/#oe yann (~yann@LFbn-1-3552-118.w90-127.abo.wanadoo.fr) |
| 09:13.31 | *** join/#oe stdint (~stdint@103.29.142.67) |
| 09:16.32 | *** part/#oe stdint (~stdint@103.29.142.67) |
| 09:17.38 | *** join/#oe koen (~koen@185.47.135.167) |
| 09:17.39 | *** join/#oe koen (~koen@linaro/koen) |
| 09:49.23 | *** join/#oe XorA (~XorA@xora.default.ggregory.uk0.bigv.io) |
| 10:09.52 | *** join/#oe Bunio_FH (~bunio@89-73-217-90.dynamic.chello.pl) |
| 10:39.15 | *** join/#oe dv__ (~quassel@62.178.118.86) |
| 10:49.33 | *** join/#oe AndersD (~anders@77.88.92.6) |
| 11:16.33 | *** join/#oe tasslehoff (~Tasslehof@82.147.55.166) |
| 11:48.38 | *** join/#oe ldnunes (~ldnunes_@181.220.79.73) |
| 12:05.47 | *** join/#oe AndersD (~anders@77.88.92.6) |
| 12:15.12 | *** join/#oe georgem_home (uid210681@gateway/web/irccloud.com/x-joniwjtdgduiepma) |
| 12:29.14 | *** join/#oe t0mmy (~tprrt@217.114.201.133) |
| 13:05.30 | *** join/#oe stephano (stephano@nat/intel/x-dfofcxfuyjopbimn) |
| 13:43.51 | *** join/#oe mflow (~code@unaffiliated/shiningthrough) |
| 13:53.22 | *** join/#oe baali (~baali@27.60.5.196) |
| 14:18.39 | *** join/#oe snowkidind (~textual@216.15.40.124) |
| 14:20.41 | *** join/#oe tom_nov (~Tomas@176.74.132.138) |
| 14:24.43 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 14:36.20 | *** join/#oe stefan_schmidt (~stefan@p200300480933FEC99A8389FFFE2E3FAE.dip0.t-ipconnect.de) |
| 14:39.29 | *** join/#oe ldnunes (~ldnunes_@181.220.79.73) |
| 14:59.48 | *** join/#oe baali (~baali@27.60.5.196) |
| 15:08.33 | *** join/#oe daro (~daro@88.131.56.168) |
| 15:11.29 | *** join/#oe Nilesh_ (uid116340@gateway/web/irccloud.com/x-hqcphjmqifyytrxw) |
| 15:22.07 | *** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte) |
| 15:28.54 | *** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte) |
| 15:39.42 | *** join/#oe ZubairLK (~Thunderbi@unaffiliated/zubairlk) |
| 15:52.50 | *** join/#oe baali (~baali@27.60.5.196) |
| 16:00.47 | *** join/#oe morphis (~morphis@pD9ED7FF5.dip0.t-ipconnect.de) |
| 16:02.14 | *** join/#oe zarzar (~zarzar@184.75.233.58) |
| 16:02.49 | zarzar | is the cross toolchain for armhf built into binaries during a yocto bitbake build for an armhf target? |
| 16:12.06 | vmeson | 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. |
| 16:14.12 | zarzar | 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) |
| 16:15.03 | zarzar | vmeson: do you know where i would find the built toolchain once my build is complete? |
| 16:16.28 | *** join/#oe morphis_ (~morphis@pD9ED75EC.dip0.t-ipconnect.de) |
| 16:17.12 | zarzar | vmeson: you said sstate is that the same as sstate-cache? |
| 16:21.11 | *** join/#oe morphis (~morphis@pD9ED75EC.dip0.t-ipconnect.de) |
| 16:21.34 | Crofton|work | zarzar, make sure peopl eknow you are using dora, things are different then |
| 16:22.19 | zarzar | Crofton: ok will do, my mistake |
| 16:22.34 | zarzar | using dora 1.5. FYI |
| 16:23.13 | Crofton|work | there have been alot of changes that may impact your answer |
| 16:25.09 | zarzar | ok |
| 16:40.06 | vmeson | zarzar: yes, sstate = sstate-cache. Dora? ugh... Also, hooking up an external compiler isn't something I've done, sorry. |
| 16:41.18 | *** join/#oe blight (~greg@80-109-132-21.cable.dynamic.surfer.at) |
| 16:41.18 | *** join/#oe blight (~greg@reactos/developer/blight) |
| 16:41.19 | zarzar | 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 |
| 16:42.26 | vmeson | zarzar: sure but you've got to get bitbake to use those binaries unless you're 'just' talking about developing your application. |
| 16:42.41 | zarzar | vmeson: yes my own application |
| 16:43.31 | zarzar | 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 |
| 16:45.26 | khem | zarzar: I was hoping you could use http://autobuilder.yoctoproject.org/pub/releases/CURRENT/toolchain/x86_64/ |
| 16:45.46 | khem | for prebuilt toolchain but it only goes back untill current release and next one |
| 16:46.51 | zarzar | khem: np i think this will work, pulling built binaries from a dora build for the target board |
| 16:47.05 | khem | yes |
| 16:47.17 | khem | although keep in mind there are point releases |
| 16:47.27 | khem | so what you might get will be latest dora |
| 16:47.39 | zarzar | i just need to make sure the settings are right, like NEON VFP etc... |
| 16:47.40 | khem | unless you know the exact dora release that was used |
| 16:47.45 | khem | ok |
| 16:47.54 | khem | that should be doable |
| 16:48.10 | zarzar | khem: i don't know the exact release except by the gcc version 4.8.1 |
| 16:48.51 | zarzar | i'm not sure if the NEON VFP settings affect the toolchain build |
| 16:49.51 | khem | it does |
| 16:50.01 | zarzar | oh ok |
| 16:50.19 | zarzar | thanks khem, will have to do more research then |
| 16:51.04 | zarzar | would be nice if that were a compiler flag instead of part of the build |
| 16:56.14 | khem | 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 |
| 16:56.35 | khem | we do depend on compiler flags to decide on these flags |
| 16:56.41 | *** join/#oe zarzar1 (~zarzar@184.75.233.58) |
| 16:56.49 | khem | but the problem is that we do not ship multilibs for compiler runtime |
| 16:57.34 | khem | so in practice you can only build for certain ABI combinations that the OE was configured for |
| 16:57.48 | zarzar1 | khem: i may have missed some of your messages just now |
| 16:57.51 | khem | but it lets you insert external toolchains |
| 16:58.02 | zarzar1 | seemed to be a freenode issue |
| 16:59.19 | zarzar1 | i saw "it does" then "but the problem is that we do not ship multilibs for compiler runtime" |
| 16:59.29 | zarzar1 | did i miss some? |
| 17:05.31 | zarzar1 | looks like there are hundreds of versions of the cross toolchain built |
| 17:05.54 | zarzar1 | https://pastebin.com/nnN8JfM9 |
| 17:06.02 | khem | dora |
| 17:06.03 | khem | 09:56:35 ⪠â we do depend on compiler flags to decide on these flags |
| 17:06.05 | khem | 09:56:40 â¬â¬â¶ â zarzar1 (~zarzar@184.75.233.58) has joined #oe |
| 17:06.27 | zarzar1 | ok thanks |
| 17:07.24 | khem | zarzar1: it builds components into individual packages |
| 17:07.30 | khem | so its one cross compiler in the end |
| 17:07.51 | khem | we have two phased bootstrap |
| 17:08.08 | *** join/#oe vmeson (~rmacleod@192-0-133-4.cpe.teksavvy.com) |
| 17:08.20 | khem | first is called -initial which is then used to jump start full cross compiler build |
| 17:08.37 | khem | its better than in past where we needed 3 phases :) |
| 17:09.14 | zarzar1 | hmmm not sure how to wade through all this |
| 17:09.36 | khem | what do you need to do ? |
| 17:09.53 | khem | in nutshell |
| 17:10.28 | zarzar1 | i guess i expected to find the toolchain binaries somewhere in sstate-cache |
| 17:12.46 | zarzar1 | i'm also surprised to see gnueabi instead of gnueabihf |
| 17:12.58 | *** join/#oe eFfeM (~frans@f160137.upc-f.chello.nl) |
| 17:27.01 | *** join/#oe florian (~florian_k@Maemo/community/contributor/florian) |
| 17:29.28 | *** join/#oe paulg_ (~paulg@128.224.252.2) |
| 17:39.28 | zarzar1 | 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) |
| 17:39.54 | khem | zarzar1: ok then checkout dora version from git |
| 17:40.13 | khem | zarzar1: and then choose MACHINE=beaglebone bitbake meta-toolchain |
| 17:40.25 | khem | that should give you SDK |
| 17:41.18 | zarzar1 | khem: i don;t need the sdk, just toolchain binaries, if the machine "beaglebone bitbake meta-toolchain" |
| 17:41.18 | khem | 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 |
| 17:43.07 | khem | yeah SDK contains more than what you need it essential is cross compiler |
| 17:43.09 | zarzar1 | khem: haha i see, i bitbake the meta-toochain sorry |
| 17:43.20 | zarzar1 | sweet! |
| 17:43.38 | zarzar1 | beaglebone or beagleboard ? |
| 17:43.39 | khem | you can share a binary from your platform then we can reverse engineer how it was built |
| 17:43.51 | khem | doesnt matter |
| 17:44.21 | khem | beaglebone might be better but whatvever is available in dora of the two |
| 17:44.57 | zarzar1 | beagleboard is in dora, not sure if that is the same processor as beaglebone |
| 17:56.35 | zarzar1 | similar enough, all are arm-v7a i think |
| 18:04.13 | *** join/#oe yann (~yann@nan92-1-81-57-214-146.fbx.proxad.net) |
| 18:22.59 | zarzar1 | hi khem, build of meta toolchain is complete |
| 18:23.07 | khem | they should be same as far as your issue is concerned |
| 18:23.21 | khem | ok install it and try to build |
| 18:24.00 | zarzar1 | is this the ADT? |
| 18:24.52 | khem | sort of yes |
| 18:25.04 | khem | it should have a self isntalled called *.sh |
| 18:25.22 | zarzar1 | khem i think i am off in the weeds, since dora does not have beaglebone support i built for the wrong arch: armel |
| 18:25.32 | zarzar1 | i need to build for armhf |
| 18:25.47 | khem | thats ok |
| 18:25.57 | zarzar1 | so i would need to figure out how to build for it in order to get the toolchain i need |
| 18:26.00 | khem | you can make that change in beagleboard.conf |
| 18:26.02 | zarzar1 | ok cool |
| 18:26.05 | zarzar1 | sweet |
| 18:26.32 | khem | just set DEFAULTTUNE = "cortexa8hf-neon" |
| 18:27.48 | zarzar1 | is this what i should follow: http://www.yoctoproject.org/docs/1.5/adt-manual/adt-manual.html#optionally-building-a-toolchain-installer |
| 18:29.31 | khem | yes |
| 18:30.54 | zarzar1 | so i think i want to change the settings then rebuild |
| 18:31.21 | zarzar1 | before i run the script, correct? |
| 18:35.41 | zarzar1 | khem: here is the beagleboard.conf https://pastebin.com/9uMgh2m0 |
| 18:36.17 | zarzar1 | commented out: #DEFAULTTUNE ?= "cortexa8hf-neon" |
| 18:36.29 | zarzar1 | uses this instead: include conf/machine/include/tune-cortexa8.inc |
| 18:38.30 | zarzar1 | here is tune-cortexa8.inc: https://pastebin.com/KkZA923h |
| 18:42.09 | zarzar1 | should i comment out the include line and use DEFAULTTUNE = "cortexa8hf-neon" instead? |
| 18:48.26 | khem | just uncomment DEFAULTTUNE assignment |
| 18:49.49 | zarzar1 | ok |
| 19:11.54 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 19:31.54 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 19:48.06 | zarzar1 | khem: build is done, genrated: poky-eglibc-x86_64-meta-toolchain-cortexa8hf-vfp-neon-toolchain-1.5.4.sh |
| 19:53.36 | zarzar1 | khem: it still builds gnueabi instead of gnueabihf, not sure why |
| 20:00.42 | *** join/#oe bluelightning (~paul@157.27.255.123.static.snap.net.nz) |
| 20:00.42 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 20:09.10 | khem | thats ok |
| 20:09.38 | khem | OE does not use the gnueabihf like debian and others |
| 20:09.54 | khem | OE uses the cmdline option instead |
| 20:10.15 | khem | -mfloat-abi=hard to control the calling convention ABI |
| 20:11.07 | zarzar1 | 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 |
| 20:11.56 | zarzar1 | build in eclipse fails also |
| 20:12.44 | zarzar1 | arm-poky-linux-gnueabi-g+= file not found even when invoking from command line in folder |
| 20:13.07 | zarzar1 | arm-poky-linux-gnueabi-gcc -v : file not found |
| 20:17.57 | zarzar1 | the executables (g++) may be linked against an incompatible runtime library https://unix.stackexchange.com/a/43516 |
| 20:21.49 | *** join/#oe ant_home (~ant__@host224-10-dynamic.249-95-r.retail.telecomitalia.it) |
| 20:33.03 | *** join/#oe florian (~florian_k@Maemo/community/contributor/florian) |
| 20:36.12 | armpit | hates code freezes |
| 20:38.14 | zarzar1 | khem: the toolchain only works on the ubuntu 12LTS VM, i would have to change build parameters somehow to statically link |
| 20:41.47 | khem | hugs armpit |
| 20:42.16 | khem | zarzar1: take the .sh installer to newer ubuntu and try it |
| 20:42.35 | khem | manual copy is always problematic, installer does some relocation stuff |
| 20:42.45 | zarzar1 | just the sh file? |
| 20:50.24 | zarzar1 | it works! |
| 20:51.04 | zarzar1 | at least ./arm-poky-linux-gnueabi-g++ -v works, testing build in eclipse now |
| 20:53.03 | zarzar1 | in eclipse there are now include issues, iostream not found |
| 20:54.06 | bluelightning | zarzar1: you should really be using the compiler command line that the environment setup script uses which will ensure the proper sysroot is used |
| 20:54.13 | bluelightning | i.e. ${CC} |
| 20:54.14 | khem | you need to source environment script |
| 20:54.30 | bluelightning | s/uses/sets/ |
| 20:54.52 | zarzar1 | bluelightning the goal was to use eclipse build and debugging |
| 20:55.21 | zarzar1 | where do i find the compiler command line? |
| 20:55.26 | bluelightning | 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 |
| 20:55.35 | zarzar1 | oh yea |
| 20:55.36 | khem | zarzar1: there is an ecipse plugin for ADT |
| 20:55.57 | zarzar1 | not for 1.5 and eclipse oxygen |
| 20:56.00 | bluelightning | basically, use the env setup script or use the same command line the script sets, one of the two |
| 20:56.25 | khem | right, source the script in shell |
| 20:56.41 | zarzar1 | trying to use 4.8.1 cross toolchain from dora + eclipse oxygen |
| 20:56.45 | khem | then echo $CC and friends fill them in into the eclipse project |
| 20:57.40 | zarzar1 | i have no idea where the scripts are |
| 20:58.28 | bluelightning | zarzar1: it's environment-setup-* in the directory where you installed the toolchain |
| 20:58.50 | zarzar1 | environment-setup-cortexa8hf-vfp-neon-poky-linux-gnueabi? |
| 20:58.59 | bluelightning | that would be it yes |
| 20:59.05 | zarzar1 | sweet |
| 21:08.21 | *** join/#oe zwg (~zgraham@50-254-135-242-static.hfc.comcastbusiness.net) |
| 21:11.13 | zarzar1 | there is a CPP and CXX variable |
| 21:12.48 | zarzar1 | never mind CPP = preprocessor |
| 21:22.27 | zarzar1 | so the build succeeds now but i cannot debug the output |
| 21:34.14 | zarzar1 | the executable is not for the right arch |
| 21:34.19 | zarzar1 | does not run |
| 21:35.00 | zarzar1 | thanks for the help, i think i will have to try a different approach |
| 21:40.07 | zarzar1 | on second thought it is possible i do not have the flags and options in the right spots though |
| 21:47.21 | *** join/#oe paulbarker (~quassel@2a01:4f8:c17:626::2) |
| 21:48.36 | *** join/#oe rsalveti (sid117878@linaro/rsalveti) |
| 21:52.31 | *** join/#oe dos1 (~dos1@neo900/coreteam/dos) |
| 21:59.23 | khem | zarzar1: what cmdline options were used to compile your app ? |
| 22:00.16 | khem | I would suggest to use all the options that env script |
| 22:00.20 | khem | uses |
| 22:01.47 | *** join/#oe marex-cloud (sid137234@gateway/web/irccloud.com/x-fwktgckcwzywfdab) |
| 22:05.00 | *** join/#oe OnkelUlla (~uol@ptx.hi.pengutronix.de) |
| 22:05.05 | *** join/#oe stefan_schmidt (~stefan@p200300480933FEC99A8389FFFE2E3FAE.dip0.t-ipconnect.de) |
| 22:54.49 | *** join/#oe georgem_home (uid210681@gateway/web/irccloud.com/x-afutygcuthtrgfwv) |