John Rice wrote:
> How to make it easy to build OSS on Solaris? > ---------------------------------------- > Is the solution to include the current JDS Common Build Environment - > has all of the GNU/ Apache build utils like automake, autoconf, > libtools, make, ant ...? > > laca>> I'd prefer to fixit at thesoruce and come up with a policy for GNU > compatibility in Solaris. There have been efforts for that > in the past[3][4]. Now that [4] is becoming history, we need > a new policy to replace it. Joe Kowalski should be involved in > any discussion about this. > > Brian>> > 1) Add Free Software development tools currently not shipped with > Solaris. This includes automake, autoconf, libtool, cvs, etc. > YES You mean like : /usr/sfw/bin/autoconf* /usr/sfw/bin/autom4te* /usr/sfw/bin/autoscan* /usr/sfw/bin/autoheader* /usr/sfw/bin/autoreconf* /usr/sfw/bin/autoupdate* and yes, we need to finish the list... > 2) Many commands in the CBE are replacements for existing apps > in Solaris. Examples include make, diff, m4, flex. We should > work with the Solaris team to enhance the Solaris versions of the > tools so we don't need to ship an extra GNU version of the tool. > Ship both, disk space is cheap. By far the simplest solution, and one I'm going to push for is as follows: 1) Add gnu tools into Solaris. Versions with identical names will get a prepended 'g', _and_ will appear with their original (conflicting) name in /usr/gnu/bin (analogous to /usr/xpg*/bin) 2) Move commands and libraries with unique names and adequate stability from /usr/sfw/* into /usr/bin, /usr/lib, etc. In this manner, anyone wishing to build in a straight gnu world can prepend /usr/gnu/bin to their path. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts
