unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 34175@debbugs.gnu.org
Subject: [bug#34175] [PATCH 2/4] gnu: Add sbsigntools.
Date: Wed, 23 Jan 2019 15:09:30 +0100	[thread overview]
Message-ID: <20190123150930.4cc4251d@scratchpost.org> (raw)
In-Reply-To: <87r2d37q4t.fsf@elephly.net>

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

Hi Ricardo,

On Wed, 23 Jan 2019 09:08:18 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:

> Danny Milosavljevic <dannym@scratchpost.org> writes:
> 
> > * gnu/packages/efi.scm (sbsigntools): New variable.  
> […]
> > +         (add-after 'unpack 'setenv
> > +           (lambda _
> > +             (setenv "CC" "gcc")
> > +             #t)))))  
> 
> Could this be done via #:make-flags instead?

No, they call a submake in a shellscript and via "make"
rather than "${MAKE} ${MAKEFLAGS}", so the option will get lost
along the way.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-01-23 14:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23  0:00 [bug#34175] [PATCH 0/4] Add EFI tools Danny Milosavljevic
2019-01-23  0:03 ` [bug#34175] [PATCH 1/4] gnu: Add gnu-efi Danny Milosavljevic
2019-01-23  0:03   ` [bug#34175] [PATCH 2/4] gnu: Add sbsigntools Danny Milosavljevic
2019-01-23  8:08     ` Ricardo Wurmus
2019-01-23 14:09       ` Danny Milosavljevic [this message]
2019-01-23  0:03   ` [bug#34175] [PATCH 3/4] gnu: Add efitools Danny Milosavljevic
2019-01-23  8:09     ` Ricardo Wurmus
2019-01-23  0:03   ` [bug#34175] [PATCH 4/4] gnu: Add efilinux Danny Milosavljevic
2019-01-23  8:12     ` Ricardo Wurmus
2019-01-23  8:05   ` [bug#34175] [PATCH 1/4] gnu: Add gnu-efi Ricardo Wurmus
2019-01-25 17:48     ` Danny Milosavljevic

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=20190123150930.4cc4251d@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=34175@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).