> > 1. you patch the source code if necessary > > Is there a 'recommended' format for patches in the > Solaris environment? > > Is this the correct commands to create a patch: > > diff -u old_file new_file > > and to apply the patch: > > patch -i patch_file file_to_be_patched > > or is there some other tricks that I should be aware > of?
That's pretty much it. A scalable way would be to write the patches into the source code directory (so that the source code remains intact), then use a Makefile and have `make` patch the source code for you right before the compilation. This also implies that the patched code would either have to be written out into a separate file, and the Makefile would have to account for that, or that you would have a prepackaged source code package in /var/spool/pkg/. Either way, with a little bit of forethought and engineering, one can easily build a nice scalable system to get the sw to seamlessly compile on Solaris (and any other UNIX, for that matter) by just using the out-of-the-box tools that come with the Solaris OE. The hardest part in all of this is patching the GCC, Linux-centric code and getting it to compile... This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
