public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bneumeier at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/18870] New: sem_open.c fails to compile with missing symbol FUTEX_SHARED Date: Wed, 26 Aug 2015 00:32:00 -0000 [thread overview] Message-ID: <bug-18870-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18870 Bug ID: 18870 Summary: sem_open.c fails to compile with missing symbol FUTEX_SHARED Product: glibc Version: 2.22 Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: bneumeier at gmail dot com CC: carlos at redhat dot com Target Milestone: --- Created attachment 8551 --> https://sourceware.org/bugzilla/attachment.cgi?id=8551&action=edit Add missing include directive. In 2.22 and master, when doing a x86_64-pc-linux-gnu to sparc-pc-linux-gnu cross-toolchain build, sem_open.c fails to compile because it can't find FUTEX_SHARED. It looks to me like an include directive got missed. The attached fixes it for me on 2.22. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-08-26 0:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-26 0:32 bneumeier at gmail dot com [this message] 2015-08-26 9:40 ` [Bug build/18870] " joseph at codesourcery dot com 2015-08-30 16:08 ` bneumeier at gmail dot com 2015-08-31 22:28 ` cvs-commit at gcc dot gnu.org 2015-08-31 22:34 ` cvs-commit at gcc dot gnu.org 2015-08-31 23:09 ` joseph at codesourcery dot com 2015-09-01 23:17 ` bneumeier at gmail dot com 2015-10-17 4:55 ` cvs-commit at gcc dot gnu.org 2015-10-29 17:05 ` jsm28 at gcc dot gnu.org
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-18870-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).