all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Hilton Chain <hako@ultrarare.space>, 67156-done@debbugs.gnu.org
Subject: bug#67156: Build insight-toolkit.x86_64-linux.skylake on master is broken.
Date: Tue, 14 Nov 2023 20:55:37 -0500	[thread overview]
Message-ID: <87edgrdbl2.fsf@gmail.com> (raw)
In-Reply-To: <ZVMcwnW0V7tDs9B_@3900XT> (Efraim Flashner's message of "Tue, 14 Nov 2023 09:07:46 +0200")

Hi,

Efraim Flashner <efraim@flashner.co.il> writes:

> On Mon, Nov 13, 2023 at 11:21:53PM -0500, Maxim Cournoyer wrote:
>> Hello!
>> 
>> Apparently, the recently pushed LLVM/Clang update broke this package,
>> according to the Cuirass notifications:
>> 
>> cuirass@gnu.org (Cuirass) writes:
>> 
>> > <p>The build <b>insight-toolkit.x86_64-linux.skylake</b> for specification <b>master</b> is
>> > broken. You can find the detailed information about this build <a
>> > href="https://ci.guix.gnu.org/build/2602507/details">here</a>.</p>
>> >
>> > https://ci.guix.gnu.org/build/2602507/details
>> 
>> I haven't investigated it, but this appears to be where it fails:

[...]

> It looks like insight-toolkit-4.12 was failing for a while and now the
> optimized versions were starting to fail too.  I added a configure-flag
> to insight-toolkit-4.12 to specifically used C++14 and then the build
> succeeded.

Excellent, thank you!

-- 
Thanks,
Maxim




      reply	other threads:[~2023-11-15  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1633@guix-ci.nnrss>
2023-11-14  4:21 ` bug#67156: Build insight-toolkit.x86_64-linux.skylake on master is broken Maxim Cournoyer
2023-11-14  7:07   ` Efraim Flashner
2023-11-15  1:55     ` Maxim Cournoyer [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=87edgrdbl2.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=67156-done@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=hako@ultrarare.space \
    /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.