Philip Brown wrote: > On Fri, Nov 28, 2008 at 03:37:28PM +0100, Sebastian Kayser wrote: >> >From what i see, the current/ package depends on CSWgcc3rt and its >> binaries are linked against libgcc_s.so.1. Does that mean they were >> compiled using gcc and that's where the size difference comes from? I >> did my builds with Sun Studio cc. > > Yup, most likely > > If you wanted to spend more time on it, you could recompile and tell sun cc > to optimize for size more than speed. It tends to "unroll loops" if you > highly optimize. > And/Or reduce the optimize level to plain "-O", if you are using -fast, and > compare that. Synergy is onlyl a virtual "KVM switch" after all.
Ok, i gave it another try with different optimization levels (-xO2, -xO3, without and without -xspace) and i could squeeze the file size for about 150k each (ended up with -xO3 -xspace). Updated packages are in testing/. As its still the same day, REV and thus the package file names staid the same. How do you differentiate the updated package in such a situation? Right now pkg-get (and pkgutil) won't let me upgrade the package. Cheers Sebastian _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
