public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: linux-gcc@vger.rutgers.edu (linuxgcc)
Cc: egcs@cygnus.com
Subject: A new binutils for linux
Date: Mon, 03 Nov 1997 16:27:00 -0000	[thread overview]
Message-ID: <m0xSUEL-0004ecC@ocean.lucon.org> (raw)

Hi,

I made a new binutils for Linux. It is mainly for non Intel-x86
platforms. It seems to work fine on Linux/alpha.


-- 
H.J. Lu (hjl@gnu.ai.mit.edu)
---
This is the beta release of binutils 2.8.1.0.16 for Linux, which is
based on the binutils 971103 snapshot plus Linux/ARM support. You
also need libc 5.4.36 or above to use the precompiled binaries for
libc 5 or glibc 2.0.4 or above to use the precompiled binaries for
glibc 2.

This release should work on linux/x86 and Linux/alpha. I don't
know if it works on linux/sparc, Linux/MIPS and linux/PPC. I'd like
to hear reports on them.

Please report any bugs related to binutils 2.8.1.0.16 to
hjl@gnu.ai.mit.edu.

Changes from binutils 2.8.1.0.15:

1. Update from the binutils gas-971103.
2. ELF/Alpha seems to work fine, including versioning.
3. ELF/PPC patches from Geoff Keating  <geoffk@ozemail.com.au>.


IMPORTANT:
The .plt format that the Alpha was using was not thread safe.  So I 
changed it.  The new format is *not* binary compatible with the old,
thus you must use glibc 2.0.4 to get an ld.so that can understand it.

Note that the new ld.so knows how to deal with the old .plt format, so
old libraries will still work, but they should be relinked eventually
for performance reasons.

The file list:

1. binutils-2.8.1.0.15-2.8.1.0.16.diff.gz. Patch against the previous
   beta source code.

   ftp://ftp.yggdrasil.com/private/hjl/binutils-2.8.1.0.15-2.8.1.0.16.diff.gz


Thanks.


H.J. Lu
hjl@gnu.ai.mit.edu
11/03/97

                 reply	other threads:[~1997-11-03 16:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m0xSUEL-0004ecC@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=egcs@cygnus.com \
    --cc=linux-gcc@vger.rutgers.edu \
    /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).