public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egmont at uhulinux dot hu" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/245] New: lowlevellock.h not installed Date: Wed, 30 Jun 2004 14:57:00 -0000 [thread overview] Message-ID: <20040630145727.245.egmont@uhulinux.hu> (raw) I compiled and installed the glibc version found in Fedora core 2 using nptl. The installed stdio-lock.h #includes a lowlevellock.h. This lowlevellock.h is present in glibc's source, but is not installed (and is missing from the nptl-devel package of Fedora, too). This causes at least gcc-2.95 compilation to fail. I don't know if the bug is fixed in current CVS, but ChangeLog of the last several months doesn't mention lowlevellock. -- Summary: lowlevellock.h not installed Product: glibc Version: 2.3.3 Status: NEW Severity: normal Priority: P2 Component: nptl AssignedTo: drepper at redhat dot com ReportedBy: egmont at uhulinux dot hu CC: glibc-bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=245 ------- 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:[~2004-06-30 14:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-30 14:57 egmont at uhulinux dot hu [this message] 2004-06-30 16:02 ` [Bug nptl/245] " drepper at redhat dot com 2004-06-30 16:23 ` egmont at uhulinux dot hu 2005-09-23 19:55 ` drepper at redhat dot com 2005-09-25 14:31 ` egmont at uhulinux dot hu 2006-04-27 23:46 ` [Bug nptl/245] Wrong stdio-lock.h installed bero at arklinux dot org 2006-04-27 23:54 ` bero at arklinux dot org 2007-02-18 4:01 ` drepper at redhat 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=20040630145727.245.egmont@uhulinux.hu \ --to=sourceware-bugzilla@sources.redhat.com \ --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).