On Sun, 2013-01-13 at 20:28 -0800, Linda Walsh wrote:
Oh ****. Dissolution of steering committee for standard C library, replaced by whoever happens to be doing development on glibc at the time. Sounds like a recipe for total chaos. Sounds like an even better reason for static linking (personally I think all of the programs used for 'boot' (ones that used to live in a subdir of /), should be statically linked. Have had several times when statically linked progs saved my butt, and conversely, am increasingly having problems with dynamic libraries that are needed for boot being located on what was traditionally a separate partition (/usr)... The straw that broke my adaptability was making mount dependent on partitions that haven't been mounted yet. A perfectly good reason to make the mount on /sbin (or /bin) statically built.)...
I just deployed an app compiled on 12.1 to run on an 11.2 system. I thought I would need to statically link it since it was built 'in the future'. Oddly, this was not needed. Which was a surprise. As to statically linking, there are a few libraries that won't link statically. Unless I am mistaken, libc is one of them. The logic for that is that it is so closely tied to the kernel that things will be better if libc and the kernel match. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org