public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Harri Porten <harri@kde.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5933: HP-UX: broken MI of virtual classes
Date: Fri, 05 Apr 2002 05:36:00 -0000	[thread overview]
Message-ID: <20020405133603.10589.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/5933; it has been noted by GNATS.

From: Harri Porten <harri@kde.org>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
    nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/5933: HP-UX: broken MI of virtual classes
Date: Fri, 05 Apr 2002 15:31:06 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5933
 
 I just tested with the 3.1 20020404 CVS version: this bug is still
 present and makes it impossible to compile Integration Test Qt/X11 2.3
 on HP-UX 11.00 (hppa1.1). The produced 'uic' binary hangs when
 processing .ui files and makes it therefore impossible to finish the
 build.


             reply	other threads:[~2002-04-05 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05  5:36 Harri Porten [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-07 15:31 danglin
2002-03-13  6:36 porten

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=20020405133603.10589.qmail@sources.redhat.com \
    --to=harri@kde.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).