Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: Tim Hockin <thockin@cobaltnet.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: an ld problem?
Date: Thu, 29 Jul 1999 15:32:23 +0200	[thread overview]
Message-ID: <19990729153223.D4730@uni-koblenz.de> (raw)
In-Reply-To: <379FBBFE.FB8C1734@cobaltnet.com>; from Tim Hockin on Wed, Jul 28, 1999 at 07:27:10PM -0700

On Wed, Jul 28, 1999 at 07:27:10PM -0700, Tim Hockin wrote:

> where it aborts.  I am a bit bewildered.  Anyone have any ideas to
> offer?  Help?

I cheated; we currently ship only with a static libstdc++.  We've got
a fix for one of the many libbfd coredump bugs in elf32-mips.c in
our patchset of ftp.linux.sgi.com.  I think it won't cure this
particular case, however.

  Ralf

  reply	other threads:[~1999-07-29 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-29  2:27 an ld problem? Tim Hockin
1999-07-29 13:32 ` Ralf Baechle [this message]
     [not found] ` <19990729153427.E4730@uni-koblenz.de>
1999-07-30  5:28   ` an ld problem? - possibly fixed Tim Hockin
1999-07-30 21:01     ` Ralf Baechle

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=19990729153223.D4730@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=thockin@cobaltnet.com \
    /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