Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: robertl@sco.com
Cc: gdb-patches@cygnus.com
Subject: Re: GDB 4.18 on SVR5: missed it by a hair
Date: Mon, 19 Apr 1999 13:47:00 -0000	[thread overview]
Message-ID: <199904192047.NAA18881@andros.cygnus.com> (raw)
In-Reply-To: <19990415225503.A10488@rjlhome.sco.com>

   Date: Thu, 15 Apr 1999 22:55:03 -0500
   From: Robert Lipe <robertl@sco.com>

   The round of optimizations we performed on configure.host didn't
   make it to configure.tgt.   So SVR5 gets detected as SVR4.0 so it
   gets /proc filesystem handling silently wrong. :-(

Argh!  The change is in the trunk, but I forget to add it to the 4.18
branch also.  Well, there's a third patch for 4.18.1...

								Stan



  reply	other threads:[~1999-04-19 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-15 20:55 Robert Lipe
1999-04-19 13:47 ` Stan Shebs [this message]
     [not found] ` <199904192047.NAA18881.cygnus.patches.gdb@andros.cygnus.com>
1999-04-19 18:13   ` Andrew Cagney
1999-04-19 19:10     ` Andrew Cagney

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=199904192047.NAA18881@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=gdb-patches@cygnus.com \
    --cc=robertl@sco.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