PERL errors?

PERL errors?

Post by Badlan » Sat, 03 Jul 1999 04:00:00



Any time I run perl, or it's called, I get these errors.

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LC_ALL = (unset),
        LANG = "us"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

Anyone know where I should look to set/fix ths stuff for FreeBSD
3.2-STABLE on x86?

Thanks...
Rob

 
 
 

PERL errors?

Post by Anton Berezi » Sat, 03 Jul 1999 04:00:00



> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>         LC_ALL = (unset),
>         LANG = "us"
>     are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> Anyone know where I should look to set/fix ths stuff for FreeBSD
> 3.2-STABLE on x86?

Set LANG to be en_US.ISO_8859-1 instead of us, whenever you have it set
(e.g. .shrc, .cshrc, /etc/profile).  Or unset it altogether.

--

The Protein Laboratory, University of Copenhagen

 
 
 

PERL errors?

Post by Chad O Hulber » Sun, 04 Jul 1999 04:00:00



> Any time I run perl, or it's called, I get these errors.

> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>         LC_ALL = (unset),
>         LANG = "us"
>     are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").

> Anyone know where I should look to set/fix ths stuff for FreeBSD
> 3.2-STABLE on x86?

    I found this problem most common after installtion of StarOffice.
StarOffice installs an initialization script in one's home directory and
invokes it from the shell's configuration scripts.  Either comment out
the LANG = part or make sure all variables are set to sane and desired
values.

--
Chad O Hulbert

"Speed is subsittute fo accurancy."

 
 
 

1. Redirect Apache ErrorDocument 500 to display perl errors/warnings?

Is there any way at all to make apache display the errors of a perl
script (cgi) instead of that disgusting Error 500 screen? I know it
would have something to do with the ErrorDocument 500 of the httpd.conf
for apache. I even tried seting it ot a test script but here seems to no
way to even determin the file the caused the error from that script. I
know I could manually check the error logs, but I would like ot see the
errors on the screens. Warnings would be helpful too. Theres gotta be a
way. I was this done once on a server running apache on some business
site a friend of mine used to work on a couple years back. Hes since
moved on.

Thank a lot for any help!

2. modemAPI.h ??

3. Perl Error Solaris 9 SPARC (Orca build)

4. Problem: HD not recognized

5. installing GIMP results in fatal PERL error

6. Control connection timeouts on FTP (coyote linux)

7. premail/perl error messages

8. kernel 2.4.6 upgrade and lost "Power off on Shutdown" option

9. installing GIMP results in Fatal PERL Error

10. Redirect Apache ErrorDocument 500 to display perl errors/warnings?

11. perl error by update with apt-get on debian

12. Perl developer/Unix SA turns PM and selling Library of unix/linux/perl books

13. /usr/local/bin/perl ->/usr/bin/perl