| # 02:06:31 | cpackham | quits : Ping timeout: 250 seconds |
| # 02:51:40 | cpackham | joins #crosstool-ng |
| # 05:33:18 | cpackham | quits : Ping timeout: 252 seconds |
| # 06:12:10 | cpackham | joins #crosstool-ng |
| # 06:22:48 | cpackham | quits : Ping timeout: 252 seconds |
| # 07:36:40 | milkylainen | I bumped binutils locally. And did arm, arm64 and x86_64 on latest with my local embedded targets. I use mostly the latest and greatest of everything. |
| # 07:37:42 | milkylainen | I didn't have any problems with the previous binutils, but it had a CVE which I decided to plug. As toolchain binutils parts can be dragged to target. |
| # 07:37:59 | milkylainen | fwiw, I had no issues with the new binutils, but that isn't saying much. |
| # 09:41:58 | DEATH | quits : Quit: leaving |
| # 18:24:58 | taw | joins #crosstool-ng |
| # 18:25:53 | taw | hello, what is the latest version of crostool-ng that supports creating toolchains with glibc 2.12.0? thank you |
| # 18:32:40 | milkylainen | 2.12? Wow. That's old. |
| # 18:34:24 | taw | unfortunately I have customers that use old systems and I cannot break the compatibility. currently I am on gcc 4.9 + glibc 2.12 and I want to increase the gcc version |
| # 18:35:25 | milkylainen | 2.12.1 was removed from after 1.25 afacit. |
| # 18:36:44 | milkylainen | So the latest release should still have 2.12.1 marked as obsolete. |
| # 18:36:52 | taw | yep, i saw the changelog, but i did not see anything about 2.12.0. |
| # 18:37:19 | taw | not sure that if i compile with 2.12.1, it will work on computers with glibc 2.12.0 |
| # 18:37:19 | taw | it's so old that very few info about it :) |
| # 18:39:48 | milkylainen | I don't think glibc tends to break stuff that big between versions. |
| # 18:43:18 | milkylainen | https://github.com/bminor/glibc/compare/glibc-2.12...glibc-2.12.1 |
| # 18:45:14 | milkylainen | What gcc version do you intend to bump to= |
| # 18:45:15 | milkylainen | ? |
| # 18:45:54 | taw | gcc? as new as possible :), glibc is the limitation |
| # 18:46:04 | taw | (thank you for the github link) |
| # 18:48:03 | taw | i am not sure if they break stuff or not, maybe i should ask on their mailing list, i have to make sure that it does not break :) |
| # 18:49:02 | milkylainen | I'd use the latest ct-ng in that case and experiment. |
| # 18:49:14 | milkylainen | I'd probably choose a specific version and port the patches. |
| # 18:49:22 | milkylainen | If there are any. |
| # 18:49:27 | milkylainen | The diffset looks very minor,. |
| # 18:51:39 | milkylainen | Are you going to rebuild everything or just a few binaries? |
| # 18:52:19 | milkylainen | If you're rebuilding everything my guess is that a lot of things are going to break. |
| # 18:52:28 | milkylainen | But yeah. |
| # 19:03:36 | taw | i will be rebuilding all the projects with all the binaries... i will check on glibc mailing list, thanks |
| # 19:10:30 | milkylainen | np. I was thinking about upping the gcc. It usually doesn't like old code. :) |
| # 19:15:47 | taw | quits : Quit: Client closed |