| # 00:06:46 | lundmar | quits : Quit: WeeChat 1.4 |
| # 00:56:27 | cheetim | joins #crosstool-ng |
| # 01:00:32 | cheetim | quits : Ping timeout: 240 seconds |
| # 01:22:03 | blueness | quits : Quit: blueness |
| # 01:22:53 | blueness | joins #crosstool-ng |
| # 01:24:36 | blueness | quits : Client Quit |
| # 01:44:24 | cheetim | joins #crosstool-ng |
| # 01:46:50 | cheetim | quits : Read error: Connection reset by peer |
| # 01:49:06 | blueness | joins #crosstool-ng |
| # 02:02:14 | caveat | joins #crosstool-ng |
| # 02:38:58 | casantos | joins #crosstool-ng |
| # 02:41:24 | casantos | hi. there is a bug in scripts/functions that causes a crash when a git repository can not be cloned |
| # 02:42:55 | casantos | diff --git a/scripts/functions b/scripts/functions |
| # 02:42:55 | casantos | index 62d264e..ca7713a 100644 |
| # 02:42:55 | casantos | --- a/scripts/functions |
| # 02:42:55 | casantos | +++ b/scripts/functions |
| # 02:42:55 | casantos | @@ -928,7 +928,7 @@ CT_GetGit() { |
| # 02:42:56 | casantos | else |
| # 02:42:58 | casantos | # Woops... |
| # 02:43:02 | casantos | CT_DoExecLog ALL rm -rf "${dir}" |
| # 02:43:04 | casantos | - CT_DoLog Debug "Could not clone '${basename}'" |
| # 02:43:06 | casantos | + CT_DoLog DEBUG "Could not clone '${basename}'" |
| # 02:43:08 | casantos | return 1 |
| # 02:43:10 | casantos | fi |
| # 02:43:12 | casantos | } |
| # 02:43:14 | casantos | this is the fix |
| # 03:16:35 | cheetim | joins #crosstool-ng |
| # 03:19:50 | jyelloz | quits : Read error: Connection reset by peer |
| # 03:20:03 | jyelloz | joins #crosstool-ng |
| # 03:21:08 | casantos | parts #crosstool-ng |
| # 05:27:15 | lundmar | joins #crosstool-ng |
| # 06:22:18 | perr | joins #crosstool-ng |
| # 06:22:18 | perr | quits : Changing host |
| # 06:22:18 | perr | joins #crosstool-ng |
| # 06:23:18 | perr | quits : Client Quit |
| # 07:18:51 | perr | joins #crosstool-ng |
| # 08:22:41 | hgb | joins #crosstool-ng |
| # 08:23:30 | hgb | I have a crosstool-ng-based toolchain, and I'm building a glibc separately for target (for simple upgrading of glibc when there are vulnerabilities). I need to make sure the dynamic linker is named the same thing it is in the toolchain. Does anyone know how this stuff is set up? |
| # 10:20:40 | pamaury | joins #crosstool-ng |
| # 10:52:48 | blueness | quits : Quit: blueness |
| # 10:53:39 | blueness | joins #crosstool-ng |
| # 10:59:32 | cheetim | quits : Remote host closed the connection |
| # 11:30:16 | perr | quits : Quit: Leaving |
| # 11:51:53 | blueness | quits : Ping timeout: 250 seconds |
| # 12:31:19 | cheetim | joins #crosstool-ng |
| # 12:35:52 | cheetim | quits : Ping timeout: 264 seconds |
| # 13:29:01 | Net147 | quits : Quit: Quit |
| # 13:30:44 | Net147 | joins #crosstool-ng |
| # 13:32:09 | cheetim | joins #crosstool-ng |
| # 13:36:48 | cheetim | quits : Ping timeout: 265 seconds |
| # 13:42:23 | Net147 | quits : Quit: Quit |
| # 13:45:14 | Net147 | joins #crosstool-ng |
| # 13:47:51 | cheetim | joins #crosstool-ng |
| # 13:52:14 | cheetim | quits : Ping timeout: 260 seconds |
| # 14:48:44 | cheetim | joins #crosstool-ng |
| # 14:53:13 | cheetim | quits : Ping timeout: 244 seconds |
| # 15:49:32 | cheetim | joins #crosstool-ng |
| # 15:54:07 | cheetim | quits : Ping timeout: 250 seconds |
| # 16:28:00 | pamaury | quits : Remote host closed the connection |
| # 16:31:38 | pamaury | joins #crosstool-ng |
| # 16:50:11 | cheetim | joins #crosstool-ng |
| # 16:54:47 | cheetim | quits : Ping timeout: 258 seconds |
| # 17:10:14 | c0de1 | joins #crosstool-ng |
| # 17:10:14 | c0de1 | quits : Changing host |
| # 17:10:14 | c0de1 | joins #crosstool-ng |
| # 17:12:04 | c0de1 | parts #crosstool-ng |
| # 17:51:00 | cheetim | joins #crosstool-ng |
| # 17:55:24 | cheetim | quits : Ping timeout: 258 seconds |
| # 18:21:37 | blueness | joins #crosstool-ng |
| # 18:51:52 | cheetim | joins #crosstool-ng |
| # 18:56:21 | cheetim | quits : Ping timeout: 258 seconds |
| # 19:56:31 | pamaury_ | joins #crosstool-ng |
| # 19:56:32 | pamaury | quits : Ping timeout: 258 seconds |
| # 19:57:01 | pamaury_ | is now known as: pamaury |
| # 20:53:25 | cheetim | joins #crosstool-ng |
| # 20:57:52 | cheetim | quits : Ping timeout: 250 seconds |
| # 20:58:20 | blueness | quits : Quit: blueness |
| # 21:01:19 | blueness | joins #crosstool-ng |
| # 21:03:47 | blueness | quits : Client Quit |
| # 21:04:26 | blueness | joins #crosstool-ng |
| # 21:15:48 | linuxjacques | joins #crosstool-ng |
| # 21:46:33 | lundmar | quits : Quit: WeeChat 1.4 |
| # 21:54:26 | cheetim | joins #crosstool-ng |
| # 21:58:32 | cheetim | quits : Ping timeout: 240 seconds |
| # 22:33:51 | aneyman | joins #crosstool-ng |
| # 22:34:06 | aneyman | hey |
| # 22:34:29 | aneyman | bhundven: are you (or YEM) still looking at 383? |
| # 22:34:32 | bhundven | aneyman: Hey! I've been waiting for you to show up! |
| # 22:34:46 | bhundven | I am, but I'm not sure where he left off |
| # 22:34:54 | aneyman | sorry, had some personal issues intervening |
| # 22:35:10 | bhundven | No problem! |
| # 22:37:29 | aneyman | I think 3b5da72 is the last one he reviewed |
| # 22:37:31 | bhundven | But, I really need to get back to reviewing this, so we can update/merge some of these other PR that are piling up |
| # 22:38:00 | bhundven | ok, thanks! |
| # 22:38:12 | bhundven | I'll get back to this tomorrow. |
| # 22:38:21 | aneyman | there are some minor changes he requested, I can either make those and rebase (again) or wait until we reach some other feasible milestone to push the next wave of changes |
| # 22:38:34 | bhundven | I updated the README.md |
| # 22:38:55 | bhundven | you can either rebase and loose the comments or merge and keep them |
| # 22:39:09 | bhundven | It's up to you |
| # 22:40:09 | aneyman | I think 7d36179 makes a good milestone |
| # 22:43:23 | aneyman | actually, I see that YEM had some comments on newer commits, too |
| # 22:43:34 | aneyman | I somehow missed those in the email, I guess |
| # 22:44:18 | linuxjacques | does ct-ng assume that all powerpc64 support altivec ? I'm getting "../sysdeps/powerpc/powerpc64/multiarch/strncase_l-power7.c:1:0: error: AltiVec not supported in this target" yet I never (knowingly) asked for altivec support |
| # 22:44:35 | aneyman | he had a comment on 05f0478, but did not comment on the previous commits that he reviewed them |
| # 22:49:25 | aneyman | github seems to do some funny things with the commit history |
| # 22:49:45 | aneyman | that it displays as a part of a PR |
| # 22:50:03 | aneyman | it seems rearranged and some commits seem to be missing |
| # 22:50:58 | aneyman | I think I'll rebase the branch, see how GH displays it and if it is botched again, I'll create a new PR with the remaining changes and with the feedback from this one picked up |
| # 22:51:32 | linuxjacques | do I need to set the ABI to no-altivec ? it looks like buildroot does something like this (?) |
| # 22:55:09 | cheetim | joins #crosstool-ng |
| # 22:59:43 | cheetim | quits : Ping timeout: 258 seconds |
| # 23:17:29 | pamaury | quits : Ping timeout: 260 seconds |
| # 23:55:48 | cheetim | joins #crosstool-ng |