unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Feng Shu" <tumashu@163.com>
To: Mekeor Melire <mekeor@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: How to replace %output with #$output?
Date: Tue, 22 Mar 2022 16:16:46 +0800	[thread overview]
Message-ID: <87pmmequ4x.fsf@163.com> (raw)
In-Reply-To: <87v8w6xwri.fsf@posteo.de> (Mekeor Melire's message of "Tue, 22 Mar 2022 07:26:38 +0000")

Mekeor Melire <mekeor@posteo.de> writes:

> 2022-03-21 / 21:57 / me@tobias.gr:
>
>> Remove the quote after arguments (replace it with a plain LIST call) and add #~ before (modify-phases ...) to define a gexp.
>>
>> Untested example:
>>
>>     (arguments
>>       (list #:tests? #f ; no tests
>>              #:make-flags (list "CC=gcc")
>>              #:phases
>>              #~(modify-phases %standard-phases
>>                  (delete 'configure)
>>                  (add-after 'unpack 'patch-makefile
>>                    (lambda _
>>                      (substitute* "Makefile"
>>                        (("/usr/local")
>>                         #$output)))))))
>
> With these changes I get this error:
>
> 	Wrong type to apply: "CC=gcc"

What about #~(list "CC=gcc") or '(list "CC=gcc") ?


>
>> So does hard-coding 'gcc' over using (cc-for-target).
>
> Yes, I would also prefer to use cc-for-target. But I wanted to simplify
> my code first. Because in order to use cc-for-target, I have to use
> backticks. If you have a suggestion for how to use both cc-for-target
> and #$output, let me know.
>
>> Very strong opinions on Scheme coding style, that boy.
>
> Please don't assume gender. But yes, you can refer to me with the "he"
> pronoun.

-- 



  parent reply	other threads:[~2022-03-22  8:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 21:31 How to replace %output with #$output? Mekeor Melire
2022-03-21 21:57 ` Tobias Geerinckx-Rice
2022-03-22  7:26   ` Mekeor Melire
2022-03-22  7:59     ` Tobias Geerinckx-Rice
2022-03-22  8:24       ` Mekeor Melire
2022-03-22 16:26         ` Tobias Geerinckx-Rice
2022-03-22  8:16     ` Feng Shu [this message]
2022-03-22  8:51       ` Mekeor Melire

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=87pmmequ4x.fsf@163.com \
    --to=tumashu@163.com \
    --cc=help-guix@gnu.org \
    --cc=mekeor@posteo.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).