public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sergstesh at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11875] 'make' fails even though 'configure' is OK
Date: Wed, 04 Aug 2010 12:00:00 -0000	[thread overview]
Message-ID: <20100804120000.6738.qmail@sourceware.org> (raw)
In-Reply-To: <20100804042204.11875.sergstesh@yahoo.com>


------- Additional Comments From sergstesh at yahoo dot com  2010-08-04 11:59 -------
(In reply to comment #10)
> Of course this is a 333 dup.  Don't ever file build problem reports in BZ.  This
> is what mailing lists are for.
> 
> *** This bug has been marked as a duplicate of 333 ***


By the way, Mr. Ulrich Drepper, how about your common sense ?

Look at this: http://ftp.gnu.org/gnu/glibc/?C=M;O=D :

glibc-2.12.1.tar.bz2                       03-Aug-2010 06:06   15M 

, i.e. look at the _date_. And now look at the date of this bug report.

Now, based on your common sense, how many responses can expect in mailing lists
taking into account the time passed between the release and my bug report ?

Today is only August the 4-th in my timezone, and I am to the East of you, so I
found this bug just several hours after the release.

And which mailing lists did you mean ?



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11875

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-08-04 12:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  4:22 [Bug libc/11875] New: " sergstesh at yahoo dot com
2010-08-04  4:24 ` [Bug libc/11875] " sergstesh at yahoo dot com
2010-08-04  4:26 ` sergstesh at yahoo dot com
2010-08-04  4:35 ` sergstesh at yahoo dot com
2010-08-04  4:36 ` sergstesh at yahoo dot com
2010-08-04  4:39 ` sergstesh at yahoo dot com
2010-08-04  4:40 ` sergstesh at yahoo dot com
2010-08-04  5:24 ` sergstesh at yahoo dot com
2010-08-04  5:47 ` sergstesh at yahoo dot com
2010-08-04  6:08 ` sergstesh at yahoo dot com
2010-08-04  7:11 ` sergstesh at yahoo dot com
2010-08-04  7:12 ` drepper at redhat dot com
2010-08-04  7:50 ` sergstesh at yahoo dot com
2010-08-04  7:53 ` sergstesh at yahoo dot com
2010-08-04  9:57 ` sergstesh at yahoo dot com
2010-08-04 12:00 ` sergstesh at yahoo dot com [this message]
2010-08-04 15:31 ` sergstesh at yahoo dot com
2010-08-04 19:54 ` aj at suse dot de
2010-08-05 18:40 ` sergstesh at yahoo dot com
2010-08-05 18:48 ` sergstesh at yahoo dot com
2010-08-05 18:52 ` sergstesh at yahoo dot com
2010-08-05 18:56 ` sergstesh at yahoo dot com
     [not found] <bug-11875-131@http.sourceware.org/bugzilla/>
2014-06-30 17:25 ` fweimer 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=20100804120000.6738.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: 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).