Re: Re: Module compilation hell

I was having similar problems with RH9 until I discovered the magic file /etc/sysconfig/i18n. By default it sets LANG to "en_US.UTF-8", which triggers many, many unicode errors and warnings, at least with the version of perl that shipped with RH9. Get rid of the UTF-8 bit, and things may be much happier. Mine is now:

LANG="en_US"
SUPPORTED="en_US:en_US.UTF-8:en"
SYSFONT="latarcyrheb-sun16"
[download]

For temporary joy, just change $LANG in your current environment to en_US if it's set to en_US.UTF-8.

I used to feel the same way about CPAN, but either it's gotten much better, or I have a bigger pile of hammers to apply to things when they break. These days, I'm well below the threshold of frustration.

In your particular case -- are you sure you've exhausted the standard set of Fedora RPMs? I don't have a Fedora handy, but in my pile of standard RH9 RPMs, I have both perl-DBD-MySQL and mod_perl RPMs.

Comment on Re: Re: Module compilation hell Download Code

Replies are listed 'Best First'.
Re: Re: Re: Module compilation hell by mpolo (Chaplain) on Mar 31, 2004 at 09:03 UTC
The module compiling problems due to Unicode implementation in RH9 were pretty much solved in FC1. That is, I have not had to mess with $LANG under FC1 to install modules, while this was necessary under RH9. There are still issues when reading SMB file systems, but Perl modules compile fine (as the poster already noted, his problem was in passing the tests, and the documentation actually provides a solution to that problem, which is due to file permissions). As to solving the problem in the module's test suite, is there any reason not to move the files that have to be modified/written to /tmp, so that "nobody" can do this? Or have the test script change the permissions on the files? I suppose there's a portability issue here, since Windows essentially has no permissions, and the temp directory can be in various places on various systems. It seems silly to have a test suite that is doomed to failure on all 'nix systems and then put a "how to fix it" note in the docs...	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Module compilation hell
by mpolo (Chaplain) on Mar 31, 2004 at 09:03 UTC

The module compiling problems due to Unicode implementation in RH9 were pretty much solved in FC1. That is, I have not had to mess with $LANG under FC1 to install modules, while this was necessary under RH9. There are still issues when reading SMB file systems, but Perl modules compile fine (as the poster already noted, his problem was in passing the tests, and the documentation actually provides a solution to that problem, which is due to file permissions).

As to solving the problem in the module's test suite, is there any reason not to move the files that have to be modified/written to /tmp, so that "nobody" can do this? Or have the test script change the permissions on the files? I suppose there's a portability issue here, since Windows essentially has no permissions, and the temp directory can be in various places on various systems. It seems silly to have a test suite that is doomed to failure on all 'nix systems and then put a "how to fix it" note in the docs...

[reply]