# 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 # 1478141144 #crosstool-ng perr join 1478141144 - perr quit Changing host 1478141144 #crosstool-ng perr join 1478144396 - perr quit Ping timeout: 250 seconds 1478148801 - blueness_ quit Quit: blueness_ 1478148825 #crosstool-ng blueness_ join 1478153857 - blueness_ quit Quit: blueness_ 1478153905 #crosstool-ng blueness_ join 1478156079 #crosstool-ng diorcety join 1478156200 - diorcety quit Read error: Connection reset by peer 1478157535 #crosstool-ng pamaury join 1478158753 #crosstool-ng perr join 1478159123 - pamaury quit Ping timeout: 265 seconds 1478163134 - perr quit Ping timeout: 256 seconds 1478166053 #crosstool-ng pamaury_ join 1478166779 - pamaury_ quit Ping timeout: 244 seconds 1478167469 - blueness_ quit Quit: blueness_ 1478167752 #crosstool-ng blueness_ join 1478167874 - blueness_ quit Client Quit 1478169531 #crosstool-ng enunes join 1478172738 #crosstool-ng yann-kaelig join 1478176731 #crosstool-ng yann-kaelig say Hi 1478176775 #crosstool-ng yann-kaelig say I have built a crosstool-ng crosscompiler for my cubieboard2. I start a test with u-boot but there is a bug 1478176778 #crosstool-ng yann-kaelig say {standard input}:336: Error: push/pop do not support {reglist}^ -- `pop {r0,r1,r2,r3,r4,r9,ip,pc}^' 1478176807 #crosstool-ng yann-kaelig say I think there is a patch for gcc, but I have no idea if the patch has been applied for ct-ng 1478176922 #crosstool-ng yann-kaelig say Here is the log of the u-boot build http://dpaste.com/23M0A7F 1478177102 #crosstool-ng enunes say yann-kaelig: which gcc version do you use, if you know which patches are needed can you check if your version already contains it? otherwise, all ct-ng applies patches are in patches/gcc/ in the ct-ng source 1478177163 #crosstool-ng yann-kaelig say enunes, Hi crosscompiler -v http://dpaste.com/2QSD7RZ 1478177548 #crosstool-ng enunes say yann-kaelig: I'd suggest trying to build it with a toolchain built with the generic arm-unknown-linux-gnueabi sample (it should also work with the cubieboard2), if this is a gcc bug maybe it's related to some optimization you have enabled 1478177734 #crosstool-ng yann-kaelig say enunes, ok. yes, that could be also my optimisation, this is first time on crosstool-ng, I'm goign to find what going wrong. 1478180498 #crosstool-ng pamaury_ join 1478180786 - pamaury_ quit Ping timeout: 265 seconds 1478185457 #crosstool-ng Guma join 1478186646 #crosstool-ng Guma say I have general question about building tools. When my target is specific linux kernel does it make sense to build using crosstool-ng and select the latest kernel available? Can someone with experience shad some light on this for me? 1478186686 #crosstool-ng Guma say I small project and I am starting in linux/embedded development 1478186756 #crosstool-ng enunes say Guma: that's kernel headers. kernel headers have to be older than or equal to, the kernel you will be running, otherwise you will get a 'kernel too old' message on boot. they are also forward-compatible, so you can use some which are a bit older than your run kernel. 1478186760 #crosstool-ng pamaury_ join 1478186823 #crosstool-ng enunes say Guma: however, some applications require some recent kernel features, and for that you need recent kernel headers. So, use some kernel headers which are older to than the oldest kernel you plan to run, but not too old that soem applications might fail to build due to missing features 1478186838 #crosstool-ng Guma say enunes Kernel too old? I am not doing baretetal but just apps to specific linux target. Where does boot in my case comes to play 1478186990 #crosstool-ng enunes say Guma: if you have the glibc from your toolchain built with newer kernel headers on your target, it will complain on boot. and it makes sense, because glibc may be relying on features which might not be available in the running kernel 1478187072 #crosstool-ng Guma say enunes I did clone master and that is what I am using to build tools. The strange thing is that if I build gdb from same tarsal on my Mac it build fine (But this is targeted for Mac OS). This is using same compiler that crosstools-ng is using. When I build it myself it builds fine. In crosstool-ng I get error about use of "undeclared identifier 'LONG_MI". From your experience do you know where to start looking? Are the some 1478187072 #crosstool-ng Guma say extra flags that needs to be passed to crosstool-ng config? 1478187144 #crosstool-ng enunes say Guma: sorry, I don't know about Mac OS... 1478187165 #crosstool-ng Guma say enunes But at this stage I am interested on building just apps NOT building kernel. So still not clear about how booting makes difference in my case. I see your point if I would cross build kernel ... 1478187216 #crosstool-ng Guma say enunes I have some changes related to Mac in my local git. When I get all resolved I will do pull request when I will also test if first on Linux. 1478187241 #crosstool-ng enunes say Guma: you don't have to build the kernel. If you build the kernel with some other toolchain, and try to run userspace with glibc newer than that kernel, you would still run into the problem I described 1478187279 #crosstool-ng Guma say enunes Thank you I am clear now 1478187281 #crosstool-ng Guma say Is anyone else here who is interested or doing work on Mac? 1478187417 #crosstool-ng Guma say enunes So the best and safest practice for now for me is to select kernel/gcc/libc/gdb as the same as my target? Or I should be good only with gcc/gdb using latest? 1478187589 #crosstool-ng enunes say Guma: if you intend to build applications to run in a different userspace (not deploying the glibc built from your new toolchain), you should make sure to use the same versions you will have on the target. I don't do this either so I'd try to figure out the verisons present in the target 1478187610 #crosstool-ng enunes say Guma: you can find out the kernel headers used in /usr/include/linux/version.h 1478187652 #crosstool-ng Guma say enunes Thank you :) 1478187717 - pamaury_ quit Ping timeout: 265 seconds 1478187852 #crosstool-ng Guma say enunes one more thing :) can I use my local gdb build for intel to connect to remote gdb (ARM) to debugging. Or Do I have to build gdb to run locally on intel but connect to ARM? How does this work? 1478187896 #crosstool-ng Guma say I am googling about this but this specific question I can't find answer. Everyone talk about how to debug. 1478187938 #crosstool-ng enunes say Guma: you probably can't use your x86 gdb to talk to an arm gdbserver. what I usually do is to build a pair cross-gdb/gdbserver (ct-ng does that) and just use it. 1478188002 #crosstool-ng Guma say Ok I do have enabled this. But since I am having problem with this maybe I was trying to solve something that is not needed in my case. But looks like I will have to fix this first. 1478188184 #crosstool-ng yann-kaelig say there is something I don't understand in menuconfig and local patch. How crosstool-ng is able to use my patch for gcc ? 1478188578 #crosstool-ng yann-kaelig say I have to create the same tree as patches $HOME/$localpatch/gcc/6.1.0/ put the patch in this folder and set my local path for patch in menuconfig in this way $HOME/$localpatch ? 1478197787 - alan_o quit Ping timeout: 256 seconds 1478198066 #crosstool-ng yann-kaelig say well, I have build a new crosscompiler with an older gcc-4.9.x from menuconfig, no others change. There is no bug u-boot compilation success 1478198095 #crosstool-ng yann-kaelig say This is the thread about gcc-6.x with patch https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70830 1478198116 #crosstool-ng yann-kaelig say but I have no idea how to use this patch on ct-ng 1478198136 #crosstool-ng yann-kaelig say for a test 1478198230 #crosstool-ng enunes say yann-kaelig: it seems that the patch fixes a generic problem, you can put it into patches/gcc/ inside the crosstool-ng sources and test it, if it works you can send a pull request on github 1478198581 #crosstool-ng alan_o join 1478198593 #crosstool-ng yann-kaelig say enunes, ok this is what I done the first time. But no output on the screen if my patch is applied. I tried to find somethign in the log, but it's really big. 1478198737 - enunes quit Ping timeout: 265 seconds 1478199516 #crosstool-ng pamaury join 1478199602 #crosstool-ng enunes join 1478206010 #crosstool-ng blueness_ join 1478206526 - blueness_ quit Quit: blueness_ 1478206811 #crosstool-ng Guma say enunes: Is there a switch to only build last failed project? So I am having trouble with debug and want to just restart this section 1478207158 #crosstool-ng enunes say Guma: you can enable one of the options in "Paths and misc options" -> "Debug crosstool-NG", I remember using "Interactive shell on failed commands" a few times, never tried "Save intermediate steps" but according to the help text, it may be what you want 1478207283 #crosstool-ng Guma say Ok Will try this 1478207564 #crosstool-ng blueness_ join 1478209312 - blueness_ quit Quit: blueness_ 1478210577 #crosstool-ng Guma say I am reading ng documentation and I stumbled upon ct-ng build-all. What is the different between ct-ng build? Is build-all is used only in debugging and will "build" all by passing Y for each step? 1478211487 #crosstool-ng blueness_ join 1478213324 - pamaury quit Ping timeout: 265 seconds 1478215341 - blueness_ quit Quit: blueness_ 1478215592 #crosstool-ng blueness_ join