| # 04:51:38 | ctngbot | joins #crosstool-ng |
| # 04:51:50 | bhundven | no clue why it dies sometimes. need to read logs |
| # 04:58:47 | blueness | joins #crosstool-ng |
| # 05:07:08 | bhundven | setup a crontab to keep the http://crosstool-ng.org/git repository updated |
| # 05:07:36 | bhundven | (in case github goes down... because... that never happens... <.< ... >.> ) |
| # 09:09:56 | blueness | quits : Quit: blueness |
| # 11:29:14 | blueness | joins #crosstool-ng |
| # 12:09:06 | blueness | quits : Quit: blueness |
| # 12:10:05 | blueness | joins #crosstool-ng |
| # 12:28:42 | blueness | quits : Quit: blueness |
| # 12:30:20 | blueness | joins #crosstool-ng |
| # 15:16:52 | ttcd | quits : Quit: Connection closed for inactivity |
| # 15:27:00 | blueness | quits : Quit: blueness |
| # 16:10:49 | aneyman | quits : Ping timeout: 245 seconds |
| # 16:15:01 | aneyman | joins #crosstool-ng |
| # 17:55:44 | aneyman | quits : Ping timeout: 260 seconds |
| # 18:16:31 | aneyman | joins #crosstool-ng |
| # 18:18:37 | blueness | joins #crosstool-ng |
| # 18:22:40 | aneyman1 | joins #crosstool-ng |
| # 19:16:08 | blueness | quits : Quit: blueness |
| # 19:34:50 | wbx | joins #crosstool-ng |
| # 19:35:14 | wbx | aneyman1: hi. how do you generate uClibc-ng configs? do you use your own defconfigs? |
| # 19:35:28 | aneyman1 | hi |
| # 19:35:32 | wbx | aneyman1: have you seen discussion on the mailinglist? |
| # 19:35:39 | wbx | aneyman1: and thanks for the macos patch |
| # 19:35:58 | aneyman1 | no, in 1.21 (I think) Bryan added some machinery to generate uclibc's configs based on configured crosstool-ng settings |
| # 19:36:42 | aneyman1 | uclibc-ng's or crosstool-ng's ML? |
| # 19:36:50 | wbx | uclibc-ng |
| # 19:36:58 | wbx | aneyman1: are you subscribed? |
| # 19:37:16 | aneyman1 | no, just peruse it when I need it :) |
| # 19:37:27 | aneyman1 | let me have a look |
| # 19:41:11 | aneyman1 | that makes sense, just have a look at crosstool-ng's machinery around this where we first determine the options to set in the .config, and then try to filter out the multilib options that uclibc-ng set as well |
| # 19:42:11 | wbx | do you use make defconfig somehow? |
| # 19:42:28 | wbx | or what do you mean with makes sense? :) |
| # 19:43:20 | wbx | while summarizing the uClibc-ng users, I forgot to take a look at the crosstool-ng methods, sorry :) |
| # 19:43:27 | aneyman1 | no, crosstool-ng has its own "defconfig" for all architectures that it whips into submission :) |
| # 19:43:50 | aneyman1 | https://github.com/crosstool-ng/crosstool-ng/blob/master/contrib/uClibc-defconfigs/uClibc-ng.config |
| # 19:43:56 | wbx | aneyman1: so you are okay, with any defconfig removal? |
| # 19:44:06 | aneyman1 | yep |
| # 19:44:28 | wbx | i think MALLOC_GLIBC_COMPAT can be removed :) |
| # 19:44:39 | wbx | it is default and symbol is removed |
| # 19:44:43 | aneyman1 | there was another proposal in the thread, regarding dropping the architecture bits from .config (or at least I understood it like that) |
| # 19:45:14 | wbx | i don't think .config architecture bits are meant |
| # 19:45:15 | aneyman1 | that would be a welcome change, it will simplify crosstool-ng's build script for uclibc-ng |
| # 19:45:30 | wbx | but i might misunderstood it |
| # 19:47:19 | wbx | when do you release? can y_morin give you admin access, if bryan doesn't give up maintainership? |
| # 19:47:41 | aneyman1 | I was talking about this: > > For example, the ARC arcv2_defconfig and defconfig only differ by the |
| # 19:47:42 | aneyman1 | > > option CONFIG_ARC_CPU_HS, whose only purpose is to pass -mcpu=archs. |
| # 19:47:42 | aneyman1 | > > Shouldn't be the solution used on ARM (removing all options to select |
| # 19:47:42 | aneyman1 | > > the compiler flags, and leave it to the user to pass the appropriate |
| # 19:47:42 | aneyman1 | > > options) be used as well ? |
| # 19:48:22 | aneyman1 | re release: I want to have the build pass on cygwin, ubuntu/centos & macos (we've had a sudden influx of macos users lately, not sure why :) |
| # 19:48:31 | wbx | ah, okay. CONFIG_ARC_CPU_HS is only used for -mcpu, then this should be removed together with Rules.mak bits |
| # 19:49:21 | wbx | i think i tried crosstool-ng on my mac in the past, but it was always broken :) |
| # 19:49:23 | aneyman1 | currently the first three pass, macos had at least two failures - one with the older kernels header-install failure (that I need to fix yet) and this 'install -D' issue in uclibc/uclibc-ng |
| # 19:49:35 | aneyman1 | well, you might try it soon :) |
| # 19:50:16 | aneyman1 | if all goes well, I'll tag rc1 this week, enter the code freeze and run the final test cycle |
| # 19:50:35 | wbx | great. |
| # 19:50:36 | aneyman1 | and yes, y_morin gave me the credentials for publishing on crosstool-ng.org |
| # 19:51:37 | aneyman1 | I |
| # 19:51:52 | aneyman1 | I've had an interesting PR popping up just today :) |
| # 19:51:58 | aneyman1 | https://github.com/crosstool-ng/crosstool-ng/pull/627 |
| # 19:52:07 | aneyman1 | I am tempted to include into 1.23 :) |
| # 19:52:38 | aneyman1 | but on the other hand, I don't want to disturb the build unless absolutely necessary at this time :) |
| # 19:53:03 | aneyman1 | need to set up a freebsd VM and add this to the test cycle :) |
| # 19:53:48 | wbx | would you add new arch support after 1.23? openrisc or sth like that? |
| # 19:55:29 | wbx | oh, do you check in ct-ng menuconfig for impossible combinations? |
| # 19:57:57 | aneyman1 | re new arches: well, ideally I should be testing the runtime somehow |
| # 19:58:12 | aneyman1 | I don't have anything but x86 & arm at this time :) |
| # 19:58:28 | wbx | qemu is an option? |
| # 19:59:08 | aneyman1 | re impossible combinations: you mean, like "is this arch supported by uclibc-ng"? then no, not currently, although it is in the todo list |
| # 19:59:56 | aneyman1 | qemu is an option, but for some reason the stock one from ubuntu crashes on my machine and I never got to configure/build/setup one from their repo |
| # 19:59:58 | wbx | or choose m68k, binary format fdpic (-> coldfire is flat only, no FDPIC support) |
| # 20:00:25 | aneyman1 | that is some long forgotten knowledge |
| # 20:00:28 | wbx | aneyman1: i always use latest qemu release on debian/jessie and macosx. |
| # 20:01:07 | aneyman1 | haven't got my hands on the coldfire since, like, 2005 or so |
| # 20:02:33 | aneyman1 | I am first struggling to make all samples build on all supported hosts |
| # 20:02:40 | aneyman1 | and keep the packages up to date |
| # 20:03:38 | aneyman1 | when I started on crosstool-ng, most samples were broken on cygwin and macos; and Linux samples pass rate was about 50% |
| # 20:04:09 | wbx | samples are predefined toolchain configurations? do you publish binaries of all samples? |
| # 20:06:51 | aneyman1 | yes. no. |
| # 20:06:52 | aneyman1 | :) |
| # 20:07:37 | aneyman1 | it is basically a claim that "we tested this and it built fine - so you can use it as a starting point" |
| # 20:08:21 | aneyman1 | because obviously we cannot possibly test all possible permutations of host/target/package versions/gcc options/binutils options etc |
| # 20:08:30 | wbx | that is totally okay, i wouldn't do anything else |
| # 20:49:25 | enunes | quits : Ping timeout: 240 seconds |
| # 21:02:34 | blueness | joins #crosstool-ng |
| # 21:39:46 | blueness | quits : Quit: blueness |
| # 22:29:27 | blueness | joins #crosstool-ng |