Roman: >> However, I think I'm trying to encourage >> that such maintainers should really consider >> being involved with the module community directly. > > Yes. As a consequence this is true. > > But I even do not know yet which projects are considered > to build Solaris spec files from. It is also not clear yet > for which toolchain the spec files are built for. Should > we make it work for the gcc or the SunPro tool chain? And > what is with 64 bit support?
From Sun's perspective Sun Studio is the better choice. It tends to build better and faster code for Solaris and OpenSolaris. It typically isn't much work to make modules work with Sun Studio. The typical problem is that many modules define GCC specific compiler flags (such as "-Wall") in the configure. However, it's pretty easy to fix these configure scripts to only do so if GCC is being used, which is more appropriate. I'd say we should try to use Sun Studio unless there is a compelling reason not to (perhaps the code makes use of extensive GCC extensions that would be too much work to get working with Sun Studio). Note the entire GNOME stack we ship is built with Sun Studio, and this hasn't been such a great amount of work, really. I'm not sure about 64 bit support. It's likely more important concern for libraries that export interfaces. Brian
