public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: danglin@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to l
Date: Wed, 17 Apr 2002 20:36:00 -0000	[thread overview]
Message-ID: <20020418033600.22048.qmail@sources.redhat.com> (raw)

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

From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: law@redhat.com
Cc: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, dave.anglin@nrc.ca,
   mark@codesourcery.com
Subject: Re: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to l
Date: Wed, 17 Apr 2002 23:31:22 -0400 (EDT)

 > Instead we should make sure that whatever paths we need to be in the executable
 > are actually in the executable.  There are flags to make that happen...  The
 > right set of switches should get the behavior we desire.
 
 I have closed this PR since after reinstalling gcc-3.1 under
 hppa2.0w-hp-hpux11.11 I haven't been able to duplicate the problem.  The
 embedded path is correctly set and enabled.  This should allow libgcc_s.sl
 to be located in the installation directory if it isn't found in the
 default location in the build directory.
 
 Frankly, I am puzzled but it may have just been the result of doing
 too many things at once.
 
 Dave
 -- 
 J. David Anglin                                  dave.anglin@nrc.ca
 National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


             reply	other threads:[~2002-04-18  3:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 20:36 John David Anglin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-16 13:16 law
2002-04-16 10:26 John David 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=20020418033600.22048.qmail@sources.redhat.com \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=danglin@gcc.gnu.org \
    --cc=gcc-prs@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).