#28220: failed to build p5-net-libidn 0.12_0 --------------------------------------+------------------------------------- Reporter: Lars.Rasmusson@… | Owner: mni@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: p5-net-libidn --------------------------------------+------------------------------------- Changes (by macsforever2000@…): * owner: macports-tickets@… => mni@… Old description:
To build p5-net-libidn, one must first create the make file from Makefile.PL
When I tried to install the latest version, 0.12_0, the Makefile that was created didn't pick up the correct settings from the $libdir and $incdir which caused the linking to fail because it tried to link with the standard os x libraries.
The command that failed was the
cd <workdir> && /opt/local/bin/perl Makefile.PL INSTALLDIRS=vendor
The "perl Makefile.PL" command can take the arguments --with-libidn and --with-libidn-inc and I was able to use them to set the correct paths,
cd <workdir> && /opt/local/bin/perl Makefile.PL --with- libidn=/opt/local/lib --with-libidn-inc=/opt/local/include
but there is probably a better way to solve that. Perhaps the correct paths could/should be picked up automatically - but for some reason they weren't.
I just wanted to file this as a bug in case someone else has a problem with it.
New description: To build p5-net-libidn, one must first create the make file from Makefile.PL When I tried to install the latest version, 0.12_0, the Makefile that was created didn't pick up the correct settings from the $libdir and $incdir which caused the linking to fail because it tried to link with the standard os x libraries. The command that failed was the {{{ cd <workdir> && /opt/local/bin/perl Makefile.PL INSTALLDIRS=vendor }}} The "perl Makefile.PL" command can take the arguments --with-libidn and --with-libidn-inc and I was able to use them to set the correct paths, {{{ cd <workdir> && /opt/local/bin/perl Makefile.PL --with- libidn=/opt/local/lib --with-libidn-inc=/opt/local/include }}} but there is probably a better way to solve that. Perhaps the correct paths could/should be picked up automatically - but for some reason they weren't. I just wanted to file this as a bug in case someone else has a problem with it. -- -- Ticket URL: <https://trac.macports.org/ticket/28220#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS