unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: 67044@debbugs.gnu.org
Subject: bug#67044: C.utf8 locale cannot be built
Date: Fri, 10 Nov 2023 15:42:59 +0100	[thread overview]
Message-ID: <ZU5Bcz1vIcoH1COM@ws> (raw)

[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]

Hi,

when trying to build a system with C.utf8 locale, I end up with the following
error:

    building /gnu/store/v6jma6kmwywr509n4y0vypchnh4y5s3m-locale-2.35.drv...
    building locale 'C.utf8'...
    [error] LC_MONETARY: value for field `mon_decimal_point' must not be an empty string
    [error] no output file produced because errors were issued
    Backtrace:
               2 (primitive-load "/gnu/store/ccv2qfrqxk166ysg6anrzj1kz4h?")
    In ice-9/boot-9.scm:
       285:13  1 (for-each #<procedure 7fffeef5c540 at ice-9/eval.scm:3?> ?)
    In guix/build/utils.scm:
        812:6  0 (invoke "localedef" "--no-archive" "--prefix" "/gnu/st?" ?)
    
    guix/build/utils.scm:812:6: In procedure invoke:
    ERROR:
      1. &invoke-error:
          program: "localedef"
          arguments: ("--no-archive" "--prefix" "/gnu/store/08rlginv27b9v1ba4n94plp7lmxjihja-locale-2.35/2.35" "-i" "C" "-f" "UTF-8" "/gnu/store/08rlginv27b9v1ba4n94plp7lmxjihja-locale-2.35/2.35/C.utf8")
          exit-status: 4
          term-signal: #f
          stop-signal: #f
    builder for `/gnu/store/v6jma6kmwywr509n4y0vypchnh4y5s3m-locale-2.35.drv' failed with exit code 1
    build of /gnu/store/v6jma6kmwywr509n4y0vypchnh4y5s3m-locale-2.35.drv failed
    View build log at '/var/log/guix/drvs/v6/jma6kmwywr509n4y0vypchnh4y5s3m-locale-2.35.drv.gz'.
    cannot build derivation `/gnu/store/g47g7zqs5la6qpfmn6q1zgbhp291l1ha-system.drv': 1 dependencies couldn't be built
    guix system: error: build of `/gnu/store/g47g7zqs5la6qpfmn6q1zgbhp291l1ha-system.drv' failed

This seems to be a known problem in 2.35,
https://sourceware.org/bugzilla/show_bug.cgi?id=28861 .  On the page there is
also a workaround, and that is to compile with the locales with -c.

So that would be one solution until we update to 2.36 or higher.  I do not see a
way to override this (add the -c) from the operating-system definition.

Tomas Volf

-- 
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 --]

             reply	other threads:[~2023-11-11 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 14:42 Tomas Volf [this message]
2023-11-27 22:02 ` bug#67044: C.utf8 locale cannot be built Ludovic Courtès
2023-11-28  1:22   ` Tomas Volf
2023-12-07 10:27     ` Ludovic Courtès
     [not found]       ` <ZXJCpL0u0UoEb8YA@ws>
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZU5Bcz1vIcoH1COM@ws \
    --to=~@wolfsden.cz \
    --cc=67044@debbugs.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).