| Solaris |
|
|
ON sources that build cleanly with gcc are now available. See the ONNV policy, detailed rationale, and the implementation addendum, which describes how shadow compilation works, what it costs, and why we believe it's a useful addition to the ON build process. It's important that everyone building ON follow the flag day instructions before attempting to build the newest versions of ON.
It's been far too long in coming, but the latest sources from the gcc project gate, based on the build 22 drop, are now making their way out to the SDLC. Almost 2/3 of all the gcc-related bugs have been fixed in ON proper, but that still leaves about 140 bug fixes in gcc-gate.
With the build 22 delivery, I've removed the custom compilers from the downloads page; they're no longer needed. Instead, you should pick up Solaris Express Community Edition build 22 or newer and use the gcc found in /usr/sfw/bin to build. This also means it is no longer necessary to set GNU_ROOT. Upgrading to build 22 will also get you past a flag day that will be coming in build 25 (see
the mailing list for the details.
Although it took a bit longer than expected, the gcc project gate sources are now available. You can now build on SPARC and x86 with gcc.
The build is now completely warning, error, and lint-clean, and everything that is part of OpenSolaris can be built with gcc. The only piece of the closed tree which cannot be built with gcc is dmi, explained in bug 6270167 below.
gcc-specific bugs fixed in the gate:
Updated known issues with GCC:
gcc-specific bugs fixed in the gate:
non-gcc bugs previously thought to be gcc-specific:
gcc-specific test failures root-caused:
New gcc-specific bugs found today:
With 2 exceptions, all of ON now builds with our custom gcc 3.4.3. The compiler is frozen, and the gate is closed except to stoppers. We're also releasing gcc-built BFU archives to the pilot for both x86 and SPARC; see the downloads page to pick them up. These are full ON builds, so they will be removed prior to launch and cannot be redistributed, even after launch. Get them now, and sign up for the gcc mailing list and report any problems there.
You can build nearly all of ON with a custom gcc 3.4.3. This page lists outstanding problems, providing bugIDs when appropriate. Note that many bugs are open against ON but are fixed in one of our workspaces; these are too numerous to be listed here.
Known issues with GCC:
Terms of Use
|
Privacy
|
Trademarks
|
Copyright Policy
|
Site Guidelines
|
Site Map
|
Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
© 2012, Oracle Corporation and/or its affiliates.