public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: objc/2902: collect2 doesn't find ctors/dtors in shared libraries under hpux10.20
Date: Fri, 04 Jan 2002 22:46:00 -0000	[thread overview]
Message-ID: <20020105064601.21164.qmail@sources.redhat.com> (raw)

The following reply was made to PR objc/2902; it has been noted by GNATS.

From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: rodrigc@gcc.gnu.org, dave.anglin@nrc.ca, gcc-bugs@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, law@redhat.com, rodrigc@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: objc/2902: collect2 doesn't find ctors/dtors in shared libraries under hpux10.20
Date: Sat, 5 Jan 2002 01:44:55 -0500 (EST)

 > Synopsis: collect2 doesn't find ctors/dtors in shared libraries under hpux10.20
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Fri Jan  4 22:33:29 2002
 > State-Changed-Why:
 >     Does this problem still occur in gcc 3.0.3 or
 >     in gcc 3.1 CVS?
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2902
 
 This problem was fixed prior to the 3.0 release.  As I recall, certain
 symbols were in the wrong section.
 
 Please close 2902.
 
 Dave
 -- 
 J. David Anglin                                  dave.anglin@nrc.ca
 National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


             reply	other threads:[~2002-01-05  6:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 22:46 John David Anglin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04 22:51 rodrigc
2002-01-04 22:33 rodrigc
2001-06-13  8:46 law
2001-05-22 11:46 dave.anglin

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=20020105064601.21164.qmail@sources.redhat.com \
    --to=dave@hiauly1.hia.nrc.ca \
    --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).