On Mon, Oct 16, 2017 at 2:58 AM, zyx <z...@gmx.us> wrote: > On Mon, 2017-10-16 at 01:56 -0700, Zac Medico wrote: >> In fact, this is all that I really needed to change in >> CMakeLists.txt: > > Hi, > thanks for a quick response. It makes more sense now. > > I tried to reproduce the build failure with OpenSSL 1.1.0f downloaded > from https://www.openssl.org/source/ and I cannot reproduce it (neither > with my 1.1.0f provided by my distribution, which also provides a > compat package with OpenSSL 1.0.2j). I see with ldd that the > podofosign uses my locally built OpenSSL. That's with PoDoFo svn > checkout at revision 1859, which compiles without any issue here, no > missing symbols reported by the compiler. I configured OpenSSL > with --prefix only. > > Could it be that you configure OpenSSL more strictly? Also, ldd on the > podofosign tool shows only linking against libcrypto. Does it compile > against other OpenSSL libraries for you? > > I'm not against the change, I'm only looking for a reproducer. > Thanks and bye, > zyx
Oh yes, now I see that my openssl-1.1.0f is configured with the disable-deprecated option. I suppose it's worthwhile to support this case, for forward compatibility? -- Thanks, Zac ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
