public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/5400] New: Assume fdatasync syscall always exists
Date: Mon, 26 Nov 2007 00:51:00 -0000 [thread overview]
Message-ID: <20071126005142.5400.aurelien@aurel32.net> (raw)
The fdatasync syscall is present for a very long time in the linux kernel
(since pre 2.0 kernels) on all architectures except alpha. On this architecture
it has been recently added to the 2.6.22 kernel.
This causes fdatasync() to fail on a glibc compiled against a 2.6.22 kernel run
on pre 2.6.22 kernel.
Patch will follow.
--
Summary: Assume fdatasync syscall always exists
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: aurelien at aurel32 dot net
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: alphaev68-unknown-linux-gnu
GCC host triplet: alphaev68-unknown-linux-gnu
GCC target triplet: alphaev68-unknown-linux-gnu
http://sourceware.org/bugzilla/show_bug.cgi?id=5400
------- 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:[~2007-11-26 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 0:51 aurelien at aurel32 dot net [this message]
2007-11-26 0:52 ` [Bug libc/5400] " aurelien at aurel32 dot net
2007-12-08 10:02 ` drepper at redhat dot com
2008-11-26 23:30 ` [Bug ports/5400] " drepper at redhat dot com
2010-05-04 3:01 ` mattst88 at gmail 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=20071126005142.5400.aurelien@aurel32.net \
--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: link
Be 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).