# Format for this file: # Epoch Channel Nickname Action Message # # All separated with a single space, empty values are replaced with a dash '-' # except messages which are kept empty. # Lines starting with '#' are comments; comments are not allowed except as the only content of the line # 1331771131 - bhundven nick bhundven|0xbee4 1331774590 - bhundven|0xbee4 nick bhundven|afk 1331788334 #crosstool-ng nandub join 1331789756 - nandub quit Quit: Get MacIrssi - http://www.sysctl.co.uk/projects/macirssi/ 1331800140 #crosstool-ng smartin join 1331807473 #crosstool-ng hank say Hi again guys. What does anyone know about the define TARGET_LIBGCC2_FLAGS? 1331807514 #crosstool-ng hank say Wondering why if I have target specific flags for gcc/libc why libgcc2 isn't passed the same data 1331807519 #crosstool-ng hank say same flags* 1331811393 #crosstool-ng aspect part 1331826370 #crosstool-ng al` join 1331827376 - smartin quit Ping timeout: 245 seconds 1331830955 #crosstool-ng smartin join 1331834467 - bhundven|afk nick bhundven 1331836794 #crosstool-ng y_morin join 1331841076 - smartin quit 1331844905 #crosstool-ng Tick_ join 1331845261 #crosstool-ng Tick_ say Hi y_morin. 1331845266 #crosstool-ng Tick_ say Tick again. 1331845270 #crosstool-ng Tick_ say You there? 1331846764 #crosstool-ng y_morin say Tick_: Heyda! :- 1331846767 #crosstool-ng y_morin say ) 1331846816 #crosstool-ng Tick_ say Hi :-) 1331846843 #crosstool-ng Tick_ say A quick question. Although I don't think it's x-tool-ng related. 1331846845 #crosstool-ng Tick_ say Is it ok? 1331846847 #crosstool-ng Tick_ say to ask? :-) 1331846863 #crosstool-ng y_morin say Don't ask to ask, just ask. ;-) 1331846956 #crosstool-ng Tick_ say if you can give me some hints.... I built the 64-bit system. The build went through fine. Imaging the box (PXE or USB) is fine as well. However, the boot procedure was stuck at pivot_root 1331846976 #crosstool-ng Tick_ say I meant the runtime system. (After imaging the box) 1331847160 #crosstool-ng Tick_ say I didn't upgrade all the packages and I don't know how to debug it. I intercept the init script to show a shell prompt. However, I have no clue which part is wrong. You mind shading some light? 1331847201 #crosstool-ng y_morin say Sorry, no idea. Does passing init=/bin/sh on the kernel command line works? 1331847420 #crosstool-ng Tick_ say I will try it. My question would be if any packages are necessary to be upgraded? I didn't upgrade GRUB (Still 0.97) because the v1.99 didn't work for me. 1331847492 #crosstool-ng y_morin say Sorry, I don't understand what you're trying to do. 1331847579 #crosstool-ng Tick_ say Sorry. I understand that it's to vague the question is. I was just stuck at this point for quite sometime and didn't know what to do next 1331847589 #crosstool-ng Tick_ say too 1331847628 #crosstool-ng Tick_ say Or maybe the question should be how do I debug the boot procedure? 1331847663 #crosstool-ng y_morin say Tick_: First, get a static hello-world print in a loop. If that works, go to next step 1331847678 #crosstool-ng y_morin say Second, get a dynamicaly-linked hello-world. 1331847683 #crosstool-ng y_morin say Third, get a shell 1331847714 #crosstool-ng y_morin say Fourth. Run an init shell script that does some more fancy stuff (load kernel module...) 1331847727 #crosstool-ng y_morin say Fifth, bring up network 1331847746 #crosstool-ng y_morin say fourth-and a half, mount file systems. 1331847795 #crosstool-ng y_morin say Tick_: use the init=... kernel command line to start your hello-world instead of the standard /sbin/init 1331847855 #crosstool-ng Tick_ say Sure. Thanks for the guidance. I will try it. 1331852611 - y_morin quit Quit: Night! 1331854618 - bhundven quit Quit: leaving