[MacPorts] #44580: p5-unicode-linebreak: use /usr/bin/ar instead of ${prefix}/bin/ar
#44580: p5-unicode-linebreak: use /usr/bin/ar instead of ${prefix}/bin/ar --------------------------------+---------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch tracemode | Port: p5-unicode-linebreak --------------------------------+---------------------------------- `p5-unicode-linebreak` automatically generates a Makefile making use of `${prefix}/bin/ar`. This will break trace mode. The possible solutions to this problem are: * add a build dependency on `cctools` * change the affected Makefiles to use `/usr/bin/ar` As only one binary is required, I went the less invasive second way. -- Ticket URL: <https://trac.macports.org/ticket/44580> MacPorts <http://www.macports.org/> Ports system for OS X
#44580: p5-unicode-linebreak: use /usr/bin/ar instead of ${prefix}/bin/ar -----------------------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch tracemode Port: p5-unicode-linebreak | -----------------------------------+-------------------------------- Comment (by ryandesign@…): To prevent failure of the stub port, the `post-configure` block you added needs to be inside the `if {$subport != $name}` block (which for consistency with other perl modules should actually be a `if {${perl5.major} != ""}` block). But how does this path to `ar` get into the `Makefile` in the first place? I'd rather patch that, than patch the `Makefile` after configure. -- Ticket URL: <https://trac.macports.org/ticket/44580#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#44580: p5-unicode-linebreak: use /usr/bin/ar instead of ${prefix}/bin/ar -----------------------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch tracemode Port: p5-unicode-linebreak | -----------------------------------+-------------------------------- Comment (by ryandesign@…): Isn't this just ExtUtils::MakeMaker getting the values via Config from /opt/local/lib/perl5/5.20/darwin-thread-multi-2level/Config_heavy.pl? In which case isn't every perl module affected? -- Ticket URL: <https://trac.macports.org/ticket/44580#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#44580: p5-unicode-linebreak: use /usr/bin/ar instead of ${prefix}/bin/ar -----------------------------------+-------------------------------- Reporter: ionic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch tracemode Port: p5-unicode-linebreak | -----------------------------------+-------------------------------- Comment (by ionic@…): Replying to [comment:1 ryandesign@…]:
To prevent failure of the stub port, the `post-configure` block you added needs to be inside the `if {$subport != $name}` block (which for consistency with other perl modules should actually be a `if {${perl5.major} != ""}` block).
You're right, sorry. Replying to [comment:1 ryandesign@…]:
But how does this path to `ar` get into the `Makefile` in the first place? I'd rather patch that, than patch the `Makefile` after configure.
"configure" is a little bit over-euphemized for those perl ports. There's no Makefile template from which it would be generated, that I made sure. But I had no idea what exactly generated it either way. Replying to [comment:2 ryandesign@…]:
Isn't this just ExtUtils::MakeMaker getting the values via Config from /opt/local/lib/perl5/5.20/darwin-thread-multi-2level/Config_heavy.pl? In which case isn't every perl module affected?
Yes, probably! It was the only perl module affected I stumpled upon, but I don't have all of them installed either. A lot of modules don't need compilation or use other means of generating their Makefiles, so that's probably why I haven't seen other modules failing. Fixing the common issue is better though, yes. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/44580#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts