public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/21526] libstdc++-v3 testsuite hangs on cygwin
Date: Thu, 12 May 2005 15:15:00 -0000	[thread overview]
Message-ID: <20050512151528.696.qmail@sourceware.org> (raw)
In-Reply-To: <20050512055332.21526.billingd@gcc.gnu.org>


------- Additional Comments From mark at codesourcery dot com  2005-05-12 15:15 -------
Subject: Re:  libstdc++-v3 testsuite hangs on cygwin

pcarlini at suse dot de wrote:
> ------- Additional Comments From pcarlini at suse dot de  2005-05-12 10:02 -------
> In other terms, we should tell DejaGNU that all the tests involving fifos must
> be skipped on such platform, because fifos are available but not completely ok.

Sorry; I assumed Cygwin must not have mkfifo, given that the test was 
disabled there; I didn't consider has-mkfifo-but-broken!

The fix for this will be to modify target-supports.exp to check the 
platform as well.

If you change check_mkfifo_available in target-supports.exp to do:

proc check_mkfifo_available {} {
     if {[istarget *-*-cygwin*]} {
       # Cygwin has mkfifo, but support is incomplete.
       return 0
     }

     return [check_function_available "mkfifo"]
}

that should fix it.  Would you mind trying that?

Thanks,



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21526


  parent reply	other threads:[~2005-05-12 15:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12  5:53 [Bug libstdc++/21526] New: " billingd at gcc dot gnu dot org
2005-05-12  6:26 ` [Bug libstdc++/21526] " pinskia at gcc dot gnu dot org
2005-05-12  6:27 ` pinskia at gcc dot gnu dot org
2005-05-12  6:34 ` david dot billinghurst at comalco dot riotinto dot com dot au
2005-05-12  9:41 ` pcarlini at suse dot de
2005-05-12 10:02 ` pcarlini at suse dot de
2005-05-12 15:15 ` mark at codesourcery dot com [this message]
2005-05-12 15:23 ` pcarlini at suse dot de
2005-05-12 15:32 ` mark at codesourcery dot com
2005-05-13  0:32 ` david dot billinghurst at comalco dot riotinto dot com dot au
2005-05-13  0:37 ` mark at codesourcery dot com
2005-05-16  0:51 ` cvs-commit at gcc dot gnu dot org
2005-05-16  0:55 ` cvs-commit at gcc dot gnu dot org
2005-05-16  0:58 ` billingd at gcc dot gnu dot org
2005-05-16  0:59 ` david dot billinghurst at comalco dot riotinto dot com dot au
2005-06-05  7:51 ` pinskia 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=20050512151528.696.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).