all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: 55449@debbugs.gnu.org
Cc: Tobias Geerinckx-Rice <me@tobias.gr>
Subject: bug#55449: recutils cross-compilation "fix" breaks bash builtins
Date: Mon, 16 May 2022 14:52:00 +0200	[thread overview]
Message-ID: <9841253361ff5e3caccd4702518c70bdba8ac622.camel@ist.tugraz.at> (raw)

Hi Guix,

The fix in commit 20fbd870938e239c038d8524a56729f123f19f80, which lets
recutils cross-compile unfortunately omits support for the bash
builtins in all build modes, as recutils can't actually detect bash
headers there.

Unfortunately, recutils' configure.ac silently swallows this error in
the following check.
  AM_CONDITIONAL([BASH_BUILTINS],
                 [test "x$bash_headers_available" = "xyes" && 
                  test "x$bash_builtins_enabled" = "xyes"])
I only noticed, because I symlink the builtins to lib/bash, where
they're actually needed, which causes runpath validation to fail
because the symlink points to a file that doesn't exist.  I fixed this
locally, but still wanted y'all to know.

Is there a way we can support bash headers in cross-compilation
contexts?  I don't think having bash:include as a native input is even
helpful here, is it?  WDYT?




             reply	other threads:[~2022-05-16 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 12:52 Liliana Marie Prikler [this message]
2022-05-16 13:37 ` bug#55449: recutils cross-compilation "fix" breaks bash builtins Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-05-16 15:15 ` Maxime Devos
2022-06-04  8:30 ` bug#55449: [PATCH] gnu: recutils: Use correct bash headers Liliana Marie Prikler
2023-06-18  7:39   ` Liliana Marie Prikler

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=9841253361ff5e3caccd4702518c70bdba8ac622.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=55449@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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.