From: Alan Modra <alan@SPRI.Levels.UniSA.Edu.Au>
To: David and Jannette Uczen <uczen@mint.net>
Cc: Ian Lance Taylor <ian@zembu.com>,
binutils@sourceware.cygnus.com, linas@linas.org
Subject: Re: IBM S/370 and binutils
Date: Wed, 27 Oct 1999 19:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9910281118520.31971-100000@mullet.itr.unisa.edu.au> (raw)
In-Reply-To: <000901bf20e5$253cbb80$aa81e3d8@duczen--lap.hannaford.com>
On Wed, 27 Oct 1999, David and Jannette Uczen wrote:
> I built binutils-2.9.5.0.14 with target=i370-elf, assembled an empty .s file
> to get an ELF binary. When I used readelf, it said the machine type was
> 0xf00f (unkown).
>
> The source I got is at ftp://ftp.valinux.com/pub/support/hjl/binutils , to
> which I was directed by Linas Vepstas ( http://www.linas.org ) who is working
> on a port of Linux to S/370.
>
> Is this not official? Thanks.
This is H.J. Lu's official release of binutils including the official
Linas Vepstas' IBM370 patches, which don't happen to yet be in the
official GNU binutils sources. :-)
I can understand the confusion from someone exposed to free software
mainly through linux, as most (all?) linux distributions use H.J. Lu's
binutils. Thus H.J.'s binutils are 'official' to most linux users. H.J.
has supported linux with very rapid response to bugs and new feature
requests, while the Cygnus/FSF binutils releases have lagged somewhat.
(CVS development sources are available to everyone though). Part of the
reason for the lag is that the Cygnus/FSF binutils releases need to
support practically every architecture on the planet, while H.J. focuses
on architectures that run linux. Also the FSF is rather strict about such
things as copyright assignment.
Ian, BTW, is the official grand-poobah binutils maintainer.
> -----Original Message-----
> From: Ian Lance Taylor <ian@zembu.com>
> >
> >As far as I know, the GNU binutils do not use that value. The
> >official sources may be found at
> > http://sourceware.cygnus.com/binutils
> >
> >There may be patches out there which use it. If I get those patches,
> >I will bear your comments in mind.
next prev parent reply other threads:[~1999-10-27 19:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 18:40 David and Jannette Uczen
1999-10-27 19:19 ` Alan Modra [this message]
1999-10-29 9:12 ` linas
1999-10-29 9:28 ` H.J. Lu
1999-10-29 9:37 ` Ian Lance Taylor
1999-10-29 10:53 ` linas
1999-10-29 9:14 ` linas
1999-10-29 9:22 ` linas
1999-10-29 9:36 ` Ian Lance Taylor
1999-10-29 9:57 ` H.J. Lu
1999-10-29 10:05 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
1999-10-30 19:32 David and Jannette Uczen
1999-10-30 10:01 David and Jannette Uczen
1999-10-30 10:57 ` linas
1999-10-29 18:37 David and Jannette Uczen
1999-10-29 18:27 David and Jannette Uczen
1999-10-30 11:45 ` linas
1999-10-29 18:27 David and Jannette Uczen
1999-10-27 16:24 David and Jannette Uczen
1999-10-27 16:40 ` Ian Lance Taylor
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=Pine.LNX.4.10.9910281118520.31971-100000@mullet.itr.unisa.edu.au \
--to=alan@spri.levels.unisa.edu.au \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.com \
--cc=linas@linas.org \
--cc=uczen@mint.net \
/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).