| # 04:15:10 | cpackham | quits : Ping timeout: 255 seconds |
| # 08:38:15 | Net147 | quits : Quit: Quit |
| # 08:38:30 | Net147 | joins #crosstool-ng |
| # 08:38:33 | Net147 | quits : Changing host |
| # 08:38:33 | Net147 | joins #crosstool-ng |
| # 20:23:59 | kenzu | joins #crosstool-ng |
| # 20:24:27 | kenzu | hello guys |
| # 20:24:39 | kenzu | hope youre all doing well |
| # 20:25:06 | kenzu | I have a question Ican't find a clear answer from the onterwebz |
| # 20:25:12 | kenzu | ./configure --host=x86_64-pc-linux-gnu --target=armv6l-unknown-linux-gnueabihf --prefix=/home/fu/cross/bitlbee |
| # 20:25:16 | kenzu | BitlBee configure |
| # 20:25:18 | kenzu | Cannot find glib2 development libraries, aborting. (Install libglib2-dev?) |
| # 20:25:31 | kenzu | how can I add glib2 to my toolchain ? |
| # 20:31:28 | milkylainen | kenzu: Hi. Various programs have different dependencies. The toolchain isn't a bucket for all sorts of libraries. You'd typically build the dependency list of libraries before you build whatever you are building. |
| # 20:32:08 | kenzu | if I understand well |
| # 20:32:29 | kenzu | you have to build a new toolchain esêcially for the program we want to cross compile ? |
| # 20:32:59 | milkylainen | No. You have to build and install the dependencies before you cross compile your program. |
| # 20:33:21 | kenzu | this is what i though |
| # 20:33:22 | milkylainen | On embedded environments that's usually the task of a build environment. Yocto, Buildroot, Ptxdist etc. |
| # 20:33:57 | kenzu | I saw somethings about buildroot but cann't really figure it out |
| # 20:34:27 | kenzu | the lib is missing , in the host, in the target, or in the toolchain ? |
| # 20:34:31 | kenzu | i guess toolchain |
| # 20:34:59 | milkylainen | No. It does not belong in the toolchain. Does all your linux distro libraries come with your toolchain? :) |
| # 20:36:03 | kenzu | not at all |
| # 20:36:29 | milkylainen | I suggest you try to read up on the embedded build environments that I suggested. They are a good place to start when doing embedded development. They have a bunch of docs and their workflow is about the same. |
| # 20:36:31 | kenzu | so this f*cking glib how should it be "installed" |
| # 20:36:55 | kenzu | i've been reading since days :) |
| # 20:37:22 | kenzu | with only success with hello.c |
| # 20:37:32 | kenzu | and a little paste program |
| # 20:37:43 | kenzu | so the toolchain can compile form my ARM |
| # 20:37:49 | milkylainen | I don't mean to be rude. But you can expect learning embedded to take years. |
| # 20:37:57 | kenzu | my ARM have this libs, since I can compile directly on it |
| # 20:38:21 | kenzu | yes I know I have a lot to learn |
| # 20:38:30 | kenzu | thats why I do my littles projects |
| # 20:38:35 | milkylainen | If you have a fully fledged distro on your machine you can build programs natively. |
| # 20:38:45 | milkylainen | Much like you would do on a normal linux pc. |
| # 20:38:55 | kenzu | my target is a rpi1 armv6 |
| # 20:39:15 | kenzu | so building is taking a loooot of time |
| # 20:39:27 | milkylainen | I'm not that familiar with what ready-made distros run on a rpi1. |
| # 20:39:42 | kenzu | but yeah; since my sreaches and some answer i get there and there |
| # 20:39:48 | kenzu | do it directly on RPI |
| # 20:39:53 | milkylainen | But if you have anything like a normal distro you should be able to install the glib-devel packages. |
| # 20:40:07 | kenzu | im in archlinux :) |
| # 20:40:21 | kenzu | that was one of my little projects |
| # 20:40:23 | milkylainen | archlinux should have a glib2 devel package you can install? |
| # 20:40:24 | kenzu | that runs fine |
| # 20:41:06 | kenzu | but it's failing on my host machine |
| # 20:41:26 | kenzu | i mean cross building |
| # 20:41:47 | kenzu | so its i my host system if I follow you |
| # 20:42:11 | kenzu | when I compile, (not cross) the same package on host it works |
| # 20:42:27 | kenzu | when I compile directly on ARM it works aswell |
| # 20:42:39 | kenzu | thats why I came up with the toolchain things |
| # 20:43:02 | milkylainen | If you're building on your host system (x86 pc or whatever) you need the cross toolchain and a build environment to be able to put together more complex things. I mean, you can do it manually, but that's just a cumbersome way to go every time. |
| # 20:43:09 | kenzu | I compiled at least 50 times my toolchain to make it work :) |
| # 20:44:07 | kenzu | Didn't quite understand your last sentence |
| # 20:44:43 | milkylainen | Hmm. |
| # 20:45:30 | kenzu | what do you mean by more complex things and build env to put together .... |
| # 20:45:34 | milkylainen | It's trying to tell you the same suggestion. For cross-builds on a PC, you will need an embedded build environment. |
| # 20:46:06 | milkylainen | If you don't use a build environment you can do it manually, but it's just very messy to do all the time. |
| # 20:46:41 | kenzu | ok, so what do you mean by build environement ? |
| # 20:47:08 | kenzu | specific exports ? architecture ? |
| # 20:47:54 | milkylainen | no, like ptxdist, yocto, buildroot. They are build environments (mostly for embedded) for cross building stuff that goes onto a target device. |
| # 20:48:07 | kenzu | ok/ |
| # 20:48:27 | kenzu | which one should I take at your opinion |
| # 20:48:38 | kenzu | i'll check how to work with |
| # 20:49:06 | milkylainen | I think buildroot or yocto are good places to start learning more about cross building for embedded targets in general. |
| # 20:49:16 | kenzu | ok |
| # 20:49:19 | milkylainen | Their documentation should be ok. |
| # 20:49:38 | milkylainen | Missing glib2 is not a crosstool-ng problem really. :) |
| # 20:49:38 | kenzu | ok i look around that |
| # 21:00:25 | zagura | kenzu: For quickstart, but hard to maintain, there are also projects which are focused on creating in some ways such ready environment output. |
| # 21:00:59 | zagura | I.e. you can get debian framework with deboostrap. |
| # 21:01:12 | kenzu | wow |
| # 21:01:20 | kenzu | i'm even more lost :D |
| # 21:01:31 | kenzu | and arhclinux is on both devices |
| # 21:01:53 | kenzu | I know it's easier with deb-like distro |
| # 21:01:59 | zagura | https://wiki.debian.org/Debootstrap - it's mainly useful for same platform, as setup is usually similar expierience as docker. |
| # 21:02:00 | kenzu | but still, my challenges |
| # 21:02:16 | milkylainen | kenzu: Why can't you build locally on the rpi1 if you have archlinux there? |
| # 21:02:33 | kenzu | the proc as been OC to.... |
| # 21:02:36 | kenzu | 1GHz |
| # 21:02:51 | kenzu | compiling is takking ages |
| # 21:03:07 | kenzu | so I put this challenge onto my head |
| # 21:03:33 | milkylainen | Ok. |
| # 21:03:45 | kenzu | just before i left the idea, I wanted to distcc cross compile |
| # 21:03:56 | kenzu | but wow |
| # 21:04:12 | kenzu | its beyond my knowledge even if I learn fast |
| # 21:04:34 | kenzu | there is not much docs |
| # 21:06:16 | zagura | kenzu: In short buildroot would provide linux on top of crosstools. There is sysroot for staging, where libraries and headers are installed and target rootfs, which could be whole image's filesystem. |
| # 21:07:07 | zagura | kenzu: Buildroot docs are very good and should be enough if one is able to understand whole words there/knows vocabulary :) |
| # 21:08:03 | kenzu | allright let's learn buildroot |
| # 21:08:14 | kenzu | thank to you guys ! |
| # 21:08:32 | kenzu | I may have further questions in some days :) |
| # 21:08:36 | milkylainen | happy learning! |
| # 21:08:45 | milkylainen | :) |
| # 21:09:38 | kenzu | thx :) |
| # 21:12:48 | zagura | kenzu: I think, it's nice indroduction into buildroot: https://www.youtube.com/watch?v=cIkTh3Xp3dA |
| # 21:13:28 | kenzu | (ã¥ï¿£ ³￣)㥠|
| # 21:15:13 | kenzu | ok so buildroot is basiclly a full system stored on a local directory |
| # 21:15:53 | zagura | A bit more :) |
| # 21:16:16 | zagura | But yeah, the part "ready to go" is from local copy of whole rootfs. |
| # 21:16:27 | milkylainen | kenzu: It's a build environment. It builds things. But I'm guessing #buildroot is available for questions related to it. :) |
| # 21:16:40 | kenzu | I guess because when you have installed a package within buildroot how to "transfer" it to the RPi |
| # 21:16:54 | kenzu | Yes I just saw the irc channel |
| # 21:17:15 | kenzu | i'll ask there for further question |
| # 21:17:27 | kenzu | nut you are good help |
| # 21:17:36 | kenzu | -n+b |
| # 21:54:37 | kenzu | last question for here, everyone is seelping on #buildrooot |
| # 21:54:39 | kenzu | 22:48 î° kenzu î° do you know if I can build rootbuild with a .img ? |
| # 21:54:40 | kenzu | 22:49 î° kenzu î° I only find buildroot TO img |
| # 21:54:58 | kenzu | maybe this a non-sense |
| # 22:03:50 | zagura | kenzu: On libera, #buildroot is very quiet. I think, on oftc, there is more active community. |
| # 22:04:29 | kenzu | ok thanks |
| # 22:04:58 | zagura | kenzu: img is complete image in one. You can get package from it location in output/target/usr/bin and scp/cp to target machine. |
| # 22:05:27 | zagura | If environment is matching (kernel/library versions/architecture), then it should work. |
| # 22:08:00 | kenzu | i flashed my rpi with this image ! |
| # 22:08:33 | kenzu | but dont really understand what you want me to do |
| # 22:28:29 | kenzu | fu@rpi ~/git/bitlbee $ ls libglib2.0-dev/usr/ |
| # 22:28:30 | kenzu | bin/ .DS_Store include/ lib/ share/ |
| # 22:28:42 | kenzu | can I just C/C ? :ddd |