# 00:14:15 |
smartin_ |
quits : Quit: leaving |
# 01:08:23 |
perr |
joins #crosstool-ng |
# 01:39:01 |
diorcety1 |
joins #crosstool-ng |
# 01:42:23 |
diorcety |
quits : Ping timeout: 260 seconds |
# 01:52:21 |
perr |
quits : Ping timeout: 265 seconds |
# 01:52:58 |
perr |
joins #crosstool-ng |
# 01:53:40 |
mingwandroid |
quits : Remote host closed the connection |
# 02:40:04 |
djerome |
quits : Remote host closed the connection |
# 02:56:59 |
perr |
quits : Ping timeout: 240 seconds |
# 02:58:03 |
perr |
joins #crosstool-ng |
# 04:32:14 |
sh4rm4 |
quits : Ping timeout: 252 seconds |
# 06:23:58 |
perr |
quits : Ping timeout: 265 seconds |
# 06:38:11 |
perr |
joins #crosstool-ng |
# 07:25:12 |
perr |
quits : Ping timeout: 252 seconds |
# 07:26:34 |
perr |
joins #crosstool-ng |
# 08:11:18 |
aalv |
joins #crosstool-ng |
# 08:40:17 |
perr |
quits : Ping timeout: 272 seconds |
# 09:18:11 |
mingwandroid |
joins #crosstool-ng |
# 09:43:20 |
mingwandroid |
quits : Read error: Connection reset by peer |
# 10:05:29 |
mingwandroid |
joins #crosstool-ng |
# 10:16:36 |
sh4rm4 |
joins #crosstool-ng |
# 10:49:05 |
aalv |
quits : Ping timeout: 252 seconds |
# 10:53:45 |
aalv |
joins #crosstool-ng |
# 11:21:26 |
frankbutt |
joins #crosstool-ng |
# 11:21:27 |
frankbutt |
parts #crosstool-ng |
# 13:32:47 |
perr |
joins #crosstool-ng |
# 13:39:38 |
perr |
quits : Ping timeout: 252 seconds |
# 14:03:16 |
perr |
joins #crosstool-ng |
# 14:44:02 |
perr |
quits : Ping timeout: 264 seconds |
# 14:45:19 |
perr |
joins #crosstool-ng |
# 14:52:41 |
perr |
quits : Ping timeout: 272 seconds |
# 15:06:05 |
perr |
joins #crosstool-ng |
# 15:14:38 |
perr |
quits : Ping timeout: 264 seconds |
# 16:30:45 |
y_morin |
joins #crosstool-ng |
# 17:42:03 |
Martell |
joins #crosstool-ng |
# 17:42:42 |
Martell |
hey y_morin :) |
# 17:43:52 |
Martell |
any idea how i override this |
# 17:43:55 |
Martell |
[EXTRA] Dumping internal crosstool-NG configuration |
# 17:43:55 |
Martell |
[EXTRA] Building a toolchain for: |
# 17:43:55 |
Martell |
[EXTRA] build = x86_64-pc-mingw64 |
# 17:43:55 |
Martell |
[EXTRA] host = x86_64-pc-mingw64 |
# 17:43:55 |
Martell |
[EXTRA] target = powerpc64-unknown-elf |
# 17:43:56 |
Martell |
[EXTRA] Dumping internal crosstool-NG configuration: done in 0.44s (at 00:27) |
# 17:44:09 |
Martell |
I want to change the build and the host |
# 17:45:14 |
y_morin |
Martell: The 'build' is thae machine that does the build of the toolchain. You can *not* change that. |
# 17:45:43 |
y_morin |
Martell: The 'host' is where the toolchain will run. By default, it is the same as host, and the toolchain will be a cros-toolchain. |
# 17:45:58 |
Martell |
okay well I'm running via msys2 |
# 17:46:10 |
Martell |
so what veriable does it get the value from |
# 17:46:17 |
y_morin |
Martell: If you want your toolchain to run on a different 'host', then you want to build a "canadian-cross toolchain". |
# 17:46:26 |
Martell |
because its different depending on how i start the shell |
# 17:46:45 |
y_morin |
Martell: 'build' is auto-computed, you can *not* change that. |
# 17:46:45 |
Martell |
no i want it to run on the same host |
# 17:47:04 |
y_morin |
Martell: Then, the values are good. |
# 17:47:15 |
Martell |
no there not :/ |
# 17:47:30 |
Martell |
I need it to end in *-mingw32 |
# 17:47:33 |
Martell |
of gcc will fail |
# 17:47:34 |
y_morin |
Martell: Why are they bad in your opinion? |
# 17:47:50 |
Martell |
[ERROR] C:/msys64/home/Martell/ct-pkg/ct-test/.build/src/gcc-4.8.2/fixincludes/fixincl.c:29:22: fatal error: sys/wait.h: No such file or directory |
# 17:47:54 |
y_morin |
Martell: Oh, but then it means you are running on a Win64 machine, right? |
# 17:48:16 |
Martell |
yup |
# 17:48:41 |
y_morin |
Martell: Then, the values *are* good, and it is a bug in gcc. |
# 17:48:49 |
Martell |
no even mingw64 has mingw64-i686-mingw32 |
# 17:49:03 |
y_morin |
OK, I don't do Windows stuff, so I can't help more. |
# 17:49:30 |
y_morin |
Martell: However, you can tell crosstool-NG to use a different host compiler |
# 17:49:42 |
Martell |
how do i do that? :) |
# 17:50:01 |
y_morin |
Martell: Just a moment... |
# 17:50:07 |
Martell |
thank you :) |
# 17:50:45 |
aalv |
parts #crosstool-ng |
# 17:50:49 |
y_morin |
Martell: In the menuconfig: Toolchain options ---> *** Build system *** --> enter the prefix for your compiler. |
# 17:51:22 |
y_morin |
Martell: They are named "Tuple", "Tools prefix" and "Tools suffix" |
# 17:51:48 |
Martell |
I'm not using menu config I'm creating a template err sample with a minimal list |
# 17:52:17 |
y_morin |
Martell: Then, go to the menuconfig, and look at the names of the symbols. |
# 17:52:30 |
y_morin |
Martell: But beware that what you are doing is *not* the way to do it. |
# 17:52:39 |
y_morin |
Martell: It is not supported at all. |
# 17:53:12 |
Martell |
I know but I don't want a really long list of variables :/ |
# 17:53:17 |
Martell |
Thanks for the help :) |
# 17:53:25 |
y_morin |
Martell: The samples (the ones bundled with crosstool-NG) are generated from existing .config files, using: ct-ng saveconfig. |
# 17:54:17 |
y_morin |
Martell: Usually, the way to get a 'sample' (also known as a 'defconfig') is to configure via the menuconfig, save and exit, and then call ct-ng saveconfig. |
# 17:54:54 |
y_morin |
Martell: Anything else is not guaranteed to work. At the very least, you have to run 'ct-ng oldconfig' to ensure all config variables are properly set. |
# 17:55:33 |
Martell |
O right I was building a sample powerpc-blah-elf |
# 17:55:43 |
Martell |
then calling ct-ng powerpc-blah-elf |
# 17:55:49 |
Martell |
and then ct-ng build |
# 17:56:12 |
y_morin |
Martell: That's the correct way to use a sample, indeed. |
# 17:56:30 |
y_morin |
Martell: But generating a sample should not be done manually. |
# 17:57:12 |
Martell |
Is there a way to use a minimal config directly ? |
# 17:57:38 |
Martell |
whithout having to add loads over pointless items to the .config |
# 17:58:27 |
y_morin |
Martell: http://code.bulix.org/u7c6vq-85524 |
# 17:58:44 |
y_morin |
Martell: Look at the samples in samples/ -> they only contain the minimal set of options. |
# 17:59:59 |
Martell |
What if I want to work from the point of a minimal set of options without going through menuconfig? |
# 18:00:17 |
Martell |
Thanks for the link it will come in handy :) |
# 18:01:22 |
y_morin |
Martell: Creating a sample manually is not guaranteed to work as you'd expect. It may work, but it may not work. YMMV... |
# 18:02:27 |
Martell |
if i added an extra option to cg-ng build |
# 18:02:58 |
Martell |
to ignore missing options so we can use a minimal without a sample |
# 18:03:13 |
Martell |
would that be accepted upstream? |
# 18:03:49 |
y_morin |
Martell: Nope. |
# 18:05:19 |
Martell |
how about an option to ct-ng that creates a full ".config" from a minimal file? |
# 18:05:39 |
Martell |
so that we can do it without messing with the samples folder |
# 18:05:39 |
y_morin |
Martell: It is already present. |
# 18:05:53 |
Martell |
really how do i do it? |
# 18:05:56 |
Martell |
:) |
# 18:07:44 |
y_morin |
No, you have to use the samples mechanism: some toolchain require additional files (eg. uClibc-based toolchains), so a simple defconfig can not be used. |
# 18:08:18 |
y_morin |
So, when I say "It is already present" I mean: "It is already present, and it is called the samples mechanism". |
# 18:55:31 |
loide |
joins #crosstool-ng |
# 18:57:07 |
mingwandroid |
quits : Remote host closed the connection |
# 19:26:03 |
mingwandroid |
joins #crosstool-ng |
# 19:43:04 |
memleak |
hello y_morin! |
# 19:43:21 |
memleak |
how are you? i just woke up |
# 19:47:05 |
Martell |
quits : Ping timeout: 245 seconds |
# 20:41:14 |
Martell |
joins #crosstool-ng |
# 21:14:28 |
memleak |
hey y_morin i am interested in being a crosstool-ng developer. |
# 21:15:08 |
y_morin |
memleak: Hello! Good! Just find something that you need in ct-ng, and send patches to the list! :-) |
# 21:15:25 |
memleak |
i've worked a lot with RTAI, embedded real-time systems and such and i want to help out |
# 21:15:40 |
memleak |
ok awesome |
# 21:15:52 |
memleak |
are you the only person with commit rights? |
# 21:16:12 |
y_morin |
memleak: Yes. I'm the maintainer, which means only me can push. |
# 21:16:49 |
memleak |
whats the method for sending patches? .patch file format email attachments? |
# 21:17:22 |
y_morin |
memleak: look in docs/ there is a tutorial. |
# 21:17:30 |
memleak |
oh lord |
# 21:17:43 |
memleak |
ok one moment |
# 21:17:49 |
y_morin |
memleak: usually, use hg do manage a local clone, add some commits, and then send them with 'hg email'. |
# 21:18:06 |
memleak |
hg email!? no way.. |
# 21:18:13 |
memleak |
thats awesome actually |
# 21:21:25 |
memleak |
thanks! |
# 22:59:58 |
smartin_ |
joins #crosstool-ng |
# 23:11:14 |
smartin_ |
quits : Quit: leaving |
# 23:35:33 |
Martell |
hey guys |
# 23:35:46 |
Martell |
CT_LOCAL_PATCH_DIR="${CT_TOP_DIR}/patches" |
# 23:36:17 |
Martell |
will that set the directoy for patches to the same folder that the .config file is in |
# 23:37:40 |
y_morin |
Martell: This is documented in: docs/3 - Configuring a toolchain.txt |
# 23:38:50 |
Martell |
Thanks y_morin :) |
# 23:42:09 |
Martell_ |
joins #crosstool-ng |
# 23:48:46 |
Martell |
quits : Ping timeout: 272 seconds |
# 23:48:47 |
mshroyer |
quits : Ping timeout: 272 seconds |
# 23:50:11 |
mshroyer |
joins #crosstool-ng |
# 23:55:24 |
y_morin |
quits : Quit: Nighty Night! |