public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wlgivens at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/11379] fcntl.c:43: error: storage size of Âfex isnÂt known Date: Sun, 14 Mar 2010 09:54:00 -0000 [thread overview] Message-ID: <20100314095434.21609.qmail@sourceware.org> (raw) In-Reply-To: <20100314095206.11379.wlgivens@gmail.com> ------- Additional Comments From wlgivens at gmail dot com 2010-03-14 09:54 ------- Also receive the SAME error with the git build of glibc-2.11.90 + glibc-tools -- http://sourceware.org/bugzilla/show_bug.cgi?id=11379 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-03-14 9:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-14 9:52 [Bug libc/11379] New: fcntl.c:43: error: storage size of fex isnt known wlgivens at gmail dot com 2010-03-14 9:54 ` wlgivens at gmail dot com [this message] 2010-03-14 11:27 ` [Bug ports/11379] " drepper at redhat dot com 2010-05-04 16:21 ` rth at gcc dot gnu dot 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=20100314095434.21609.qmail@sourceware.org \ --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).