Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: tim@cobaltmicro.com, linux@cthulhu.engr.sgi.com
Subject: Re: Hanging.
Date: Mon, 4 May 1998 21:32:05 +0200	[thread overview]
Message-ID: <19980504213205.32754@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.980504130914.11760G-100000@lager.engsoc.carleton.ca>; from Alex deVries on Mon, May 04, 1998 at 01:14:21PM -0400

On Mon, May 04, 1998 at 01:14:21PM -0400, Alex deVries wrote:

> On Mon, 4 May 1998 ralf@uni-koblenz.de wrote:
> > On Sun, May 03, 1998 at 10:15:27PM -0400, Alex deVries wrote:
> > > Alright. I got it about once an hour today, which is tough to live with.
> > > I think I'll go and compile RPMs on Zach's Qube instead...
> > Cobalt Qube is little endian ...
> 
> I stand corrected, I'd misunderstood.
> 
> There'll be a pretty large problem with Qube users using the version of
> RPM that ships with it, since those think they're 'mips', which is
> actually 'mipseb' now. 
> 
> Anyone know anybody at Cobalt Micro who does their distribution
> development? We need to sort this problem out somehow. Their machines
> should ship with a later release of RPM, and their packages should ship
> as mipsel.

I cc this to Tim.  DaveM is also reading this list, so they'll know.
The problem isn't too bad.  One new rpm binaries have been installed those
will know about mipsel/mipseb.  And we _had_ to break compatibility,
remember the purpose was to make the two flavours and the old ``mips''
flavour different and distinguishable from each other.

If this ends up being a problem one can still add apropriate entries to
/usr/lib/rpmrc or using the --ignore-arch option.

> Oh, and there'll be a huge batch of mipseb binary RPMs ported from the
> contrib directory on ftp.redhat.com.  Details later. 

Cool.

  Ralf

  reply	other threads:[~1998-05-04 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-01 18:20 Hanging Alex deVries
1998-05-01 19:29 ` Hanging William J. Earl
1998-05-01 19:37   ` Hanging Alex deVries
1998-05-01 19:45     ` Hanging William J. Earl
1998-05-02 10:52 ` Hanging ralf
1998-05-03  1:26   ` Hanging Alex deVries
1998-05-03 18:22   ` Hanging Alex deVries
1998-05-03 18:40     ` Hanging ralf
1998-05-04  2:15       ` Hanging Alex deVries
1998-05-04  6:57         ` Hanging ralf
1998-05-04 17:14           ` Hanging Alex deVries
1998-05-04 19:32             ` ralf [this message]
1998-05-04 19:45               ` Hanging 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=19980504213205.32754@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=tim@cobaltmicro.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