From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: gcc -shared ... -lc ?
Date: Tue, 6 Jan 1998 16:21:06 +0100 [thread overview]
Message-ID: <19980106162106.28163@alpha.franken.de> (raw)
In-Reply-To: <m0xpMZT-0005FsC@lightning.swansea.linux.org.uk>; from Alan Cox on Tue, Jan 06, 1998 at 12:08:38AM +0000
On Tue, Jan 06, 1998 at 12:08:38AM +0000, Alan Cox wrote:
> > > This is a binutils 2.7 bug. Upgrading to 2.8.1 solves the problem.
> >
> > this is with binutils-2.8.1
>
> Oh good its not me seeing things. Ralf - could there be two sets of your
> binutils-2.8.1 one working one not and could you maybe post MD5 hashes
> of your binaries you know work ?
I'm using the little endian rpm from ftp.linux.sgi.com. Here is the md5sum:
bce052ce002cbe434133cecf2c4a4f10 binutils-2.8.1-1.mips.rpm
and:
Linux mips.franken.de 2.1.72 #140 Sat Jan 3 23:43:04 MET 1998 mips
[root@mips /root]# ld --version
GNU ld 2.8.1
Copyright 1997 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
Supported emulations:
elf32lmip
elf32bmip
mipslit
mipsbig
I'm sure the binutils 2.7, I've used before, didn't have the bug. But
I wanted to make the redhat-5.0 rpms with the newer binutils.
Thomas.
--
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
[Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]
next prev parent reply other threads:[~1998-01-06 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-05 17:45 gcc -shared ... -lc ? Thomas Bogendoerfer
1998-01-05 18:10 ` Timothy Stonis
1998-01-05 21:09 ` ralf
1998-01-05 23:16 ` Thomas Bogendoerfer
1998-01-06 0:08 ` Alan Cox
1998-01-06 0:08 ` Alan Cox
1998-01-06 5:31 ` ralf
1998-01-06 15:21 ` Thomas Bogendoerfer [this message]
1998-01-06 20:11 ` Thomas Bogendoerfer
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=19980106162106.28163@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.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