public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Richard B. Kreckel" <kreckel@ginac.de>
To: ro@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5505: Doubts about a patch for OSF
Date: Mon, 18 Feb 2002 12:56:00 -0000	[thread overview]
Message-ID: <20020218205602.27959.qmail@sources.redhat.com> (raw)

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

From: "Richard B. Kreckel" <kreckel@ginac.de>
To: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: target/5505: Doubts about a patch for OSF
Date: Mon, 18 Feb 2002 21:49:22 +0100 (CET)

 On Mon, 4 Feb 2002, Richard B. Kreckel wrote:
 > On Mon, 4 Feb 2002, Rainer Orth wrote:
 > > Fine.  Instead of patching the whole machine, it should be sufficient to
 > > just drop a copy of the patched ld in
 > > $prefix/lib/gcc-lib/alpha-dec-osf5.1/3.0.4/ld.
 > 
 > The machine isn't operated by myself, unfortunately.  I have to wait for a
 > planned downtime tomorrow.  Then, the machine will be patched.
 > 
 > [...]
 > > I've re-bootstrapped GCC 3.0.4 20020129 with no regressions compared to
 > > 3.0.2 20010921, and this version still creates a working CLN 1.1.4 which
 > > passes make check.  I've even tried to drop the Tru64 UNIX V5.1 ld (before
 > > any patches) into the gcc tree as mentioned above and rebuilt CLN, which
 > > keeps working.  This may mean that ld isn't the culprit or the error only
 > > happens when linking libstdc++.
 > 
 > Thanks for this piece of information.  After our last email I had grown
 > suspicious, too, about ld being the only reason for this failure...
 
 Sigh.  Finally they have patched the machine up to ld from patch 358 --
 sorry it took so long.  Unfortunately, the problem does not go away.  I
 have bootstrapped gcc-3.0.3 and compiled CLN from scratch and it still
 complains about multiple symbols and crashes upon execution.
 
 So I have still no idea what is needed for gcc to function properly and,
 hence, cannot provide a proper documentation patch.  I'm afraid, this is
 as good as it gets, unless somebody can come up with an educated guess
 what to try next.
 
 Regards
     -richy.
 -- 
 Richard B. Kreckel
 <Richard.Kreckel@Uni-Mainz.DE>
 <http://wwwthep.physik.uni-mainz.de/~kreckel/>
 
 


             reply	other threads:[~2002-02-18 20:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18 12:56 Richard B. Kreckel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10  5:36 Rainer Orth
2002-05-10  5:27 ro
2002-05-09 10:56 Richard B. Kreckel
2002-04-16 10:56 Rainer Orth
2002-02-25  8:58 Rainer Orth
2002-02-23 14:12 Richard B. Kreckel
2002-02-22 15:46 Rainer Orth
2002-02-22 14:16 Rainer Orth
2002-02-21 16:21 Richard B. Kreckel
2002-02-20  9:36 Richard B. Kreckel
2002-02-19  5:26 Rainer Orth
2002-02-04 11:06 Richard B. Kreckel
2002-02-04 11:06 Rainer Orth
2002-01-30  6:14 ro
2002-01-27  6:26 kreckel

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=20020218205602.27959.qmail@sources.redhat.com \
    --to=kreckel@ginac.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=ro@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).