#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by dluke@…): Can you try the standard fix? (i.e.. add 'build.env LANG=C' to the Portfile and see if it fixes it)? -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by dluke@…): Replying to [comment:2 mf2k@…]:

I just tried it and the same error occurs.

oh, because this sed is being run in the configure phase, not the build phase. Try 'configure.env-append LANG=C' instead. -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by dluke@…): can you attach the main.log from the new failure? -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by dluke@…): Looks like setting configure.env doesn't change the env in post-configure blocks (which is where the perl5 portgroup does a couple of reinplaces). This also a problem for p5-shell-parser (#37066). We probably need to (at least temporarily) be setting LANG=C or LC_CTYPE=C in the perl5 portgroup. -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: p5-spiffy | ------------------------+--------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: One fix would be to change the perl5 portgroup's post-configure `reinplace` to use `-locale C`. [changeset:123712 When last I encountered this] with a different module I instead patched its Makefile.PL. There is a real underlying bug somewhere that should be fixed—a Makefile.PL that starts out as UTF-8 should not result in a Makefile that is not UTF-8—I just couldn't find where in ExtUtils::MakeMaker the bug was, then realized it could be a bug in any of its dependencies, and also the bug affects the versions of these modules that ship with perl5.16 and perl5.18 (but not perl5.14 or earlier nor perl5.20). -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by dluke@…): Replying to [comment:10 ryandesign@…]:

Replying to [comment:7 dluke@…]:

...

This also a problem for p5-shell-parser (#37066).

#37066 has a different cause: that project's Makefile.PL isn't UTF-8 (it's ISO8859-1).

And I've now realized that while p5-spiffy's Makefile.PL is ASCII, it contains escape codes representing ISO8859-1 characters, which get turned into real ISO8859-1 characters in the generated Makefile.

yep. I think there may be some fixes for this sort of thing in ExtUtils::MakeMaker 7.00 (which isn't out yet). Easiest way to work around this would be to make a change to the perl5 portgroup (for now). -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p5-spiffy | ------------------------+--------------------- Changes (by mojca@…): * version: 2.3.1 => Old description:

I'm suddenly seeing the following error when trying to build p5.16-spiffy with all the new perl updates.

{{{ ---> Configuring p5.16-spiffy sed: RE error: illegal byte sequence }}}

New description: I'm suddenly seeing the following error when trying to build p5.16-spiffy with all the new perl updates. {{{ ---> Configuring p5.16-spiffy sed: RE error: illegal byte sequence }}} See also #43145. -- -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:13> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by dluke@…): The META.yml file that gets generated from Makefile.PL is supposed to allow utf8 characters, so ideally we wouldn't have to munge the author's name in order to get things to build. I haven't tested newer ExtUtils::MakeMaker, but they've made some utf8 handling changes that possibly fix this (and/or allow it to be fixed more appropriately). -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:15> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by mojca@…): Oh ... I always thought that `döt Net` was just an obfuscation method to confuse spammers and that it meant the `.net` part in his email address. I didn't notice until now that it's actually part of his official name. -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:17> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by mojca@…): If p5-extutils-makemaker is some semi-universal dependency – wouldn't it make sense to add it to the PortGroup? -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:19> MacPorts <http://www.macports.org/> Ports system for OS X

#44630: p5.16-spiffy configure error - sed: RE error: illegal byte sequence ------------------------+--------------------- Reporter: mf2k@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p5-spiffy | ------------------------+--------------------- Comment (by mf2k@…): Thanks everyone for figuring out and fixing this so fast! -- Ticket URL: <https://trac.macports.org/ticket/44630#comment:21> MacPorts <http://www.macports.org/> Ports system for OS X