* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
@ 2022-10-08 21:08 ` oreo639
2022-10-08 21:08 ` oreo639
` (35 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-08 21:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1272397789
Comment:
> igt-gpu-tools
That should be fixed here https://github.com/void-linux/void-packages/pull/39780.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
2022-10-08 21:08 ` oreo639
@ 2022-10-08 21:08 ` oreo639
2022-10-08 21:08 ` oreo639
` (34 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-08 21:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 251 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1272397789
Comment:
> igt-gpu-tools
That should have been fixed here https://github.com/void-linux/void-packages/pull/39780.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures 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
` (33 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-08 21:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1272397789
Comment:
> igt-gpu-tools
That should have been fixed here https://github.com/void-linux/void-packages/pull/39780.
Same for apl here: https://github.com/void-linux/void-packages/pull/39750
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (2 preceding siblings ...)
2022-10-08 21:08 ` oreo639
@ 2022-10-09 18:22 ` Anachron
2022-10-09 18:26 ` Duncaen
` (32 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: Anachron @ 2022-10-09 18:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1272600797
Comment:
Can we tag maintainers or at least add their email addresses?
If I saw that correctly none of them is maintained by me.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (3 preceding siblings ...)
2022-10-09 18:22 ` Anachron
@ 2022-10-09 18:26 ` Duncaen
2022-10-09 21:28 ` oreo639
` (31 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: Duncaen @ 2022-10-09 18:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1272601624
Comment:
No I don't want to have to wait 5 months because 100 different people fix minor issues.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (4 preceding siblings ...)
2022-10-09 18:26 ` Duncaen
@ 2022-10-09 21:28 ` oreo639
2022-10-09 23:15 ` oreo639
` (30 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-09 21:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1272631539
Comment:
> cross-powerpc64le-linux-gnu
I can't reproduce this build failure?
> cross-powerpcle-linux-gnu
This is caused by glibc using big-endian specific instructions (that would normally trigger an exception in little-endian mode) that got blacklisted when assembling little-endian code in binutils 2.36.
Would it be best to just mark the package as broken for now?
> cross-x86_64-w64-mingw32
That should be able to be fixed by updating it to gcc 12.2+:
https://github.com/gcc-mirror/gcc/commit/de6f402a54f7e6a3f8a79d723a25724e6274cc3e
https://github.com/gcc-mirror/gcc/commit/ad5d760b815b3d491bdb5d97f6e053d60d6991b9
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (5 preceding siblings ...)
2022-10-09 21:28 ` oreo639
@ 2022-10-09 23:15 ` oreo639
2022-10-10 14:48 ` dkwo
` (29 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-09 23:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1272397789
Comment:
> igt-gpu-tools
That should have been fixed here https://github.com/void-linux/void-packages/pull/39780.
Same for apl here: https://github.com/void-linux/void-packages/pull/39750
Edit: also coreboot-utils: https://github.com/void-linux/void-packages/commit/8ad38d98423afc0b15b663072e9de23c869d3d2a
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (6 preceding siblings ...)
2022-10-09 23:15 ` oreo639
@ 2022-10-10 14:48 ` dkwo
2022-10-15 9:44 ` oreo639
` (28 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: dkwo @ 2022-10-10 14:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 177 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1273431910
Comment:
`singular` should be fixed by #39866
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (7 preceding siblings ...)
2022-10-10 14:48 ` dkwo
@ 2022-10-15 9:44 ` oreo639
2022-10-15 10:41 ` oreo639
` (27 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-15 9:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1279707374
Comment:
The qemu build failure is this: https://github.com/void-linux/void-packages/blob/master/srcpkgs/qemu/patches/musl-fix-sigevent-and-sigval_t.patch
The patch will need to be removed in the gcc12 PR.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (8 preceding siblings ...)
2022-10-15 9:44 ` oreo639
@ 2022-10-15 10:41 ` oreo639
2022-10-15 12:54 ` oreo639
` (26 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-15 10:41 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1279707374
Comment:
The qemu build failure is this: https://github.com/void-linux/void-packages/blob/master/srcpkgs/qemu/patches/musl-fix-sigevent-and-sigval_t.patch
The patch will need to be removed in the gcc12 PR.
Edit: this has been fixed in the gcc 12 PR.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (9 preceding siblings ...)
2022-10-15 10:41 ` oreo639
@ 2022-10-15 12:54 ` oreo639
2022-10-15 12:54 ` oreo639
` (25 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-15 12:54 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1279740115
Comment:
I was able to fix the build failure in openjdk10-bootstrap with gcc 12, however after that I get a build failure with glibc 2.36:
https://gist.github.com/oreo639/470e234e45134c56383bf722dd2d1ccb
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (10 preceding siblings ...)
2022-10-15 12:54 ` oreo639
@ 2022-10-15 12:54 ` oreo639
2022-10-19 7:40 ` oreo639
` (24 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-15 12:54 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1279740115
Comment:
I was able to fix the build failure in openjdk10-bootstrap with gcc 12:
https://gist.github.com/oreo639/9fcd2f6736a84434a7678ba27b0c0e5e
However after that I get a build failure with glibc 2.36:
https://gist.github.com/oreo639/470e234e45134c56383bf722dd2d1ccb
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (11 preceding siblings ...)
2022-10-15 12:54 ` oreo639
@ 2022-10-19 7:40 ` oreo639
2022-10-19 7:41 ` oreo639
` (23 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-19 7:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1708 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);
| ^~~~~~~~~~~~~~~~~~~~~
```
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (12 preceding siblings ...)
2022-10-19 7:40 ` oreo639
@ 2022-10-19 7:41 ` oreo639
2022-10-19 7:41 ` oreo639
` (22 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-19 7:41 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1867 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)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (13 preceding siblings ...)
2022-10-19 7:41 ` oreo639
@ 2022-10-19 7:41 ` oreo639
2022-10-19 7:52 ` oreo639
` (21 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-19 7:41 UTC (permalink / raw)
To: ml
[-- 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)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (14 preceding siblings ...)
2022-10-19 7:41 ` oreo639
@ 2022-10-19 7:52 ` oreo639
2022-10-19 8:02 ` oreo639
` (20 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-19 7:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2005 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)
Edit: rebuilding clucene fixes the issue so maybe the pthreads patch didn't get applied?
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (15 preceding siblings ...)
2022-10-19 7:52 ` oreo639
@ 2022-10-19 8:02 ` oreo639
2022-10-31 17:29 ` dkwo
` (19 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-10-19 8:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2110 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)
Edit: rebuilding clucene fixes the issue so maybe the pthreads patch didn't get applied?
Edit 2: Yep https://github.com/void-linux/void-packages/commit/6af326e6c89216b4ddf9a9dd15025e39fc8a412f
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (16 preceding siblings ...)
2022-10-19 8:02 ` oreo639
@ 2022-10-31 17:29 ` dkwo
2022-12-04 23:51 ` oreo639
` (18 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: dkwo @ 2022-10-31 17:29 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1297429997
Comment:
`singular` has now been updated, so it should be fine.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (17 preceding siblings ...)
2022-10-31 17:29 ` dkwo
@ 2022-12-04 23:51 ` oreo639
2022-12-05 0:57 ` oreo639
` (17 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-04 23:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (18 preceding siblings ...)
2022-12-04 23:51 ` oreo639
@ 2022-12-05 0:57 ` oreo639
2022-12-05 1:00 ` oreo639
` (16 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 0:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I don't see anything in Alpine related to this issue although they compile lxc with gdc rather than dmd and I really do not want to go through the trouble of enabling gdc.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (19 preceding siblings ...)
2022-12-05 0:57 ` oreo639
@ 2022-12-05 1:00 ` oreo639
2022-12-05 1:02 ` oreo639
` (15 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 1:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I don't see anything in Alpine related to this issue although they compile lxc with gdc rather than dmd and I really do not want to go through the trouble of enabling gdc. (keep in mind that gdc requires a working d compiler anyway)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (20 preceding siblings ...)
2022-12-05 1:00 ` oreo639
@ 2022-12-05 1:02 ` oreo639
2022-12-05 3:02 ` oreo639
` (14 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 1:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I don't see anything in Alpine related to this issue although they compile lxc with gdc rather than dmd and I really do not want to go through the trouble of re-enabling gdc. (keep in mind that gdc requires a working d compiler anyway)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (21 preceding siblings ...)
2022-12-05 1:02 ` oreo639
@ 2022-12-05 3:02 ` oreo639
2022-12-05 3:03 ` oreo639
` (13 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 3:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I don't see anything in Alpine related to this issue although they compile lxc with gdc rather than dmd and I really do not want to go through the trouble of re-enabling gdc. (keep in mind that gdc requires a working d compiler anyway)
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (22 preceding siblings ...)
2022-12-05 3:02 ` oreo639
@ 2022-12-05 3:03 ` oreo639
2022-12-05 3:17 ` oreo639
` (12 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 3:03 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I don't see anything in Alpine related to this issue although they compile lxc with gdc rather than dmd and I really do not want to go through the trouble of re-enabling gdc. (keep in mind that gdc requires a working d compiler anyway)
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (23 preceding siblings ...)
2022-12-05 3:03 ` oreo639
@ 2022-12-05 3:17 ` oreo639
2022-12-05 3:19 ` oreo639
` (11 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 3:17 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I don't see anything in Alpine related to this issue although they compile lxc with gdc rather than dmd and I really do not want to go through the trouble of re-enabling gdc. (keep in mind that gdc requires a working d compiler anyway)
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue (although it did fix it from messing up the gdb backtrace)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (24 preceding siblings ...)
2022-12-05 3:17 ` oreo639
@ 2022-12-05 3:19 ` oreo639
2022-12-05 4:58 ` oreo639
` (10 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 3:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2314 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I don't see anything in Alpine related to this issue although they compile lxc with gdc rather than dmd and I really do not want to go through the trouble of re-enabling gdc. (keep in mind that gdc requires a working d compiler anyway)
Also alpine compiles ldc with llvm14 and the error is in C/C++ code so it could be also related to that.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue (although it did fix it from messing up the gdb backtrace)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (25 preceding siblings ...)
2022-12-05 3:19 ` oreo639
@ 2022-12-05 4:58 ` oreo639
2022-12-05 4:59 ` oreo639
` (9 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 4:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM, alpine uses LLVM 14 which we don't have so I can't test it. The build failure also occurs with clang/clang++ and libstdc++ although I haven't gotten it to build with libc++ so I can't say if that works.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue (although it did fix it from messing up the gdb backtrace)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (26 preceding siblings ...)
2022-12-05 4:58 ` oreo639
@ 2022-12-05 4:59 ` oreo639
2022-12-05 5:01 ` oreo639
` (8 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 4:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 which we don't have so I can't test it. The build failure also occurs with clang/clang++ and libstdc++ although I haven't gotten it to build with libc++ so I can't say if that works.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue (although it did fix it from messing up the gdb backtrace)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (27 preceding siblings ...)
2022-12-05 4:59 ` oreo639
@ 2022-12-05 5:01 ` oreo639
2022-12-05 5:02 ` oreo639
` (7 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 5:01 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 which we don't have so I can't test it. The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue (although it did fix it from messing up the gdb backtrace)
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (28 preceding siblings ...)
2022-12-05 5:01 ` oreo639
@ 2022-12-05 5:02 ` oreo639
2022-12-05 18:56 ` oreo639
` (6 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 5:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 which we don't have so I can't test it. The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue it did stop libexecinfo from messing up the gdb backtrace.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (29 preceding siblings ...)
2022-12-05 5:02 ` oreo639
@ 2022-12-05 18:56 ` oreo639
2022-12-05 18:57 ` oreo639
` (5 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 18:56 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 although even after updating to that the crash still occurs (albeit in a slightly different place). The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue it did stop libexecinfo from messing up the gdb backtrace.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (30 preceding siblings ...)
2022-12-05 18:56 ` oreo639
@ 2022-12-05 18:57 ` oreo639
2022-12-06 1:32 ` oreo639
` (4 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-05 18:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 although even after updating to that the crash still occurs (albeit in a slightly different place, but still in `Target::_init()`). The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue it did stop libexecinfo from messing up the gdb backtrace.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (31 preceding siblings ...)
2022-12-05 18:57 ` oreo639
@ 2022-12-06 1:32 ` oreo639
2022-12-06 2:46 ` oreo639
` (3 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-06 1:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 although even after updating to that the crash still occurs (albeit in a slightly different place, but still in `Target::_init()`). I can also confirm that updating musl and using the gcc git snapshot alpine uses doesn't fix the crash either. The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue it did stop libexecinfo from messing up the gdb backtrace.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (32 preceding siblings ...)
2022-12-06 1:32 ` oreo639
@ 2022-12-06 2:46 ` oreo639
2022-12-06 2:46 ` oreo639
` (2 subsequent siblings)
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-06 2:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2488 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 although even after updating to that the crash still occurs (albeit in a slightly different place, but still in `Target::_init()`). I can also confirm that updating musl and using the gcc git snapshot alpine uses doesn't fix the crash either. The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue it did stop libexecinfo from messing up the gdb backtrace.
EDIT 1: compiling ldc without dmd works fine.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (33 preceding siblings ...)
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
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-06 2:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 although even after updating to that the crash still occurs (albeit in a slightly different place, but still in `Target::_init()`). I can also confirm that updating musl and using the gcc git snapshot alpine uses doesn't fix the crash either. The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue it did stop libexecinfo from messing up the gdb backtrace.
EDIT 1: compiling ldc without using dmd works fine.
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (34 preceding siblings ...)
2022-12-06 2:46 ` oreo639
@ 2022-12-18 3:47 ` oreo639
2023-06-21 16:16 ` [ISSUE] [CLOSED] " Duncaen
36 siblings, 0 replies; 38+ messages in thread
From: oreo639 @ 2022-12-18 3:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1356655899
Comment:
ldc should be fixed by https://github.com/void-linux/void-packages/pull/41158
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: [ISSUE] [CLOSED] [TRACKING] gcc 12 build failures
2022-10-08 13:16 [ISSUE] [TRACKING] gcc 12 build failures Duncaen
` (35 preceding siblings ...)
2022-12-18 3:47 ` oreo639
@ 2023-06-21 16:16 ` Duncaen
36 siblings, 0 replies; 38+ messages in thread
From: Duncaen @ 2023-06-21 16:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]
Closed issue by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/39809
Description:
https://vasilek.cz/logs/gcc12-musl/bad/
- [x] Carla
- [x] The-Powder-Toy
- [x] XQilla
- [x] advancecomp
- [x] afterstep
- [x] amdvlk
- [x] apl
- [x] asignify
- [x] attract
- [x] barrier
- [x] bctoolbox
- [x] beignet
- [x] bish
- [x] blackboxwm
- [x] blobby2
- [x] bonnie++
- [x] ccache
- [x] cglm
- [x] chromium
- [x] clucene
- [x] codeblocks
- [x] codelite
- [x] commoncpp2
- [x] coreboot-utils
- [x] cross-powerpc64le-linux-gnu
- [x] cross-powerpcle-linux-gnu (marked broken)
- [x] cross-x86_64-w64-mingw32
- [x] darkice
- [x] darkplaces
- [x] edb-debugger
- [x] electron19 (#40890)
- [x] endless-sky-gl21
- [x] facter
- [x] ffmpeg
- [x] flatbuffers
- [x] fluxbox
- [x] freeimage
- [x] fsearch
- [x] ghdl #40614
- [x] glmark2
- [x] glog
- [x] gloox
- [x] glslViewer
- [x] goldendict
- [x] grive2
- [x] grub-customizer
- [x] gstreamermm
- [x] hashdeep
- [x] htmlcxx
- [x] igt-gpu-tools
- [x] incron
- [x] ipv6calc
- [x] jigdo
- [x] john
- [x] juCi++
- [x] kakoune
- [x] kea
- [x] kodi-addon-pvr-hts
- [x] ldc https://github.com/void-linux/void-packages/pull/40931
- [x] leatherman
- [x] libbitcoin-system
- [x] libebml
- [x] libgdal
- [x] liblastfm-qt5
- [x] libomxil-bellagio
- [x] libpgf
- [x] libreoffice
- [x] linux4.14
- [x] linux4.9
- [x] lyx
- [x] melonDS
- [x] mercury
- [x] mimic
- [x] monero-gui
- [x] mpdscribble
- [x] msp430-toolchain
- [x] netpgp
- [x] network-ups-tools
- [x] nmap
- [x] ogmtools
- [x] openbabel
- [x] openjdk10-bootstrap
- [x] openjdk9-bootstrap
- [x] openmsx
- [x] openmw
- [x] opensc
- [x] owncloudclient
- [x] papi
- [x] passwordsafe
- [x] psensor
- [x] qemu-user-static
- [x] qemu
- [x] qt5-doc
- [x] qv4l2
- [x] rdfind
- [x] retroshare
- [x] rlottie
- [x] rmilter
- [x] rocksdb
- [x] rstudio
- [x] singular
- [x] slim
- [x] snapper
- [x] source-highlight
- [x] subtitleeditor
- [x] supertux2
- [x] tab
- [x] textadept
- [x] textosaurus
- [x] ucommon
- [x] uhd
- [x] unittest-cpp
- [x] upx
- [x] vtk
- [x] xstow
- [x] xwmfs
- [x] yosys
- [x] zeromq
- [x] zynaddsubfx
^ permalink raw reply [flat|nested] 38+ messages in thread