#49679: perl5.16 and 5.22 have invalid -lcrypt flag ---------------------------------+-------------------------------- Reporter: ian.cheong@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: perl5.16, perl5.22 | ---------------------------------+-------------------------------- Changes (by ryandesign@…): * port: => perl5.16, perl5.22 Old description:

perl5.16 and 5.22 build fails.

{{{ :info:build perlmini.o opmini.o miniperlmain.o gv.o toke.o perly.o pad.o regcomp.o dump.o util.o mg.o reentr.o mro.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o -ldl -lm -lcrypt -lutil -lc :info:build ld: library not found for -lcrypt :info:build collect2: ld returned 1 exit status :info:build ld: library not found for -lcrypt :info:build collect2: ld returned 1 exit status :info:build lipo: can't open input file: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_perl5.16/perl5.16/work/.tmp/cco5fdbS.out (No such file or directory) :info:build make: *** [miniperl] Error 1

}}}

I understand that -lcrypt is meant to be not used on macos. https://trac.macports.org/wiki/snc/portfile_dev

Prior versions of perl5 were operating correctly.

(Trying to figure out how to patch the portfile, but not finding it simple...)

New description: perl5.16 and 5.22 build fails. {{{ :info:build perlmini.o opmini.o miniperlmain.o gv.o toke.o perly.o pad.o regcomp.o dump.o util.o mg.o reentr.o mro.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o -ldl -lm -lcrypt -lutil -lc :info:build ld: library not found for -lcrypt :info:build collect2: ld returned 1 exit status :info:build ld: library not found for -lcrypt :info:build collect2: ld returned 1 exit status :info:build lipo: can't open input file: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_perl5.16/perl5.16/work/.tmp/cco5fdbS.out (No such file or directory) :info:build make: *** [miniperl] Error 1 }}} I understand that -lcrypt is meant to be not used on macos. wiki:snc/portfile_dev Prior versions of perl5 were operating correctly. (Trying to figure out how to patch the portfile, but not finding it simple...) -- Comment: I have not heard of this problem before, and the perl ports are in heavy use, which makes me think there is something specific to your computer that is causing this problem. Please attach the main.log file generated by your failed installation attempt. If it turns out to be something we need to fix, we should test the other versions of perl too: perl5.8, perl5.10, perl5.12, perl5.14, perl5.18, perl5.20. -- Ticket URL: <https://trac.macports.org/ticket/49679#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

#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

#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@…): {{{ $ port provides /opt/local/lib/libcrypt.dylib /opt/local/lib/libcrypt.dylib is not provided by a MacPorts port. }}} I do have +universal flag as default since I still have some alive older macs. -- Ticket URL: <https://trac.macports.org/ticket/49679#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X

#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@…): So I deleted /opt/local/lib/libcrypt.dylib and everything seems fine. I upp'd the main.log before deleting the file. (It can be deleted.) OK for perl5.16 and 5.22. I thought when this problem started, I tested previous perl version which had no problems. /opt/local/lib/libcrypt.dylib was an alias dated 13/6/2013 to current version of libgcrypt.20.dylib which still exists. I presume some previous package wrote it???? (I don't mess with /opt.) -- Ticket URL: <https://trac.macports.org/ticket/49679#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

#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@…): (FWIW maybe it was gambas which has similar dates.) -- Ticket URL: <https://trac.macports.org/ticket/49679#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X