# 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 # 1465085024 - imMute quit Ping timeout: 260 seconds 1465085488 #crosstool-ng imMute join 1465087264 - lundmar quit Quit: WeeChat 1.4 1465088029 - blueness quit Quit: blueness 1465088137 #crosstool-ng blueness join 1465088359 #crosstool-ng fenugrec join 1465090285 #crosstool-ng fenugrec_ join 1465090515 - fenugrec quit Ping timeout: 258 seconds 1465092178 - fenugrec_ nick fenugrec 1465101423 - fenugrec quit Ping timeout: 264 seconds 1465109805 #crosstool-ng lundmar join 1465119693 #crosstool-ng y_morin join 1465123957 #crosstool-ng y_morin_ join 1465124016 - c0de1 quit Ping timeout: 260 seconds 1465124023 - aneyman__ quit Ping timeout: 260 seconds 1465124023 - y_morin quit Quit: leaving 1465124025 - coffeeholic_ quit Ping timeout: 260 seconds 1465124030 - y_morin_ nick y_morin 1465124133 #crosstool-ng c0de1 join 1465124133 - c0de1 quit Changing host 1465124133 #crosstool-ng c0de1 join 1465124466 #crosstool-ng aneyman__ join 1465125546 #crosstool-ng coffeeholic_ join 1465135201 #crosstool-ng fenugrec join 1465136920 - s1341 quit Ping timeout: 252 seconds 1465137750 #crosstool-ng s1341 join 1465145344 - blueness quit Quit: blueness 1465145385 #crosstool-ng blueness join 1465154775 - muep quit Remote host closed the connection 1465154810 #crosstool-ng muep join 1465163475 #crosstool-ng ghostbsdun join 1465164373 #crosstool-ng JakeSays join 1465164412 #crosstool-ng JakeSays say hey is it possible with crosstool-ng to build a toolchain hosted on windows and targeting linux/arm? 1465164426 #crosstool-ng JakeSays say would be built on linux 1465164834 #crosstool-ng lundmar say JakeSays: http://crosstool-ng.org/#canadian_build 1465164857 #crosstool-ng JakeSays say lundmar: lol canadian? 1465164888 #crosstool-ng lundmar say JakeSays: yes, that is the name of the type of build you are looking for ;) 1465164895 #crosstool-ng JakeSays say LOL thats funny 1465164936 #crosstool-ng lundmar say well, I would rather be in Canada now than then US haha 1465165036 #crosstool-ng JakeSays say hmm. i'd prefer to target msys/mingw than cygwin 1465165191 #crosstool-ng JakeSays say any plans to move to gcc 5.3? 1465165194 #crosstool-ng fenugrec say I wonder what a "Trump build" would consist of ? 1465165231 #crosstool-ng lundmar say fenugrec: exactly my point haha 1465165419 #crosstool-ng lundmar say JakeSays: ct-ng usually include support for the latest stable gcc at the time of ct-ng release. 1465165454 #crosstool-ng JakeSays say right, which was 7 months ago 1465165463 #crosstool-ng JakeSays say isn't 5.3 stable? 1465165535 #crosstool-ng lundmar say JakeSays: gcc 5.3 was released before last ct-ng release. 1465165566 #crosstool-ng lundmar say *latest 1465165566 #crosstool-ng JakeSays say lundmar: lol i know. let me rephrase my question. when is the next release of ct-ng planned? 1465165611 #crosstool-ng lundmar say sorry, I don't know. Someone else will have to answer that question. 1465165854 #crosstool-ng fenugrec say I expect the answer to be "when it's ready", or "when you take care of it" P-) 1465165874 #crosstool-ng JakeSays say fenugrec: lol yeah me too 1465165984 #crosstool-ng fenugrec say while there's some sign of life on this channel : where are the arguments / variables set just before compiling newlib ? 1465165986 #crosstool-ng lundmar say either way, no need to talk 5.3 when 5.4 is here :) 1465166008 #crosstool-ng JakeSays say its not a big issue. 5.2 is fine for what i'm doing at the moment. 1465166043 #crosstool-ng fenugrec say i.e. why does newlib think the target is "sh3eb" instead of just "sh", etc 1465166237 #crosstool-ng lundmar say fenugrec: did you have a look at scripts/build/libc/newlib.sh? 1465166302 #crosstool-ng fenugrec say lundmar: I thought I did, but maybe I skipped that one 1465166335 - diorcety quit Read error: Connection reset by peer 1465166353 #crosstool-ng lundmar say well, its pretty instrumental for newlib builds ;) 1465166620 #crosstool-ng lundmar say fenugrec: there is also scripts/build/arch/sh.sh 1465166621 #crosstool-ng fenugrec say no doubt. I think I was trying to track down a something_VARIANT variable that gets formed into "sh3eb" at some point. Also, I kept getting massive crashes while compiling, which hasn't helped the thought process 1465166658 #crosstool-ng lundmar say sh* is simply not well tested platform 1465166665 #crosstool-ng lundmar say +a 1465166669 #crosstool-ng fenugrec say you don't say : )) 1465166692 #crosstool-ng lundmar say I would put it in the exotic category haha 1465166971 - y_morin quit Quit: Nighty Night! 1465167005 #crosstool-ng fenugrec say also, wtf, at some point newlib has ${host_cpu} defined to "sh3eb". Pretty sure I'm running ct-ng on an x86 1465167190 #crosstool-ng lundmar say fenugrec: that is a common misconception. host is toolchain building context means the host system that output shall run on. However, your build_cpu is x86. 1465167202 #crosstool-ng lundmar say in* 1465167211 #crosstool-ng fenugrec say where did I read that "host" was the machine compiling the toolchain 1465167242 #crosstool-ng fenugrec say i.e. in my case, build == host != target 1465167267 #crosstool-ng fenugrec say yeah, we're saying the same thing I think 1465167281 #crosstool-ng fenugrec say build = x86, host = x86, target = SH 1465169319 #crosstool-ng fenugrec say lundmar: I think I found the problem. internally newlib does some string matching, for arm it wildcards it with "arm*", but "sh" doesn't have the * 1465169404 #crosstool-ng lundmar say fenugrec: sounds likely, newlib is probably not up to speed with sh* support 1465169530 #crosstool-ng ghostbsdun say Hello. Is there some asticles or tutorials how to build Linux From Scratch with crosstool-ng? 1465169535 #crosstool-ng ghostbsdun say *articles 1465169875 #crosstool-ng lundmar say ghostbsdun: if you intend to us ct-ng to cross build LFS, then you might want to have a look at http://clfs.org 1465170005 #crosstool-ng ghostbsdun say lundmar, yes, I'm reading CLFS now. I'm interested of how some steps can be simplified with ct-ng 1465170186 #crosstool-ng lundmar say ghostbsdun: a little word of advice, (c)lfs is a lot of manual work. If you want to cross build say a small filesystem for !x86 then you are better off using a firmware build tool which supports cross compiling. 1465170237 #crosstool-ng lundmar say but (c)lfs is somewhat good for learning 1465170400 #crosstool-ng ghostbsdun say lundmar, I'm developing some king of package manager, which successfully builds LFS tools now. I don't like that programs run in host system's environment (see entry filesystem). How crosstool-ng deals with installation prefix? 1465170418 #crosstool-ng ghostbsdun say *some kind 1465170656 #crosstool-ng lundmar say ghostbsdun: ct-ng simply creates a toolchain that you can install at any location and use with clfs. 1465170819 #crosstool-ng ghostbsdun say lundmar, ok, thank you. I just don't fully understand place of each tool (cross-toolchain, temporary toolchain) in the build process. Will learn further 1465170910 #crosstool-ng lundmar say ghostbsdun: sorry, can't help you there. I'm not familiar with the intricate details of LFS. 1465170991 #crosstool-ng lundmar say ghostbsdun: you could also take a look at http://buildgear.io - it uses ct-ng to build filesystems easily. 1465171009 #crosstool-ng lundmar say cross built naturally 1465171048 #crosstool-ng lundmar say it's kind of inbetween LFS and buildroot/OE - it's simple. 1465171058 #crosstool-ng ghostbsdun say lundmar, looks interesting. Is it something like buildroot? 1465171140 #crosstool-ng lundmar say ghostbsdun: yeah, but I think you will find it more straightforward. If you want to create small/medium sized filesystem from scratch or not then it is a good choice.