[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: locale errors



I wonder whether it's difficult to fix that. If I recall correctly most
of the locale code in libc5 is from glibc anyway.

Michael

--
Dr. Michael Meskes, Projekt-Manager    | topsystem Systemhaus GmbH
meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
meskes@debian.org                      | 52146 Wuerselen
Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10

>-----Original Message-----
>From:	Erv Walter [SMTP:edwalter@iname.com]
>Sent:	Wednesday, June 18, 1997 1:55 AM
>To:	Ben Pfaff
>Cc:	Die Adresse des Empfängers ist unbekannt.
>Subject:	Re: locale errors
>
>
>Damn, pinepgp is screwing up auto signatures.  Sorry.
>
>=======================================================
>
>> On 17 Jun 1997, Ben Pfaff wrote:
>> 
>> > kai@khms.westfalen.de (Kai Henningsen) writes:
>> > > meskes@topsystem.de (Michael Meskes)  wrote on 17.06.97 in
>><c=DE%a=_%p=topsystem%l=EINSTEIN-970617110158Z-203@einstein.topsystem.de>:
>> > > 
>> > > > No! You cannot use libc5 compiled perl with glibc locales! Wait for a
>> > > > libc6 version of perl and everything should be fine again.
>> > > 
>> > > This is, of course, a problem nearly as serious as that about utmp.
>> > 
>> > Not really.  This is an issue only with `unstable' (as far as I can
>> > tell from the discussion), and `unstable' means exactly
>> > that--everything might not work properly.
>> 
>
>That is true, but like the utmp problem, it's not going to go away
>by itself.  If we want to be able to have a system where both libc5 and
>libc6 programs can coexist, we run into a problem with utmp.  The 2
>libraries manipulate utmp differently, so if you run both libc5 and
>libc6 binaries that try to manipulate utmp, it gets corrupted.
> 
>Similarly, if we install libc5 locale files, libc6 programs can't use
>them.  If we install libc6 locale files, libc5 programs can't use
>them.  
> 
>These are not trivial problems to fix, and they'll still be around in
>3 months if nothing is done in the mean time.  I am confident that
>someone will come up with an elligant solution after the 1.3 release
>settles down.
> 
>Erv
>
>--
>	  PGP Public Key: finger walter@fozzie.chem.wisc.edu
>  PGP Fingerprint: A5 AB 25 7D 7A FD 4D FE  BE 21 47 60 0C DC 67 9E
>                                 ____
> ----==-- _                     / /  \         
> ---==---(_)__  __ ____  __    / / /\ \	              - edwalter@iname.com
> --==---/ / _ \/ // /\ \/ /   / /_/\ \ \            - walter@chem.wisc.edu   
> -=====/_/_//_/\_,_/ /_/\_\  /______\ \ \     - edwalter@students.wisc.edu
>                             \_________\/  
>
>
>--
>TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
>debian-devel-request@lists.debian.org . 
>Trouble?  e-mail to templin@bucknell.edu .
>


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble?  e-mail to templin@bucknell.edu .


Reply to: