Re: Custom Glibc collation version strings under LOCPATH

2025-06-04 Thread Joe Conway
On 6/4/25 19:35, Thomas Munro wrote: On Thu, Jun 5, 2025 at 3:44 AM Joe Conway wrote: If you go from anything pre-glibc-2.21 to post-glibc-2.21 I think you will find that even with the same data files you get a different sort. The same patch that caused the performance regression [1] (still pre

Re: Custom Glibc collation version strings under LOCPATH

2025-06-04 Thread Thomas Munro
On Thu, Jun 5, 2025 at 3:44 AM Joe Conway wrote: > On 6/4/25 09:52, Joe Conway wrote: > > On 6/4/25 00:03, Thomas Munro wrote: > >> I'm interested in hearing about other concrete > >> examples of the locale-recompilation technique failing to be perfect, > >> and getting to the bottom of them; I ha

Re: Custom Glibc collation version strings under LOCPATH

2025-06-04 Thread Joe Conway
On 6/4/25 09:52, Joe Conway wrote: On 6/4/25 00:03, Thomas Munro wrote: One way to move to a newer glibc-based Linux distribution but keep the locales working the same* without keeping the associated zombie C code alive is to find the source system's collation definition source files, compile th

Re: Custom Glibc collation version strings under LOCPATH

2025-06-04 Thread Joe Conway
On 6/4/25 00:03, Thomas Munro wrote: One way to move to a newer glibc-based Linux distribution but keep the locales working the same* without keeping the associated zombie C code alive is to find the source system's collation definition source files, compile them with the localedef on the target

Re: Custom Glibc collation version strings under LOCPATH

2025-06-04 Thread Thomas Munro
On Wed, Jun 4, 2025 at 9:17 PM Peter Eisentraut wrote: > I wonder why you want to capture LOCPATH early in main.c. It seems > sufficient to look it up when needed? Right, it is setenv() that we're trying to avoid. Updated. From 5482ccf5a61061411f9a996da84f14471b791d83 Mon Sep 17 00:00:00 2001 F

Re: Custom Glibc collation version strings under LOCPATH

2025-06-04 Thread Peter Eisentraut
On 04.06.25 06:03, Thomas Munro wrote: One way to move to a newer glibc-based Linux distribution but keep the locales working the same* without keeping the associated zombie C code alive is to find the source system's collation definition source files, compile them with the localedef on the targe

Custom Glibc collation version strings under LOCPATH

2025-06-03 Thread Thomas Munro
Hi, One way to move to a newer glibc-based Linux distribution but keep the locales working the same* without keeping the associated zombie C code alive is to find the source system's collation definition source files, compile them with the localedef on the target system and point to the top-level