http://bugs.winehq.org/show_bug.cgi?id=26643
Summary: Undefined symbols _SSLCopyPeerCertificates on Mac OS X 10.4.11 Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Mac OS X 10.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: wine-2011@ryandesign.com
Created an attachment (id=33919) --> (http://bugs.winehq.org/attachment.cgi?id=33919) build log from MacPorts
Building wine 1.3.16 or 1.3.17 with MacPorts on Mac OS X 10.4.11 with Xcode 2.5 fails with:
:info:build /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols: :info:build _SSLCopyPeerCertificates
Attached is the full log.
1.3.15 built ok on Mac OS X 10.4.
1.3.16 and 1.3.17 build fine on Mac OS X 10.6.
I did not test Mac OS X 10.5.
P.S: I am the maintainer of wine in MacPorts
http://bugs.winehq.org/show_bug.cgi?id=26643
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression CC| |austinenglish@gmail.com Component|-unknown |build-env
http://bugs.winehq.org/show_bug.cgi?id=26643
--- Comment #1 from Ryan Schmidt wine-2011@ryandesign.com 2011-04-19 03:30:30 CDT --- I'm going to guess commit 5015f388 is what caused this, since that's the commit in which the use of SSLCopyPeerCertificates was introduced, and I'll guess SSLCopyPeerCertificates is not available on Mac OS X 10.4. The commit message is "secur32: Add alternative schannel implementation for Mac OS X. It uses the native Secure Transport API rather than GnuTLS." I am configuring with --with-gnutls and gnutls is installed. But this alternative implementation seems to be getting used anyway, even when it won't work. Is there a way to tell wine I don't want this alternative implementation and to let it use gnutls as it did before? Anyway, ./configure --help lists the option --without-gnutls, which implies that --with-gnutls is the default, but that doesn't seem to be the case here anymore.
http://bugs.winehq.org/show_bug.cgi?id=26643
--- Comment #2 from Austin English austinenglish@gmail.com 2011-04-19 13:22:08 CDT --- Created an attachment (id=34224) --> (http://bugs.winehq.org/attachment.cgi?id=34224) configure check
You need a configure check for that function, something like the attached (untested). Be sure to run autoconf before testing.
http://bugs.winehq.org/show_bug.cgi?id=26643
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Mac OS X 10.4 |Mac OS X
http://bugs.winehq.org/show_bug.cgi?id=26643
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Regression SHA1| |5015f388d1cd1db86609e2414b9 | |ea660383f8dbe
http://bugs.winehq.org/show_bug.cgi?id=26643
--- Comment #3 from Ryan Schmidt wine-2011@ryandesign.com 2011-10-10 02:34:37 CDT --- I was able to get past this problem by using the following patch:
https://trac.macports.org/browser/trunk/dports/x11/wine-devel/files/patch-SS...
http://bugs.winehq.org/show_bug.cgi?id=26643
--- Comment #4 from Ryan Schmidt wine-2011@ryandesign.com 2011-10-13 12:27:28 CDT --- Actually it turns out SSLCopyPeerCertificates is available on Tiger after all, it's just called SSLGetPeerCertificates. So this patch is simpler and better:
https://trac.macports.org/browser/trunk/dports/x11/wine-devel/files/patch-SS...
http://bugs.winehq.org/show_bug.cgi?id=26643
--- Comment #5 from Juan Lang juan_lang@yahoo.com 2011-10-13 14:22:05 CDT --- (In reply to comment #4)
Actually it turns out SSLCopyPeerCertificates is available on Tiger after all, it's just called SSLGetPeerCertificates. So this patch is simpler and better:
https://trac.macports.org/browser/trunk/dports/x11/wine-devel/files/patch-SS...
In that case, it'd be preferable to dynamically load a function pointer instead.
http://bugs.winehq.org/show_bug.cgi?id=26643
--- Comment #6 from Ryan Schmidt wine-2011@ryandesign.com 2011-10-13 19:32:14 CDT --- Ok, whatever you feel is best. I'm not really a C programmer so I'm not in a position to be able to do that; I just followed one of our other developers' suggestions to arrive at the patch I provided, and it worked for me.
http://bugs.winehq.org/show_bug.cgi?id=26643
--- Comment #7 from Juan Lang juan_lang@yahoo.com 2011-10-14 09:43:54 CDT --- Sure, it works for you. My concern is that a version of Wine built on one version of MacOS should ideally work on another version of MacOS. That's why determining the appropriate function to call at runtime is the right approach, IMO.
http://bugs.winehq.org/show_bug.cgi?id=26643
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |65634bca0be94c65e739bb00c74 | |69c9ba27c6840 Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #8 from Austin English austinenglish@gmail.com 2011-10-27 13:32:46 CDT --- Fixed by http://source.winehq.org/git/wine.git/commitdiff/65634bca0be94c65e739bb00c74...
http://bugs.winehq.org/show_bug.cgi?id=26643
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2011-11-04 14:14:12 CDT --- Closing bugs fixed in 1.3.32.
-
wine-bugs＠winehq.org