Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: gcc RPM missing crtbegin.o
Date: Sun, 26 Apr 1998 03:48:39 +0200	[thread overview]
Message-ID: <19980426034839.39956@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.980425195431.4684A-100000@lager.engsoc.carleton.ca>; from Alex deVries on Sat, Apr 25, 1998 at 08:01:33PM -0400

On Sat, Apr 25, 1998 at 08:01:33PM -0400, Alex deVries wrote:

> Hm. I've re-installed gcc from the RPM that's in the mustang directory on
> linus (2.7.2-1, build date is Dec 4 03:23:00).  "Yipee", says I, "I can
> now become an productive member of society". 
> 
> But, the gcc RPM doesn't have crtbegin.o, which is a bit odd.  It's not
> the end of the world, I snarfed it from the cross compiling RPM for i386.
> Was there a reason it wasn't included? 

It's spelled ``bug''.  This has been reported before and I'm shure I've
uploaded the apropriate fixes in form of new patch sets, source and binary
rpms.

>Clickety<

[ralf@lappi ralf]$ ssh -C -l ralf linus.linux.sgi.com
Enter passphrase for RSA key 'root@rio': 
Last login: Thu Apr 23 08:28:04 1998 from vulcan.ko.ivm.net
Welcome to linus.linux.sgi.com !

This machine serves as:
        o A  repository for SGI/Linux source code          /src/cvs
        o A  web server for SGI/Linux (www.linux.sgi.com)  /src/web
        o An ftp server for SGI/Linux (ftp.linux.sgi.com)  /src/ftp

Please, use the /src and /work directories for storing big stuff
Home dirs are on / and it fills quite fast.

Shell access to core developers and contributors via ssh only.
Happy hacking!

                        ariel@sgi.com   Jul, 1997
ralf@linus:ralf# locate gcc-2.7.2 | fgrep -e -3 | fgrep .rpm
/src/ftp/pub/redhat/redhat-5.0/RPMS/mips/gcc-2.7.2-3.mips.rpm
/src/ftp/pub/redhat/redhat-5.0/RPMS/mipsel/gcc-2.7.2-3.mipsel.rpm
/src/ftp/pub/redhat/redhat-5.0/SRPMS/gcc-2.7.2-3.src.rpm

ralf@linus:ralf#

Easy, isn't it?

> I'm having some really wonky behaviour on my filesystem with .72; files
> are disappearing off my filesystem left right and center.  For instance,
> crtbegin.o has been on the system since I first got the machine last fall.
> e2fsck's always come back clean. Now that I got my compiler working, I'm
> running .1.91 again.

I've fixed *shitloads* of bugs since .72, not too mention a dramatic increase
in performance.  You're right, filesystems on Indys (not other MIPS boxes)
had the problem of a certain ``volatilibility'', but that's gone for me.
If somebody still sees fs corruption on Indys running 2.1.91, please report.

> I also upgraded to the glibc 2.0.7 RPMs, which seems to have messed up
> tcsh.  It'd be real nice to get gdb and/or strace working to debug things
> like this.

Strace is working.  See the CVS.

There is no glibc 2.0.7.

  Ralf

  reply	other threads:[~1998-04-26  1:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-26  0:01 gcc RPM missing crtbegin.o Alex deVries
1998-04-26  1:48 ` ralf [this message]
1998-04-26  3:00   ` Alex deVries
1998-04-26  3:39     ` ralf
1998-04-26  4:34       ` Alex deVries
1998-04-26 11:14         ` ralf
1998-04-26 12:09         ` ralf
1998-04-26 21:52           ` Various kernel issues Alex deVries

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=19980426034839.39956@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=adevries@engsoc.carleton.ca \
    --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