public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: matthew green <mrg@cygnus.com>
To: Mike Pelley <mike@solidum.com>
Cc: binutils@sources.redhat.com
Subject: re: NetBSD and 2.11.2
Date: Mon, 27 Aug 2001 08:38:00 -0000	[thread overview]
Message-ID: <23027.998926629@cygnus.com> (raw)
In-Reply-To: <3B8A5D09.A977C0FA@solidum.com>

   I'm attempting to use binutils 2.11.2 natively for both NetBSD 1.4.3 and
   1.5.1.  Binutils compiles ok, but when I try to use it to compile gcc
   (2.95.1 or 2.95.3), I get errors as follows:


support for 1.5 is not present in GCC 2.95* or binutils 2.11.2 and
earlier (though is in binutils 2.11.3 and beyond, and GCC -current
from about a month ago.)  the 1.4 machine should work though.  i'll
see if i can test this myself.


.mrg.

      reply	other threads:[~2001-08-27  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27  7:45 Mike Pelley
2001-08-27  8:38 ` matthew green [this message]

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=23027.998926629@cygnus.com \
    --to=mrg@cygnus.com \
    --cc=binutils@sources.redhat.com \
    --cc=mike@solidum.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).