Bug 571374

Summary:	cross-x86_64-linux-musl/gcc-4.9.3-r99 fails to build in libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
Product:	Gentoo Linux	Reporter:	Ingo Krabbe <ikrabbe.ask>
Component:	[OLD] Development	Assignee:	Gentoo musl team <musl>
Status:	RESOLVED FIXED
Severity:	normal	CC:	musl
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	430702

Description Ingo Krabbe 2016-01-09 14:21:17 UTC

The compilation of the musl cross compiler fails as there are some header files that seem not to exist.

// #include <net/if_ppp.h>
// #include <netax25/ax25.h>
// #include <netipx/ipx.h>
// #include <netrom/netrom.h>
[...]
// #include <sys/ustat.h>

When I drop the missing includes there are consecutive errors due to missing structures then.

What is the preferred way to solve this?
Maybe we can drop the sanitizer.*posix step at all?
If so, how can gcc be configured to do so?
 

Reproducible: Always

Steps to Reproduce:
1.compile cross-x86_64-linux-musl/gcc-4.9.3-r99

Actual Results:  
Error.

Expected Results:  
Success.

I can provide more information, but it might be better to reproduce the problem.

Please note that I already patched the musl overlay gcc-4.9.3-r99.ebuild, to obey the musl patches not only on elibc_musl, but also when doing the cross step, as described in the report comments of 563208.

Comment 1 Felix Janda 2016-01-09 15:25:10 UTC

emerge gcc with USE="-sanitize"

This use flag is masked on musl profiles, but similarly to bug 563208
that does not apply to the case when cross-compiling from glibc. The
comment for the mask refers to bug 504200.

Comment 2 Ingo Krabbe 2016-01-14 05:52:05 UTC

Thank you! USE="-sanitize" helped.

It would be good if the ebuild would at least document that behaviour in the musl overlay or even auto-switch that option on "elibc_musl" and "cross-*musl" categories.

Comment 3 Felix Janda 2016-01-14 07:09:04 UTC

Good to know that USE="-sanitize" helped.

Please reopen this bug. The underlying issue is not really solved.
Furthermore, it makes it easier for someone to find this bug including
the workaround.