Skip Menu |

This queue is for tickets about the ExtUtils-MakeMaker CPAN distribution.

Report information
The Basics
Id: 39235
Status: resolved
Priority: 0/
Queue: ExtUtils-MakeMaker

People
Owner: Nobody in particular
Requestors: CFAERBER [...] cpan.org
Cc: dolmen [...] cpan.org
ether [...] cpan.org
AdminCc:

Bug Information
Severity: Normal
Broken in: 6.44
Fixed in: (no value)



Subject: Invalid UTF-8 sequence in generated Makefile breaks Solaris 2.10+
If Makefile.PL contains utf8 characters, they are converted to bytes in the Makefile generated by ExtUtils::MakeMaker. This would not be a big deal (except that META.yml will also be in bytes) but this causes several modules to FAIL on i86pc-solaris-64int 2.10+: http://groups.google.com/group/perl.cpan.testers/search?group=perl.cpan.testers&q=i86pc-solaris-64int+invalid-byte-sequence
On Fri Sep 12 17:15:26 2008, CFAERBER wrote: Show quoted text
> > If Makefile.PL contains utf8 characters, they are converted to bytes > in > the Makefile generated by ExtUtils::MakeMaker. > > This would not be a big deal (except that META.yml will also be in > bytes) but this causes several modules to FAIL on i86pc-solaris-64int > 2.10+: > >
http://groups.google.com/group/perl.cpan.testers/search?group=perl.cpan.testers&q=i86pc- Show quoted text
> solaris-64int+invalid-byte-sequence
So what's the solution? I don't know much about byte encoding. MakeMaker doesn't appear to make any special consideration regarding character sets.
Subject: Re: [cpan.org] [rt.cpan.org #39235] Invalid UTF-8 sequence in generated Makefile breaks Solaris 2.10+
Date: Sun, 5 Apr 2009 17:11:46 +0200
To: bug-ExtUtils-MakeMaker [...] rt.cpan.org
From: Claus Färber <cfaerber [...] cfaerber.name>
Am 2009-04-03 um 14:47 schrieb Michael G Schwern via RT: Show quoted text
> So what's the solution? I don't know much about byte encoding. > MakeMaker doesn't appear to make any special consideration regarding > character sets.
Unfortunately, I don't know MakeMaker well enough to have a solution. Further, any solution might introduce further incompabilities on other platforms. The first thing that comes to my mind is: just read and write everything as ':utf8'. However, this means that no distribution will be able to use non-utf8 8bit filenames. (But then, I don't think that 8bit filenames are currently possible with MakeMaker.) Claus
Download smime.p7s
application/pkcs7-signature 3.8k

Message body not shown because it is not plain text.

05 Nis. 2009 Paz., 11:12:10 tarihinde, cfaerber@cfaerber.name yazdı: Show quoted text
> > Am 2009-04-03 um 14:47 schrieb Michael G Schwern via RT:
> > So what's the solution? I don't know much about byte encoding. > > MakeMaker doesn't appear to make any special consideration regarding > > character sets.
> > Unfortunately, I don't know MakeMaker well enough to have a
solution. Show quoted text
> Further, any solution might introduce further incompabilities on
other Show quoted text
> platforms. > > The first thing that comes to my mind is: just read and write > everything as ':utf8'. However, this means that no distribution will > be able to use non-utf8 8bit filenames. (But then, I don't think
that Show quoted text
> 8bit filenames are currently possible with MakeMaker.) > > Claus
That Makefile.PL contains some characters but the file encoding ain't utf8. Don't know if this'll make a difference but you can try to make the file encoding utf8 to test. FYI: Unix.pm itself seems to be in utf8 encoding
Up to date URL for those CPAN test results: https://groups.google.com/forum/#!searchin/perl.cpan.testers/i86pc-solaris-64int$2Binvalid-byte-sequence I claim this is obsolete since it is a local issue on a now-old version of Solaris, and no other open reports on this issue.
I believe this is patched in the latest development release. Solaris make *does* have issues with encoding in EUMM generated Makefiles. I will need to test on Solaris 11 before v7.00 is released.
RT-Send-CC: cfaerber [...] cfaerber.name
7.00 is released.