all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Mortimer Cladwell <mbcladwell@gmail.com>,
	help-guix <help-guix@gnu.org>,  Josselin Poiret <dev@jpoiret.xyz>
Subject: Re: guile-hoot install reproducibly crashes at 41% build
Date: Sun, 29 Oct 2023 08:46:10 -0400	[thread overview]
Message-ID: <CAJ=RwfYCZP_zY-3hj7Ek4Mjfom_s0OSw4oWwF5NSA0KhYOnTqg@mail.gmail.com> (raw)
In-Reply-To: <87a5s2cdik.fsf@lease-up.com>

Hi Felix,

On Sat, Oct 28, 2023 at 11:29 PM Felix Lechner
<felix.lechner@lease-up.com> wrote:
>
> Hi Dave,
>
> On Fri, Oct 27 2023, Thompson, David wrote:
>
> > Or remove v8 from the package inputs at the bottom of the guix.scm
> > file.  We only use V8 for the test suite.
>
> I know it's impolite to quote oneself, but please grant me a brief plug
> to drop build-time tests everywhere. [1]
>
> Package declarations would list (test-inputs ...) separately. For many
> packages, it has the potential to reduce the prerequisites actually
> needed to build them.

That's good to know! Thanks for the tip. I'm behind the times on that
detail. In this particular case, though, Mortimer was trying to build
our development environment, in which we definitely want V8.  The
package in Guix core doesn't use it. :)

- Dave


  reply	other threads:[~2023-10-29 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 11:00 guile-hoot install reproducibly crashes at 41% build Mortimer Cladwell
2023-10-27 13:22 ` Thompson, David
2023-10-27 19:27   ` Mortimer Cladwell
2023-10-27 20:34     ` Thompson, David
2023-10-28  5:49       ` Mortimer Cladwell
2023-10-29  3:29       ` Felix Lechner via
2023-10-29 12:46         ` Thompson, David [this message]
2023-10-30 15:40           ` Felix Lechner via

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=RwfYCZP_zY-3hj7Ek4Mjfom_s0OSw4oWwF5NSA0KhYOnTqg@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=dev@jpoiret.xyz \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    --cc=mbcladwell@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.