[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: lib/53722: Static binaries don't support locales that are implemented using shared objects
The following reply was made to PR lib/53722; it has been noted by GNATS.
From: christos%zoulas.com@localhost (Christos Zoulas)
To: Robert Elz <kre%munnari.OZ.AU@localhost>
Cc: Martin Husemann <martin%duskware.de@localhost>, gnats-bugs%NetBSD.org@localhost,
Subject: Re: lib/53722: Static binaries don't support locales that are implemented using shared objects
Date: Sun, 11 Nov 2018 20:39:03 -0500
On Nov 12, 8:00am, kre%munnari.OZ.AU@localhost (Robert Elz) wrote:
-- Subject: Re: lib/53722: Static binaries don't support locales that are imp
| Why are we using dynamic linking for locales? Sure, that should work, but
| a local is just a bunch of data, is it not? Wouldn't just malloc()ing a space
| to stick it, and doing a simple read() work? Or at worst, reading a header
| to find out how many structs are needed, then malloc() and read() the rest.
Nope, there is code too; see /usr/src/lib/libc/citrus/
| What does using dynamic linking really achieve (aside from that the support
| is there already, and needed for other stuff.)
Conserves some memory (there are many locales)... But really not enough to
make it worth the hassle these days. It is there to allow custom locales
and to provide code and data isolation for them.
It is a good GSoC project to make static linking of locales to work. I've
added it to the list of projects.
Main Index |
Thread Index |