From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [TRACKING] gcc 12 build failures
Date: Wed, 19 Oct 2022 09:41:41 +0200 [thread overview]
Message-ID: <20221019074141.Zypv71EdPdlLOgXGnK_gtmfKwWfhq54wOGY0Mfm1DU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39809@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1283567922
Comment:
The ffmpeg build failure isn't related to gcc 12 and has already been resolved: https://github.com/void-linux/void-packages/issues/39648
Here is the libreoffice build failure on musl:
```
configure:23848: checking for CLucene/analysis/cjk/CJKAnalyzer.h
configure:23848: /usr/bin/ccache g++ -c -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -DGLM_ENABLE_EXPERIMENTAL -DU_USING_ICU_NAMESPACE=1 -DGLM_ENABLE_EXPERIMENTAL -DU_USING_ICU_NAMESPACE=1 -fdebug-prefix-map=/builddir/libreoffice-7.3.3.2=. conftest.cpp >&5
In file included from /usr/include/CLucene/debug/lucenebase.h:10,
from /usr/include/CLucene/SharedHeader.h:201,
from /usr/include/CLucene/StdHeader.h:20,
from /usr/include/CLucene.h:11,
from conftest.cpp:90:
/usr/include/CLucene/LuceneThreads.h:72:24: error: 'pthread_t' does not name a type
72 | static _LUCENE_THREADID_TYPE _GetCurrentThreadId();
| ^~~~~~~~~~~~~~~~~~~~~
/usr/include/CLucene/LuceneThreads.h:73:32: error: 'pthread_t' does not name a type
73 | static _LUCENE_THREADID_TYPE CreateThread(luceneThreadStartRoutine* func, void* arg);
| ^~~~~~~~~~~~~~~~~~~~~
/usr/include/CLucene/LuceneThreads.h:74:48: error: 'pthread_t' has not been declared
74 | static void JoinThread(_LUCENE_THREADID_TYPE id);
| ^~~~~~~~~~~~~~~~~~~~~
```
(You'll need to use this patch: https://github.com/LibreOffice/core/commit/f7e170eb084cd4e92818de966b287330184749a8 to fix a gpgme related configure error, since the function it checks for was removed)
next prev parent reply other threads:[~2022-10-19 7:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 13:16 [ISSUE] " Duncaen
2022-10-08 21:08 ` oreo639
2022-10-08 21:08 ` oreo639
2022-10-08 21:08 ` oreo639
2022-10-09 18:22 ` Anachron
2022-10-09 18:26 ` Duncaen
2022-10-09 21:28 ` oreo639
2022-10-09 23:15 ` oreo639
2022-10-10 14:48 ` dkwo
2022-10-15 9:44 ` oreo639
2022-10-15 10:41 ` oreo639
2022-10-15 12:54 ` oreo639
2022-10-15 12:54 ` oreo639
2022-10-19 7:40 ` oreo639
2022-10-19 7:41 ` oreo639
2022-10-19 7:41 ` oreo639 [this message]
2022-10-19 7:52 ` oreo639
2022-10-19 8:02 ` oreo639
2022-10-31 17:29 ` dkwo
2022-12-04 23:51 ` oreo639
2022-12-05 0:57 ` oreo639
2022-12-05 1:00 ` oreo639
2022-12-05 1:02 ` oreo639
2022-12-05 3:02 ` oreo639
2022-12-05 3:03 ` oreo639
2022-12-05 3:17 ` oreo639
2022-12-05 3:19 ` oreo639
2022-12-05 4:58 ` oreo639
2022-12-05 4:59 ` oreo639
2022-12-05 5:01 ` oreo639
2022-12-05 5:02 ` oreo639
2022-12-05 18:56 ` oreo639
2022-12-05 18:57 ` oreo639
2022-12-06 1:32 ` oreo639
2022-12-06 2:46 ` oreo639
2022-12-06 2:46 ` oreo639
2022-12-18 3:47 ` oreo639
2023-06-21 16:16 ` [ISSUE] [CLOSED] " Duncaen
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=20221019074141.Zypv71EdPdlLOgXGnK_gtmfKwWfhq54wOGY0Mfm1DU4@z \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).