00:15:52 buc sent you an email with a link. 00:20:50 wyatt8740 Could you check if you can build SeaMonkey from comm-central. Might need further build changes. The comm-central version will not run but should build. 00:34:48 frg_away: i can try, but it took me five hours of work to get as far as i did with the last one (mostly setting up the cross compiler), so I can't promise to do it quickly 00:35:03 hopefully my build env will be good now 00:35:15 and rustc won't be complaining 00:37:19 wyatt8740 There should be minimal differences only. WG9s builds daily. I now and then only. 00:37:54 alright. i will make an attempt (mozilla/ goes underneath comm-central, right?) 00:37:58 not the other way around? 00:38:23 no all build with mozilla on top now 00:38:53 and comm-central is expected to be under it in a direcroty named comm 00:39:40 As 2.53. comm dir in the mozilla one. Or just try to build Firefox only without comm Should make no difference and if this fails it is because something is not right in the environment. 00:41:26 so in the .mozconfig you need to specify "ac_add_options --enable-application=comm/suite" 00:42:33 for reference the mozconfig file i use is in https://www.wg9s.com/comm-central/build/mozconfig_sm 00:43:00 that is the one I use for 64-bit linujx builds 00:43:07 linux 00:44:38 all of the mozconfig files are in https://www.wg9s.com/comm-central/build/ 02:02:17 frg_away: firefox requires node.js though 02:02:24 and ppc32 does _not_ have node.js 02:02:34 i guess my cross compile might work anyway 02:02:58 will try to test it, making dinner 02:03:10 thanks, all