public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/25936] libgomp needs to link against rt on HPUX
Date: Sun, 29 Jan 2006 20:26:00 -0000	[thread overview]
Message-ID: <20060129202654.17453.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25936-276@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from pinskia at gcc dot gnu dot org  2006-01-29 20:26 -------
Confirmed.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
  GCC build triplet|hppa64-hp-hpux11.11         |
   GCC host triplet|hppa64-hp-hpux11.11         |
   Last reconfirmed|0000-00-00 00:00:00         |2006-01-29 20:26:54
               date|                            |
            Summary|FAIL: libgomp.c/appendix-   |libgomp needs to link
                   |a/a.15.1.c (test for excess |against rt on HPUX
                   |errors)                     |


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


  parent reply	other threads:[~2006-01-29 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24  0:03 [Bug libgomp/25936] New: FAIL: libgomp.c/appendix-a/a.15.1.c (test for excess errors) danglin at gcc dot gnu dot org
2006-01-24  0:59 ` [Bug libgomp/25936] " pinskia at gcc dot gnu dot org
2006-01-24  2:12 ` dave at hiauly1 dot hia dot nrc dot ca
2006-01-29 20:26 ` pinskia at gcc dot gnu dot org [this message]
2006-02-08 17:46 ` [Bug libgomp/25936] libgomp needs to link against rt on HPUX roger at eyesopen dot com
2006-02-08 18:17 ` dave at hiauly1 dot hia dot nrc dot ca
2006-02-13  2:33 ` sayle at gcc dot gnu dot org
2006-02-13 19:02 ` roger at eyesopen 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=20060129202654.17453.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).