----- Original Message ----- > > Yes. I think the static library was only split out into its own > > RPM > > from a relatively recent Fedora (whichever was being developed in > > Feb-Mar 2011, as that's when we hit this same error), but it's > > preferable > > to link dynamically in all cases. I believe the library was split > > out because > > pretty much everything else links dynamically and doesn't need it. > > Shouldn't it be general case for OpenJDK on Linux to use dynamic > linking with stdc++ like all others libs ? > If so STATIC_CXX=false should be generalized for now only RH but all > Linux distros isn't it ? >
Yes, I'd suggest it is set on all GNU/Linux builds. IcedTea sets it, so most GNU/Linux distro packages are going to be built with it set, as they use that, AFAIK. As I say, I'd go even further and have it as the default for OpenJDK. It's what I believe most developers would expect the behaviour to be. Having it linked statically makes sense for Oracle distributing a binary blob they want to work anywhere, but not for distro packages or something you've built yourself. If there is a security issue with libstdc++, a static build means OpenJDK needs to be rebuilt as well. If it's linked dynamically, it doesn't. -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
