unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@gnu.org>
To: Vinicius Monego <monego@posteo.net>
Cc: 42807@debbugs.gnu.org
Subject: [bug#42807] [PATCH 1/2] gnu: darktable: Update to 3.2.1.
Date: Mon, 10 Aug 2020 18:31:21 -0500	[thread overview]
Message-ID: <87imdqcc3a.fsf@gnu.org> (raw)
In-Reply-To: <20200810232325.61515-1-monego@posteo.net> (Vinicius Monego's message of "Mon, 10 Aug 2020 20:23:25 -0300")

Vinicius Monego <monego@posteo.net> writes:

--8<---------------cut here---------------start------------->8---
> +             ;; Build fails with every version of GCC.
>               (setenv "CC" "clang") (setenv "CXX" "clang++")
--8<---------------cut here---------------end--------------->8---

Hey, is this issue with GCC reported upstream? I'm not opposed to
compiling against clang<++>, especially since it is already in the
closure for the package. But if there is a reported issue for this, the
ticket number should be referenced in the comment ideally. Otherwise,
could you report it?

Thanks!

Brett Gilio




  parent reply	other threads:[~2020-08-10 23:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 23:23 [bug#42807] [PATCH 1/2] gnu: darktable: Update to 3.2.1 Vinicius Monego
2020-08-10 23:25 ` [bug#42807] [PATCH 2/2] gnu: darktable: Add dependency on libavif, ocl-icd Vinicius Monego
2020-08-10 23:31 ` Brett Gilio [this message]
2020-08-11  1:12   ` [bug#42807] [PATCH 1/2] gnu: darktable: Update to 3.2.1 Vinicius Monego
2020-08-12  1:01     ` Vinicius Monego
2020-09-04  9:06       ` Ludovic Courtès
2020-08-13 14:59 ` [bug#42807] [PATCH v2 " Vinicius Monego
2020-08-13 14:59   ` [bug#42807] [PATCH v2 2/2] gnu: darktable: Add dependency on libavif, ocl-icd Vinicius Monego
2020-09-04  9:06   ` bug#42807: [PATCH v2 1/2] gnu: darktable: Update to 3.2.1 Ludovic Courtès
2020-09-05 18:17     ` [bug#42807] " Vinicius Monego

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=87imdqcc3a.fsf@gnu.org \
    --to=brettg@gnu.org \
    --cc=42807@debbugs.gnu.org \
    --cc=monego@posteo.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).