#49679: perl5.16 and 5.22 have invalid -lcrypt flag ---------------------------------+--------------------- Reporter: ian.cheong@… | Owner: mojca@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: perl5.16, perl5.22 | ---------------------------------+--------------------- Comment (by ian.cheong@…): Are you guys saying that this advice on the macports wiki on -lcrypt is wrong? {{{ Dealing with Incompatible Flags Use a patchfile so that if upstream ever fixes their software to not use -lcrypt and your patch then breaks, you'll be able to tell why. -lcrypt specifically is a flag you find in some Linux software but which is incompatible with and unnecessary on Mac OS X. If software tries to use that flag on Mac OS X, you would write a patchfile to remove that option, but only apply the patchfile on platform darwin (MacPorts could be installed on a non-Mac operating system and you wouldn't want this particular patch to be applied there). Ideally you would report the problem to the author of the software and they would fix their configure script or whatever, so that Mac users who are not using MacPorts will also benefit from what we discovered and we can remove our patch with the next release. }}} The error is "library not found". The wiki suggests it is because "library is not needed". The only libcrypt.dylib I have is /opt/local/lib/libcrypt.dylib. No idea why macports says it is not there. I presume it is there because I installed the library trying to get rid of the error. The error appears to be caused by the unnecessary -lcrypt. What software apart from other macports ports might cause the -lcrypt flag to appear erroneously in my makefile? I will have to break all the hand-patched ports to regenerate the logs. So if it's not a problem for anybody else, just ignore it and I can keep doing what I am doing. -- Ticket URL: <https://trac.macports.org/ticket/49679#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X