From: Vinicius Monego <monego@posteo.net>
To: Brett Gilio <brettg@gnu.org>
Cc: 42807@debbugs.gnu.org
Subject: [bug#42807] [PATCH 1/2] gnu: darktable: Update to 3.2.1.
Date: Mon, 10 Aug 2020 22:12:52 -0300 [thread overview]
Message-ID: <875z9qyoh7.fsf@posteo.net> (raw)
In-Reply-To: <87imdqcc3a.fsf@gnu.org>
Brett Gilio writes:
> 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?
I debugged the build with -K and the problem seems to be this tiny
detail:
`ld: cannot find -lpthreads`
From a quick read online, -lpthreads is Clang syntax. In GCC it's
only
-lpthread or -pthread. That flag is not changed for GCC. Some
other flags are
also using -s termination which GCC doesn't recognize.
I'm not sure who's at fault here. I may be missing something in
the
build steps, but I don't have enough time to investigate this.
The ticket/issue that more closely matches this problem is #5185
and GCC 8+ is
officially supported by Darktable.
next prev parent reply other threads:[~2020-08-11 1:14 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 ` [bug#42807] [PATCH 1/2] gnu: darktable: Update to 3.2.1 Brett Gilio
2020-08-11 1:12 ` Vinicius Monego [this message]
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=875z9qyoh7.fsf@posteo.net \
--to=monego@posteo.net \
--cc=42807@debbugs.gnu.org \
--cc=brettg@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).