From: Tomas Volf <~@wolfsden.cz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 67044@debbugs.gnu.org, 67686@debbugs.gnu.org
Subject: [bug#67686] bug#67044: C.utf8 locale cannot be built
Date: Thu, 7 Dec 2023 23:09:40 +0100 [thread overview]
Message-ID: <ZXJCpL0u0UoEb8YA@ws> (raw)
In-Reply-To: <87zfyme29z.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]
Hi :)
On 2023-12-07 11:27:04 +0100, Ludovic Courtès wrote:
> [..]
>
> I decided to give it a go:
>
> https://issues.guix.gnu.org/67686
>
> Please do chime in and let me know what you think!
Thanks to the detailed cover letter, now I understand the benefit, so I agree it
would make sense. I looked over the implementation, and it looks fine to me (I
am not sure if I am qualified to do the review though :) ).
I just have few notes:
1.
> (glibc-2.35)[arguments]: Delete ‘install-utf8-c-locale’ phase.
I do think 2.35 should install the locale as well. That would require to change
(invoke (string-append bin "/localedef")
"--no-archive" "--prefix" locale
"-i" "C" "-f" "UTF-8"
(string-append locale "/C.UTF-8")))))
into
(invoke (string-append bin "/localedef")
"-c" "--no-archive" "--prefix" locale
"-i" "C" "-f" "UTF-8"
(string-append locale "/C.UTF-8")))))
however I think that is fine. I am using locale built like that and it works
well. What is more, from the discussion under the other issue[0], that is
exactly what is done during normal glibc build:
> It turns out we ignore errors during the glibc build (--quiet -c).
After that the drop of 'install-utf8-c-locale can be moved into some other
version < 2.35.
2.
I still believe it makes sense to add the -c also into the locale builder,
because my understanding is that this change will not allow using (locale
"C.utf8") in the operating-system definition (since that would still try to
build it, and fail).
If you are not opposed to the idea, I can send a patch if you would prefer not
to do it yourself.
3.
> I suspect libc builds an additional ‘localedef’ for the build machine but I’m
> not sure where it is, hmm…
I looked around a bit, and I am not sure that is true. There seems to be only
./locale/localedef created. However, there is localedef inside gcc-toolchain's
bin directory, and, of course, in the build glibc. I am not sure what are the
version requirements here, but I would expect at least the one provided by glibc
to be usable.
Have a nice day,
Tomas
0: https://sourceware.org/bugzilla/show_bug.cgi?id=28845
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-07 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 14:42 bug#67044: C.utf8 locale cannot be built Tomas Volf
2023-11-27 22:02 ` Ludovic Courtès
2023-11-28 1:22 ` Tomas Volf
2023-12-07 10:27 ` Ludovic Courtès
2023-12-07 22:09 ` Tomas Volf [this message]
2023-12-09 14:46 ` bug#67044: [bug#67686] " Ludovic Courtès
2023-12-10 0:57 ` Tomas Volf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZXJCpL0u0UoEb8YA@ws \
--to=~@wolfsden.cz \
--cc=67044@debbugs.gnu.org \
--cc=67686@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.