On Mar 15, 2012, at 6:46 PM, Ryan Schmidt wrote: >> I just [1] bumped the OpenSSH rev to force a rebuild; you can either >> rebuild locally from source or wait for the change to flow through and >> then selfupdate / upgrade outdated. > > We had to do this with neon too. > > WTF? According to "otool -L', the library version numbers of libcrypto and > libssl in openssl 1.0.1 are still 1.0.0, which is their guarantee to us that > they have not changed the library interface. Do the openssl developers not > understand what a library version number is?
or maybe the ABI for openssl didn't actually change just neon/openssh are being extra conservative (requiring the headers they were built with to exactly match the library that they are runtime linked against) because of past issues with openssl minor versions? -- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
