Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 864847 - sys-devel/llvm-14.0.6-r2: fails to compile with musl
Summary: sys-devel/llvm-14.0.6-r2: fails to compile with musl
Status: RESOLVED DUPLICATE of bug 838979
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: LLVM support project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-11 02:35 UTC by Felix Janda
Modified: 2022-12-30 21:40 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
build.log.xz (build.log.xz,13.28 KB, application/x-xz)
2022-08-11 02:37 UTC, Felix Janda 		Details
emerge --info (emerge.info,8.11 KB, text/plain)
2022-08-11 02:37 UTC, Felix Janda 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Janda 2022-08-11 02:35:44 UTC 
The first error is:

llvm/lib/Support/Unix/Signals.inc:565:13: error: 'backtrace' was not declared in this scope; did you mean 'StackTrace'?

Reproducible: Always
Comment 1 Felix Janda 2022-08-11 02:37:08 UTC 
Created attachment 799231 [details]
build.log.xz
Comment 2 Felix Janda 2022-08-11 02:37:30 UTC 
Created attachment 799233 [details]
emerge --info
Comment 3 Jory A. Pratt gentoo-dev 2022-08-13 22:57:32 UTC 
(In reply to Felix Janda from comment #0)
> The first error is:
> 
> llvm/lib/Support/Unix/Signals.inc:565:13: error: 'backtrace' was not
> declared in this scope; did you mean 'StackTrace'?
> 
> Reproducible: Always

The question becomes why is configure finding a backtrace header on your system. I have not been able to duplicate on x86_64, arm64, and arm. Compile is successful as configure should not be defining backtrace support exist for musl users.
Comment 4 Felix Janda 2022-08-14 02:03:49 UTC 
This is from sys-libs/libbacktrace
Comment 5 Felix Janda 2022-12-30 21:40:14 UTC 

*** This bug has been marked as a duplicate of bug 838979 ***