From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: mesa: Add libva input.
Date: Fri, 01 May 2015 00:17:21 +0200 [thread overview]
Message-ID: <87618dfeha.fsf@gnu.org> (raw)
In-Reply-To: <87oam6c9ja.fsf@taylan.uni.cx> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Thu, 30 Apr 2015 10:20:09 +0200")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> Actually, I hit the problem again now; it's during the compilation of
> .scm files.
>
> The problem seems to be that 'inherit' fields of packages are evaluated
> eagerly, so when video.scm directly or indirectly imports gl.scm before
> having bound the libva variable to its value, and the libva-without-mesa
> definition in gl.scm tries to reference libva, it errors.
>
> I can solve this by wrapping the libva-without-mesa definition in a
> delay, and forcing it in the input field of mesa. Is that OK?
Yes, indeed, the solution in such cases is to use a promise or a thunk,
or to have the two definitions in the same file.
Thanks,
Ludo’.
prev parent reply other threads:[~2015-04-30 22:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 13:14 [PATCH] gnu: mesa: Add libva input Taylan Ulrich Bayırlı/Kammer
2015-04-28 14:14 ` Taylan Ulrich Bayırlı/Kammer
2015-04-28 14:20 ` 宋文武
2015-04-28 20:21 ` Taylan Ulrich Bayırlı/Kammer
2015-04-29 8:59 ` 宋文武
2015-04-29 21:12 ` Andreas Enge
2015-04-29 21:52 ` Taylan Ulrich Bayırlı/Kammer
2015-04-30 7:29 ` Andreas Enge
2015-04-30 7:31 ` Andreas Enge
2015-04-30 7:52 ` Taylan Ulrich Bayırlı/Kammer
2015-04-30 13:26 ` Taylan Ulrich Bayırlı/Kammer
2015-04-30 22:18 ` Ludovic Courtès
2015-04-30 7:49 ` Taylan Ulrich Bayırlı/Kammer
2015-04-30 8:20 ` Taylan Ulrich Bayırlı/Kammer
2015-04-30 22:17 ` Ludovic Courtès [this message]
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=87618dfeha.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.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.
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.