#52739: perl5 @5.22.2: build_arch and universal not fully respected ----------------------------------+---------------------- Reporter: MarcusCalhoun-Lopez | Owner: mojca@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5 | ----------------------------------+---------------------- Comment (by MarcusCalhoun-Lopez): Replying to [comment:2 mojca]:
So basically you don't care which of the three patches is used if I understand correctly? Personally, I have no strong feelings about which is best.
I would imagine that a more logical solution than to create a variant manually or to put the code inside the `pre-configure {}` block would be to use {{{ if {[variant_isset universal]} { configure.post_args-append "-Alddlflags=\"[get_canonical_archflags ld]\"" } }}} Does that work properly? I do not believe this would work.[[BR]] At this point in the Portfile, {{{get_canonical_archflags}}} would not work properly without the workarounds provided earlier.[[BR]] Further, {{{build_arch}}} would still not be respected.
Just curious, what's the difference (if any) between `configure`'s `post-args` and `args`? Why not appending it simply to `args`? I am not sure why {{{configure.post_args}}} is used.[[BR]] I do not see the harm, but {{{configure.args}}} seems like a more nature choice.
I would be grateful for a hint how to test building `.bundle` files. Personally, I use the command {{{find ./ -name \*.bundle -exec file {} \;}}} in the destroot directory to check to check.
Do any of those patches address #52290? Since I can not reproduce the exact error, I am not sure.[[BR]] Based on the error, however, it would seem likely that these two bugs are related.
-- Ticket URL: <https://trac.macports.org/ticket/52739#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X