[MacPorts] #49679: perl5.16 and 5.22 have invalid -lcrypt flag
MacPorts
noreply at macports.org
Thu Dec 24 03:36:49 PST 2015
#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 mojca@…):
Replying to [comment:6 ian.cheong@…]:
>
> {{{
> $ port provides /opt/local/lib/libcrypt.dylib
> /opt/local/lib/libcrypt.dylib is not provided by a MacPorts port.
>
> }}}
Please backup that file just in case, then delete it and run
{{{
sudo port clean perl5.22
sudo port install perl5.22
}}}
I assume that would work.
Are you able to figure out where this file came from (possibly with help
of the timestamp of the file)? In any case, unless the file has been
installed by MacPorts, having it there is considered a "bug" on your
machine or a "bug" in the software that installed that file to that
location, not a bug in MacPorts.
Sometimes "badly designed" software packages put files under `/opt/local`,
but those cases should be reported as problems to distributors of such
packages.
One could also argue that Perl should not use `libcrypt` on Mac at all (I
don't know what that library does, so please don't take my words for
granted). Honestly I don't know why the configure script first figures out
that it should be ok to use that flag and later fails to build. But this
is something that you should discuss with upstream Perl developers rather
than with MacPorts packagers.
> I do have +universal flag as default since I still have some alive older
macs.
That should not be relevant in any way.
--
Ticket URL: <https://trac.macports.org/ticket/49679#comment:7>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list