public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kallisti5 at unixzen dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/113143] New: Remove usage of ucontext.h Date: Tue, 26 Dec 2023 03:43:45 +0000 [thread overview] Message-ID: <bug-113143-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113143 Bug ID: 113143 Summary: Remove usage of ucontext.h Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: kallisti5 at unixzen dot com Target Milestone: --- libgo/sysinfo.c references #include <ucontext.h> which breaks the libgo build on strict POSIX compliance platforms. ucontext.h was removed in issue 7, and types were migrated to signal.h. Old 2004 spec: https://pubs.opengroup.org/onlinepubs/009695399/basedefs/ucontext.h.html Pretty much any recent spec: (ucontext.h is gone) https://pubs.opengroup.org/onlinepubs/9699919799/
next reply other threads:[~2023-12-26 3:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-26 3:43 kallisti5 at unixzen dot com [this message] 2023-12-26 3:48 ` [Bug go/113143] " kallisti5 at unixzen dot com 2023-12-26 4:48 ` ian at airs dot com 2023-12-26 13:13 ` kallisti5 at unixzen dot com 2023-12-26 23:16 ` ian at airs dot com 2023-12-27 2:31 ` kallisti5 at unixzen dot com 2023-12-27 2:34 ` kallisti5 at unixzen dot com 2023-12-27 2:40 ` pinskia at gcc dot gnu.org 2023-12-27 3:20 ` kallisti5 at unixzen dot com 2023-12-27 3:38 ` kallisti5 at unixzen dot com 2023-12-27 23:20 ` ian at airs dot com 2023-12-29 1:45 ` kallisti5 at unixzen dot com 2023-12-30 6:26 ` ian at airs dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113143-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).