-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
Hi, > As Gregor mentioned, the upstream bug report appears to refer to > something entirely different. Since there's no error messages in > this bug, I can't tell whether it's still a problem or not. The patch > supplied in this bug report has not been applied in the latest > upstream release of protobuf. > > I see other dlopen-related bugs upstream, but most are closed: > https://github.com/google/protobuf/issues?utf8=%E2%9C%93&q=is%3Aissue++dlopen+ > > Please let me know if this bug should still be open or not; and if > so, which upstream bug is relevant? This bug is already closed. There is no original bug report as we moved from google code to github, but related bug reports are: https://github.com/protocolbuffers/protobuf/issues/1941 https://github.com/protocolbuffers/protobuf/issues/4126 Best regards, Nobuhiro -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAl03JlkACgkQMiR/u0Ct H6aKrw/+LG5O6Vrpkg7paPLjlPYAL0NkCcq+feTdWUbprj+gdNPvZV0ZuVA7+ba/ iuyDp6V+9+XJz6rZm136cjfezefMj8uFmX4i+VcVvNwWEz/Aw0Pxk3tmrREOonmn TmQeBaCVO8zBSNzYpSmt/CXzdmgDqmtpX+hb2oUuPatklpkCNTxl7rng7lPpyQLA CJbPD/YhvvyAfNGlwvHVa0u0kBBfP8Dka/qUtY+PADbsAq66MxdnbJaqd2LxNH6o pIy+PqegJrKGsGbn61hh2eJeLd0igj/c1W11kMxyxvJSiW5R4rYPF8ga3GHHoTDP Z0OwSpEJ8Rqy0XlyMoCKK3CzAN/185WU87U7i5bR/H+GPYV12vhDBVltZAnDH7jh KitlDrz4qV3agdRzIMxAZPKw9WCF/RTLw26fe87hK/HNfc+FPyJMeHBnXL2aTcsy htuSIB8jiPkMbXKtJN2y5P2x/yXUEF74/o6MV92qp2qOCxQs2+OOagmwl/+vaQN4 1KDvNqSd5klV6BMHnZ4YEM+W2VUYOjONuxaqEOjSigTjCpHiU76K64DFkG9H5J+N tW2WD08GcgfJN9j1tyLxdHWU9fxbONoX+F8oc4/rD7AcKi8L49V9re8pTZYztXTs cAEm3rOZtpksiPDL7X1ok1GRPK3mYLR62ECbjaKRVx7n4qh4yTI= =uCQf -----END PGP SIGNATURE-----
