Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 831522 - dev-util/apitrace-9.0-r3 fails to compile: backtrace.h:54:10: fatal error: gstdint.h: No such file or directory
Summary: dev-util/apitrace-9.0-r3 fails to compile: backtrace.h:54:10: fatal error: gs...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
: 924151 (view as bug list)
Depends on:
Blocks: missing-depend
  Show dependency tree
 
Reported: 2022-01-20 07:13 UTC by Agostino Sarubbo
Modified: 2024-05-23 17:46 UTC (History)
0 users

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

Attachments
build.log (build.log,151.27 KB, text/plain)
2022-01-20 07:13 UTC, Agostino Sarubbo 		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 Agostino Sarubbo gentoo-dev 2022-01-20 07:13:31 UTC 
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-util/apitrace-9.0-r3 fails to compile.
Discovered on: amd64 (internal ref: tinderbox_musl)

NOTE:
This machine uses MUSL libc
Comment 1 Agostino Sarubbo gentoo-dev 2022-01-20 07:13:34 UTC 
Created attachment 762726 [details]
build.log

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2022-01-20 07:13:35 UTC 
Error(s) that match a know pattern in addition to what has been reported in the summary:


/var/tmp/portage/dev-util/apitrace-9.0-r3/work/apitrace-9.0/thirdparty/libbacktrace/backtrace.h:54:10: fatal error: gstdint.h: No such file or directory
/var/tmp/portage/dev-util/apitrace-9.0-r3/work/apitrace-9.0/thirdparty/libbacktrace/backtrace.h:54:10: fatal error: gstdint.h: No such file or directory
Comment 3 Matt Turner gentoo-dev 2024-05-23 17:46:32 UTC 
*** Bug 924151 has been marked as a duplicate of this bug. ***