| # 00:03:44 | imMute | quits : Ping timeout: 260 seconds |
| # 00:11:28 | imMute | joins #crosstool-ng |
| # 00:41:04 | lundmar | quits : Quit: WeeChat 1.4 |
| # 00:53:49 | blueness | quits : Quit: blueness |
| # 00:55:37 | blueness | joins #crosstool-ng |
| # 00:59:19 | fenugrec | joins #crosstool-ng |
| # 01:31:25 | fenugrec_ | joins #crosstool-ng |
| # 01:35:15 | fenugrec | quits : Ping timeout: 258 seconds |
| # 02:02:58 | fenugrec_ | is now known as: fenugrec |
| # 04:37:03 | fenugrec | quits : Ping timeout: 264 seconds |
| # 06:56:45 | lundmar | joins #crosstool-ng |
| # 09:41:33 | y_morin | joins #crosstool-ng |
| # 10:52:37 | y_morin_ | joins #crosstool-ng |
| # 10:53:36 | c0de1 | quits : Ping timeout: 260 seconds |
| # 10:53:43 | aneyman__ | quits : Ping timeout: 260 seconds |
| # 10:53:43 | y_morin | quits : Quit: leaving |
| # 10:53:45 | coffeeholic_ | quits : Ping timeout: 260 seconds |
| # 10:53:50 | y_morin_ | is now known as: y_morin |
| # 10:55:33 | c0de1 | joins #crosstool-ng |
| # 10:55:33 | c0de1 | quits : Changing host |
| # 10:55:33 | c0de1 | joins #crosstool-ng |
| # 11:01:06 | aneyman__ | joins #crosstool-ng |
| # 11:19:06 | coffeeholic_ | joins #crosstool-ng |
| # 14:00:01 | fenugrec | joins #crosstool-ng |
| # 14:28:40 | s1341 | quits : Ping timeout: 252 seconds |
| # 14:42:30 | s1341 | joins #crosstool-ng |
| # 16:49:04 | blueness | quits : Quit: blueness |
| # 16:49:45 | blueness | joins #crosstool-ng |
| # 19:26:15 | muep | quits : Remote host closed the connection |
| # 19:26:50 | muep | joins #crosstool-ng |
| # 21:51:15 | ghostbsdun | joins #crosstool-ng |
| # 22:06:13 | JakeSays | joins #crosstool-ng |
| # 22:06:52 | JakeSays | hey is it possible with crosstool-ng to build a toolchain hosted on windows and targeting linux/arm? |
| # 22:07:06 | JakeSays | would be built on linux |
| # 22:13:54 | lundmar | JakeSays: http://crosstool-ng.org/#canadian_build |
| # 22:14:17 | JakeSays | lundmar: lol canadian? |
| # 22:14:48 | lundmar | JakeSays: yes, that is the name of the type of build you are looking for ;) |
| # 22:14:55 | JakeSays | LOL thats funny |
| # 22:15:36 | lundmar | well, I would rather be in Canada now than then US haha |
| # 22:17:16 | JakeSays | hmm. i'd prefer to target msys/mingw than cygwin |
| # 22:19:51 | JakeSays | any plans to move to gcc 5.3? |
| # 22:19:54 | fenugrec | I wonder what a "Trump build" would consist of ? |
| # 22:20:31 | lundmar | fenugrec: exactly my point haha |
| # 22:23:39 | lundmar | JakeSays: ct-ng usually include support for the latest stable gcc at the time of ct-ng release. |
| # 22:24:14 | JakeSays | right, which was 7 months ago |
| # 22:24:23 | JakeSays | isn't 5.3 stable? |
| # 22:25:35 | lundmar | JakeSays: gcc 5.3 was released before last ct-ng release. |
| # 22:26:06 | lundmar | *latest |
| # 22:26:06 | JakeSays | lundmar: lol i know. let me rephrase my question. when is the next release of ct-ng planned? |
| # 22:26:51 | lundmar | sorry, I don't know. Someone else will have to answer that question. |
| # 22:30:54 | fenugrec | I expect the answer to be "when it's ready", or "when you take care of it" P-) |
| # 22:31:14 | JakeSays | fenugrec: lol yeah me too |
| # 22:33:04 | fenugrec | while there's some sign of life on this channel : where are the arguments / variables set just before compiling newlib ? |
| # 22:33:06 | lundmar | either way, no need to talk 5.3 when 5.4 is here :) |
| # 22:33:28 | JakeSays | its not a big issue. 5.2 is fine for what i'm doing at the moment. |
| # 22:34:03 | fenugrec | i.e. why does newlib think the target is "sh3eb" instead of just "sh", etc |
| # 22:37:17 | lundmar | fenugrec: did you have a look at scripts/build/libc/newlib.sh? |
| # 22:38:22 | fenugrec | lundmar: I thought I did, but maybe I skipped that one |
| # 22:38:55 | diorcety | quits : Read error: Connection reset by peer |
| # 22:39:13 | lundmar | well, its pretty instrumental for newlib builds ;) |
| # 22:43:40 | lundmar | fenugrec: there is also scripts/build/arch/sh.sh |
| # 22:43:41 | fenugrec | 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 |
| # 22:44:18 | lundmar | sh* is simply not well tested platform |
| # 22:44:25 | lundmar | +a |
| # 22:44:29 | fenugrec | you don't say : )) |
| # 22:44:52 | lundmar | I would put it in the exotic category haha |
| # 22:49:31 | y_morin | quits : Quit: Nighty Night! |
| # 22:50:05 | fenugrec | also, wtf, at some point newlib has ${host_cpu} defined to "sh3eb". Pretty sure I'm running ct-ng on an x86 |
| # 22:53:10 | lundmar | 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. |
| # 22:53:22 | lundmar | in* |
| # 22:53:31 | fenugrec | where did I read that "host" was the machine compiling the toolchain |
| # 22:54:02 | fenugrec | i.e. in my case, build == host != target |
| # 22:54:27 | fenugrec | yeah, we're saying the same thing I think |
| # 22:54:41 | fenugrec | build = x86, host = x86, target = SH |
| # 23:28:39 | fenugrec | 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 * |
| # 23:30:04 | lundmar | fenugrec: sounds likely, newlib is probably not up to speed with sh* support |
| # 23:32:10 | ghostbsdun | Hello. Is there some asticles or tutorials how to build Linux From Scratch with crosstool-ng? |
| # 23:32:15 | ghostbsdun | *articles |
| # 23:37:55 | lundmar | ghostbsdun: if you intend to us ct-ng to cross build LFS, then you might want to have a look at http://clfs.org |
| # 23:40:05 | ghostbsdun | lundmar, yes, I'm reading CLFS now. I'm interested of how some steps can be simplified with ct-ng |
| # 23:43:06 | lundmar | 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. |
| # 23:43:57 | lundmar | but (c)lfs is somewhat good for learning |
| # 23:46:40 | ghostbsdun | 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? |
| # 23:46:58 | ghostbsdun | *some kind |
| # 23:50:56 | lundmar | ghostbsdun: ct-ng simply creates a toolchain that you can install at any location and use with clfs. |
| # 23:53:39 | ghostbsdun | 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 |
| # 23:55:10 | lundmar | ghostbsdun: sorry, can't help you there. I'm not familiar with the intricate details of LFS. |
| # 23:56:31 | lundmar | ghostbsdun: you could also take a look at http://buildgear.io - it uses ct-ng to build filesystems easily. |
| # 23:56:49 | lundmar | cross built naturally |
| # 23:57:28 | lundmar | it's kind of inbetween LFS and buildroot/OE - it's simple. |
| # 23:57:38 | ghostbsdun | lundmar, looks interesting. Is it something like buildroot? |
| # 23:59:00 | lundmar | 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. |