# 00:06:04 |
devcoder |
quits : Quit: devcoder |
# 00:22:56 |
plfiorini_ |
quits : Ping timeout: 244 seconds |
# 00:23:24 |
sh4rm4 |
quits : Ping timeout: 276 seconds |
# 00:25:57 |
sh4rm4 |
joins #crosstool-ng |
# 02:38:10 |
mingwandroid |
quits : Quit: Leaving. |
# 04:29:33 |
alan_o |
quits : Ping timeout: 256 seconds |
# 07:35:17 |
smartin |
joins #crosstool-ng |
# 07:36:01 |
mingwandroid |
joins #crosstool-ng |
# 08:34:17 |
diorcety |
quits : Quit: Leaving. |
# 09:25:40 |
mingwandroid |
quits : Quit: Leaving. |
# 11:03:06 |
Joker-2 |
joins #crosstool-ng |
# 11:03:10 |
Joker-2 |
Hello |
# 11:03:28 |
Joker-2 |
I created toolchain with ct-ng. Now, how am I supposed to boot into that toolchain ? |
# 11:03:48 |
Joker-2 |
so that I can compile extra packages by hand against this toolchain |
# 11:09:36 |
tkil |
Joker-2 -- you don't "boot into" a toolchain. use use executables from that toolchain in the host environment to build executables which can run on the target. |
# 11:10:19 |
Joker-2 |
tkil, If I used that toolchain in "buildroot" then can I use the resultant image to "boot into" |
# 11:11:20 |
tkil |
well, you need either an emulator or the actual hardware. you build your image for the target, then transfer it to the target somehow, then cause your target to run it. if it's a kernel, then yes, a reboot is usually required. |
# 11:11:56 |
tkil |
the other instructions here are out of date, but this section is the gist of it: http://buffalo.nas-central.org/wiki/Build_%28and_use%29_a_cross-toolchain_using_Dan_Kegel%27s_crosstool_0.38#Using_a_Cross-Toolchain |
# 11:14:36 |
tkil |
Joker-2 -- although, depending on your target, you might have better luck with more integrated systems. you mentioned buildroot; the final output from that ought to be (at least) a kernel and a disk image. /me reads docs and it generates the bootloader as well... nice. |
# 11:14:45 |
tkil |
wishes he had know all this stuff 4 years ago. :) |
# 11:15:14 |
tkil |
Joker-2 -- what is your target? e.g., raspberry pi, router, something else? |
# 11:15:39 |
Joker-2 |
tkil, Thin client |
# 11:16:26 |
tkil |
like, chromebook type thing, or? |
# 11:18:27 |
Joker-2 |
sort of. It is a board with less CPU and used FLASH for storage purpose |
# 11:18:50 |
Joker-2 |
mostly used to connect to server like ICA, RDP |
# 11:21:06 |
tkil |
ok. so you have buildroot configured for your cpu / gfx / storage / client progs? and you've successfully built everything? |
# 11:23:59 |
Joker-2 |
yeah. I guess so. |
# 11:24:34 |
Joker-2 |
Now I am trying to boot into it, but it fails somehow ( not giving me login OR shell prompt ) |
# 11:25:58 |
diorcety1 |
joins #crosstool-ng |
# 11:27:16 |
tkil |
but you see kernel messages? |
# 11:27:50 |
Joker-2 |
yeah....It started all daemons mentioned in /etc/rc5.d and then it get stuck |
# 11:31:47 |
tkil |
so you even have init running. hm. how does buildroot handle /dev entries? might be that your virtual terminals aren't getting set up quite right. |
# 11:32:03 |
Joker-2 |
what is the correct value for "Port to run a getty (login prompt)" in buildroot |
# 11:32:09 |
Joker-2 |
I am running this image in vmware |
# 11:32:13 |
tkil |
you might also try to find a buildroot channel / forum, as it seems that the actuall cross compiling is working correctly. :( |
# 11:32:21 |
tkil |
(and it's 6:30a eastern USA time, so usa devs should be waking up soon.) |
# 11:32:37 |
Joker-2 |
it's 5:02 pm here |
# 11:42:16 |
tkil |
Joker-2 -- also: http://buildroot.uclibc.org/downloads/manual/manual.html#_frequently_asked_questions_amp_troubleshooting |
# 13:18:17 |
Joker-2 |
tkil, THnx |
# 13:18:35 |
Joker-2 |
Issue was the _wrong_ configuration |
# 13:18:46 |
Joker-2 |
I modify it and now I am in |
# 13:31:29 |
Net147 |
joins #crosstool-ng |
# 13:32:53 |
speakman |
joins #crosstool-ng |
# 13:32:54 |
speakman |
quits : Changing host |
# 13:32:54 |
speakman |
joins #crosstool-ng |
# 14:16:48 |
Joker-2 |
quits : Ping timeout: 245 seconds |
# 14:29:44 |
Joker-2 |
joins #crosstool-ng |
# 14:59:10 |
Net147 |
quits : Read error: Connection reset by peer |
# 16:19:44 |
diorcety1 |
quits : Quit: Leaving. |
# 16:26:22 |
usuario_ |
joins #crosstool-ng |
# 16:32:24 |
usuario_ |
quits : Quit: Saliendo |
# 17:14:34 |
alan_o |
joins #crosstool-ng |
# 17:33:42 |
y_morin |
joins #crosstool-ng |
# 17:36:20 |
diorcety |
joins #crosstool-ng |
# 17:37:25 |
hrubi |
quits : Ping timeout: 264 seconds |
# 17:40:15 |
hrubi |
joins #crosstool-ng |
# 17:43:06 |
codyps |
quits : Ping timeout: 276 seconds |
# 17:59:29 |
plfiorini |
joins #crosstool-ng |
# 17:59:36 |
hrubi |
quits : *.net *.split |
# 18:06:10 |
diorcety |
y_morin: hi |
# 18:06:50 |
y_morin |
diorcety: Hello! |
# 18:14:15 |
hrubi |
joins #crosstool-ng |
# 18:21:24 |
codyps |
joins #crosstool-ng |
# 18:22:31 |
diorcety |
y_morin: i have investigate my issue |
# 18:23:12 |
y_morin |
diorcety: Hmm. THe llvmgcc problem, right? |
# 18:24:27 |
diorcety |
y_morin: it's not a llvmgcc issue |
# 18:24:35 |
diorcety |
y_morin: it appears to be a gcc 4.2.1 issue |
# 18:24:53 |
diorcety |
y_morin: i have tried to compile gcc 4.2.1 (obsolete) i have a same issue |
# 18:25:12 |
y_morin |
diorcety: OK. Why such an old gcc version? Because llvm has not been ported to a GPLv3 gcc? |
# 18:25:16 |
diorcety |
y_morin: i'm currently tring to build it with the 1.16 release and not my git |
# 18:25:30 |
diorcety |
y_morin: llvmgcc is based on 4.2.1 |
# 18:25:41 |
y_morin |
diorcety: latest ct-ng is 1.17, not 1.16. |
# 18:26:09 |
diorcety |
y_morin: let's see with 1.16 first :D |
# 18:26:32 |
y_morin |
diorcety: Is that because gcc 4.2.1 is the latest to be GPLv2 that llvm has not been ported to a more recent gcc? |
# 18:27:20 |
diorcety |
y_morin: llvmgcc is like obsolete ... but it can be usefull (even if you doesn't want integrate it) |
# 18:27:33 |
y_morin |
diorcety: OK. |
# 18:28:19 |
diorcety |
y_morin: i confirm. bare-metal build x86 with gcc 4.2.1 is not working .. |
# 18:50:21 |
diorcety |
y_morin: Did I miss something? |
# 18:51:23 |
y_morin |
diorcety: I have not tried bare-metal x86 for a long time. Not sure it is supported... :-/ |
# 18:51:51 |
y_morin |
diorcety: You should try with a more recent gcc to see if it works. If it does, then it's a bug in gcc-4.2.1. |
# 18:52:08 |
y_morin |
diorcety: If it still does not work, then maybe we're doing something incorrect in ct-ng... |
# 18:52:18 |
diorcety |
ok |
# 18:52:32 |
diorcety |
i am currently running tests .. |
# 18:52:45 |
diorcety |
i will try with the last version (just before experimental) |
# 18:53:31 |
y_morin |
diorcety: OK. |
# 19:01:07 |
diorcety |
y_morin: 4.6.3 works |
# 19:19:38 |
smartin |
quits : Quit: leaving |
# 19:30:56 |
diorcety |
y_morin: start to work at 4.5.0 |
# 19:51:47 |
plfiorini |
quits : Quit: Leaving |
# 20:20:23 |
smartin |
joins #crosstool-ng |
# 20:36:57 |
plfiorini |
joins #crosstool-ng |
# 20:39:21 |
plfiorini |
quits : Remote host closed the connection |
# 20:43:24 |
plfiorini |
joins #crosstool-ng |
# 22:55:59 |
y_morin |
quits : Quit: N ighty Night! |
# 23:16:30 |
smartin |
quits : Quit: leaving |