unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Philip McGrath" <philip@philipmcgrath.com>
Cc: help-guix@gnu.org
Subject: Re: Debugging cross-compilation dependencies
Date: Tue, 09 Aug 2022 22:16:13 +0200	[thread overview]
Message-ID: <87wnbh41gy.fsf@gnu.org> (raw)
In-Reply-To: <5edb2b76-2df5-42d4-84ec-f844a8bbf985@www.fastmail.com> (Philip McGrath's message of "Fri, 29 Jul 2022 01:36:31 -0400")

Hello!

"Philip McGrath" <philip@philipmcgrath.com> skribis:

> Much to my surprise, I discovered I can avoid the problem by changing code for #:make-flags like this:
>
> ```
> #~(string-append "ZUO="
>                                   #$(this-package-native-input "zuo")
>                                   "/bin/zuo"))
> ```

You should prolly use ‘ungexp-native’ (aka. #+) instead of ‘ungexp’ (#$).

  #~(string-append … #+(this-package-native-input "zuo") …)

HTH!

Ludo’.


  reply	other threads:[~2022-08-09 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 11:30 Debugging cross-compilation dependencies Philip McGrath
2022-07-29  5:36 ` Philip McGrath
2022-08-09 20:16   ` Ludovic Courtès [this message]
2022-08-09 20:16   ` Ludovic Courtès

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=87wnbh41gy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=philip@philipmcgrath.com \
    /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).