On 2013-07-12 19:54, Alan Coopersmith wrote:
On 07/12/13 10:14 AM, Jim Klimov wrote:
Possibly, later releases of SS12.3 patches (if publicly available)
fixed the problem - after all, Oracle would be using it to compile
their Solaris, and likely hit similar problems; I am not aware of
anything trying that with illumos.

Yes, we apply compiler patches or support repository updates to the
Studio compilers we use to build Solaris itself - always have, I
don't think there has ever been a release we used without some fixes
for a corner case only hit compiling/running the complex code in the OS
(especially that in kernel space, which has very different constraints
  than applications do).

The problem with those for OI is simply that they require paying for
a Studio support contract to get the patches or support repo access.

The Studio 12.0 + patches set used for compiling OpenSolaris was made
freely available when we were making it possible for outside people
to contribute to OpenSolaris - since that ended, the newer Studio +
patches sets have not been given away for free.



By the way, do you know what the corporation's legal stance would
be if some member(s) of the community would buy subscription for
the Studio, and either use the most recent compiler with patches
to build releases of the competing OS, or make a compile server
(or farm thereof) for other community members to use and test
their developments with recent Studio compilers for free?

The latter might be questionable due to clauses on leasing (though
one might argue that for use within a community - this is like one
organization, and for free is not leasing); but at least releases -
there would be no road-blocks to release Solaris-like OSes built
with Oracle technology? ;)

Thanks if you have a chance to clarify any of this,
//Jim

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to