In my opinion, the other consolidations should not be using illumos’ nightly. The needs of other consolidations are usually quite different from illumos, and vice versa. Trying to build “one nightly to rule them all” is difficult without close coordination between consolidations maintainers. Post diaspora, that coordination no longer exists.
Indeed, /opt/onbld indicates “ON” (short for OS/Net), which is the consolidation that illumos is derived from. I’d recommend that other consolidations create their own forks of /opt/jdsbld or /opt/gnomebld/ or whatever suits their fancy. -- Garrett D'Amore Sent with Airmail On March 10, 2014 at 10:59:38 PM, Alexander Pyhalov (a...@rsu.ru) wrote: Hello. After integration of 4522 the build doesn't fail nearly often enough we have some problems using nightly to build non-illumos consolidations. At least I couldn't fix slim_source build. Not sure about other. The question is the following: could nightly be modified so that build warnings are treated as build_extras, i.e. existing of $TMPDIR/build_warnings${SUFFIX} leads to build_extras_ok=n , not build_ok=n at https://github.com/illumos/illumos-gate/blob/master/usr/src/tools/scripts/nightly.sh#L224 ? Or is it better just to use patched nightly while building these consolidations? -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University ------------------------------------------- illumos-developer Archives: https://www.listbox.com/member/archive/182179/=now RSS Feed: https://www.listbox.com/member/archive/rss/182179/21239177-3604570e Modify Your Subscription: https://www.listbox.com/member/?member_id=21239177&id_secret=21239177-2d0c9337 Powered by Listbox: http://www.listbox.com
_______________________________________________ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev