Bug 23997 - Perl warnings on new glibc 2.2-12
Perl warnings on new glibc 2.2-12
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-14 12:30 EST by James Brents
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-01-14 13:06:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description James Brents 2001-01-14 12:30:56 EST
I have recently upgraded glibc to 2.2-12 as in the RedHat errata. Since
then, I now have these warnings on invoking perl:
[syonic@Mars syonic]$ perl
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "en_US"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").


Perl worked fine before this, And I only upgraded glibc at the time, so im
sure it has to be related.. It exists on all machines, as all have upgraded
to the new glibc.
Comment 1 Jakub Jelinek 2001-01-14 13:06:20 EST
Cannot reproduce this. The only thing which comes to my mind which
would cause this is that you don't have glibc-common installed.
How have you done the upgrade? If using rpm -F --nodeps, then it
would explain it. The errata described you should do:
rpm -Uvh glibc-2* glibc-common-2*
rpm -Fvh glibc-[dp]* nscd*
Comment 2 James Brents 2001-01-14 13:37:24 EST
Thanks for the advice, my problem was that glibc-common was added, and my perl
script that I made to automate updates never looked for that. After installing
glibc-common the problem is resolved. This is not a bug, but user error. Marking
bug as such.

Note You need to log in before you can comment on or make changes to this bug.