all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
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 07:41:31 -0400	[thread overview]
Message-ID: <CAJ=RwfaSCU3RaDeutVE0yVTjOf=1fZpouH2GXW4quQO9dzi6Ew@mail.gmail.com> (raw)
In-Reply-To: <idjbn34xcq3.fsf@bimsb-sys02.mdc-berlin.net>

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

  reply	other threads:[~2016-06-14 11:41 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 [this message]
2016-06-14 11:53     ` Efraim Flashner
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ=RwfaSCU3RaDeutVE0yVTjOf=1fZpouH2GXW4quQO9dzi6Ew@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=davet@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.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. 
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.