Bug 536834 – dev-scheme/guile: header install slightly broken

• Status: RESOLVED DUPLICATE of bug 493464
• Product: Gentoo Linux

[Description DaggyStyle 2015-01-17 12:26:57 UTC]

a patch against hardened-dev git, musl branch to allow compilation of autogen-5.18.1

this patch isn't intended for inclusion to official portage tree, it is intended for the musl branch in the hardened-dev overlay.

Reproducible: Always

[Comment 1 DaggyStyle 2015-01-17 12:28:04 UTC]

Created attachment 394154 [details, diff]
patch

[Comment 2 DaggyStyle 2015-01-17 12:29:14 UTC]

please assign to Anthony Basile

[Comment 3 Felix Janda 2015-01-17 21:27:37 UTC]

This is actually a bug in Guile's headers which has been fixed in Guile 2.0.10

http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=36c40440078c005cd5e239cca487d29f6f60007d;hp=b1fe20c24ccb380420ea1ffdc7f249224072dcdc

[Comment 4 Jeroen Roovers (RETIRED) 2015-01-19 07:26:55 UTC]

What error would that print?

[Comment 5 Felix Janda 2015-01-20 13:26:44 UTC]

The problem is more precisely, that musl ships the header
<stdnoreturn.h> which is likely to become part of the next C Standard.
This header is supposed to define "noreturn" (used to mark functions
which don't return). musl uses "__attribute__((__noreturn__))" as the
definition for "noreturn". Now there is also guile's public header
<libguile/__scm.h> which defines "SCM_NORETURN" as
"__attribute__ ((noreturn))". So if <stdnoreturn.h> is included before
<libguile/__sch.h> we get "__attribute__ ((__attribute((__noreturn__))))
which of course throws an error. The linked commit fixes this problem.

[Comment 6 SpanKY 2015-02-10 21:42:55 UTC]

doesn't look like it has anything to do with autogen

[Comment 7 Anthony Basile 2015-02-13 11:34:26 UTC]

There is more history in bug #493464.

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