On 2016/10/18 21:29, Jeremie Courreges-Anglas wrote: > Pascal Stumpf <[email protected]> writes: > > > > I don't claim to know much about objc, but I think the correct solution > > would be to either rename libobj from lang/gcc to libeobjc (and make the > > port use it) or go the fortran route and remove support from base. > > According to sqlports, openvpn-auth-ldap is the only port with objc in > > WANTLIB (GNUstep stuff uses clang + libobjc2). > > Same stance wrt objc, I think we should remove it from base. I took > a quick look at this openvpn plugin (last update from 2007...) and it > looks like just using gobjc from ports isn't enough. Debian has patches > to allow building with gcc 4.6+, those patches look interesting but > I did not dig further. There also are mentions of gnustep in their > package.
So openvpn-auth-ldap is broken again because of the libobjc conflict; it picks up the higher-numbered version from /usr/local/lib ahead of the lower-numbered version in /usr/lib (i.e. higher version number trumps being earlier in the path). As this is now broken anyway, and other objc ports use libobjc2 instead, there's not really any disadvantage in removing libobjc from base. Then openvpn-auth-ldap would need fixing to work with whichever of ports libobjc and libobjc2 is easiest..
