unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>, David Thompson <davet@gnu.org>
Subject: Re: [PATCH] gnu: boost: Allow for customizable build flags.
Date: Tue, 14 Jun 2016 14:53:12 +0300	[thread overview]
Message-ID: <20160614115312.GE10636@debian-netbook> (raw)
In-Reply-To: <CAJ=RwfaSCU3RaDeutVE0yVTjOf=1fZpouH2GXW4quQO9dzi6Ew@mail.gmail.com>

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

On Tue, Jun 14, 2016 at 07:41:31AM -0400, Thompson, David wrote:
> On Tue, Jun 14, 2016 at 6:54 AM, Ricardo Wurmus
> <ricardo.wurmus@mdc-berlin.de> wrote:
> >
> > David Thompson <dthompson2@worcester.edu> writes:
> >
> >> From: David Thompson <davet@gnu.org>
> >>
> >> * gnu/packages/boost.scm (boost)[arguments]: Extract build flags to #:make-flags argument.
> >
> > If I understand correctly, this moves the let-bound “build-flags” to
> > regular make-flags and reuses the default mechanism for passing
> > make-flags, right?
> 
> Yes, exactly.  With it I can easily create things like a statically
> linked variant.
> 
> ~283 packages will need to rebuilt with this change, so maybe
> core-updates would be a good place to put this?  Or would it be
> core-updates-next?  I'm not sure anymore. :)
> 
> Thanks!
> 
> - Dave
> 

I would toss it into core-updates and hope Ludo doesn't notice :). I don't
think it's quite reached building out that far yet so it should be ok.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

  reply	other threads:[~2016-06-14 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 13:08 [PATCH] gnu: boost: Allow for customizable build flags David Thompson
2016-06-14 10:54 ` Ricardo Wurmus
2016-06-14 11:41   ` Thompson, David
2016-06-14 11:53     ` Efraim Flashner [this message]
2016-06-14 12:04     ` Ludovic Courtès
2016-06-14 12:52       ` Thompson, David

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=20160614115312.GE10636@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=davet@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    /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).