unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Helmut Grohne <helmut@subdivi.de>
Cc: 1064998@bugs.debian.org, guile-devel@gnu.org
Subject: Re: Bug#1064998: guile-lib: broken package when cross building
Date: Fri, 01 Mar 2024 17:01:30 -0800	[thread overview]
Message-ID: <87o7bxbg5x.fsf@contorta> (raw)
In-Reply-To: <20240228132207.GA3451424@subdivi.de>

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

Forwarding this upstream, originally submitted in the Debian bug
tracking system at:

  https://bugs.debian.org/1064998

On 2024-02-28, Helmut Grohne wrote:
> guile-lib actually does cross build, but we still track it as cross
> build failure, because the resulting package contains a build
> architecture multiarch tuple and that trips post-build sanity checks.
>
> The root cause of the failure lies in the way the ccache directory is
> determined. There are actually several ways this is being done during
> configure - some of which work correctly - and ultimately, the last
> attempt using GUILE_SITE_CCACHE_DIR gets to set the value wrongly.
> Surprisingly, there already is a more complete and working
> implementation GUILE_SITE_DIR and simply reusing that makes it compute
> the ccache directory correctly. Is the attached patch acceptable?
>
> Helmut
> --- guile-lib-0.2.7.orig/m4/guile-ext.m4
> +++ guile-lib-0.2.7/m4/guile-ext.m4
> @@ -63,12 +63,4 @@
>  # The variable is marked for substitution, as by @code{AC_SUBST}.
>  #
>  AC_DEFUN([GUILE_SITE_CCACHE_DIR],
> - [AC_REQUIRE([GUILE_PROGS])
> -  AC_MSG_CHECKING(for Guile site ccache directory)
> -  GUILE_SITE_CCACHE=`$GUILE -c "(display (%site-ccache-dir))"`
> -  if test "$GUILE_SITE_CCACHE" = ""; then
> -     AC_MSG_FAILURE(site ccache dir not found)
> -  fi
> -  AC_MSG_RESULT($GUILE_SITE_CCACHE)
> -  AC_SUBST(GUILE_SITE_CCACHE)
> - ])
> + [AC_REQUIRE([GUILE_SITE_DIR])])

Would the guile-lib developers consider merging this? Are there any
use-cases where this is inappropriate?

Thanks!

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

       reply	other threads:[~2024-03-02  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228132207.GA3451424@subdivi.de>
2024-03-02  1:01 ` Vagrant Cascadian [this message]
2024-03-03  3:29   ` Bug#1064998: guile-lib: broken package when cross building Maxim Cournoyer
2024-03-03 23:49   ` David Pirotte

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87o7bxbg5x.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=1064998@bugs.debian.org \
    --cc=guile-devel@gnu.org \
    --cc=helmut@subdivi.de \
    /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.
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).