public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lacombar at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/11894] New: linux/sys/ptrace.h namespace pollution Date: Mon, 09 Aug 2010 01:18:00 -0000 [thread overview] Message-ID: <20100809011750.11894.lacombar@gmail.com> (raw) Glibc 2.11.2 failed with the following: In file included from ../sysdeps/unix/sysv/linux/ptrace.c:21:0: ../sysdeps/unix/sysv/linux/sys/ptrace.h:135:3: error: expected identifier before numeric constant make[3]: *** [/targets/sh4-system-linux-gnu/build/build-libc/misc/ptrace.o] Error 1 make[3]: Leaving directory `/targets/src/glibc-2.11.2/misc' make[2]: *** [misc/subdir_lib] Error 2 make[2]: Leaving directory `/data/src/toolchain/build/targets/src/glibc-2.11.2' make[1]: *** [all] Error 2 make[1]: Leaving directory `/targets/sh4-system-linux-gnu/build/build-libc' It was built against a 2.6.15 Linux kernel. -- Summary: linux/sys/ptrace.h namespace pollution Product: glibc Version: 2.11 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: lacombar at gmail dot com CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i486-unknown-linux-gnu GCC host triplet: i486-unknown-linux-gnu GCC target triplet: sh4-unknown-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=11894 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-08-09 1:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-09 1:18 lacombar at gmail dot com [this message] 2010-08-09 1:21 ` [Bug libc/11894] " lacombar at gmail dot com 2010-10-04 2:38 ` drepper dot fsp at gmail dot com 2010-10-04 5:08 ` kkojima at rr dot iij4u dot or dot jp
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=20100809011750.11894.lacombar@gmail.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).