Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: miguel@nuclecu.unam.mx (Miguel de Icaza)
Cc: adevries@engsoc.carleton.ca, linux@cthulhu.engr.sgi.com
Subject: Re: BlueBelt Linux for SGI
Date: Mon, 12 Jan 1998 19:52:15 +0000 (GMT)	[thread overview]
Message-ID: <m0xrpuB-0005FsC@lightning.swansea.linux.org.uk> (raw)
In-Reply-To: <199801121847.MAA01817@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Jan 12, 98 12:47:58 pm

> > A lot of those failures are simply because of the order I built
> > everything in;  eg. I built gpm-devel late in the game, so things like mc
> > didn't compile. 
> 
> Oh, but this is such an important tool.  
> 
> We need mc ;-)

I've filled in a pile of the obvious blanks and a few spec file fixes
- ftp.uk.linux.org as usual

WARNING: multiple messages have this Message-ID (diff)
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: adevries@engsoc.carleton.ca, linux@cthulhu.engr.sgi.com
Subject: Re: BlueBelt Linux for SGI
Date: Mon, 12 Jan 1998 19:52:15 +0000 (GMT)	[thread overview]
Message-ID: <m0xrpuB-0005FsC@lightning.swansea.linux.org.uk> (raw)
Message-ID: <19980112195215.gev2L5XwGIjdeILjxwRCuUCIpVpYmRoz9Zm5hBvXPCU@z> (raw)
In-Reply-To: <199801121847.MAA01817@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Jan 12, 98 12:47:58 pm

> > A lot of those failures are simply because of the order I built
> > everything in;  eg. I built gpm-devel late in the game, so things like mc
> > didn't compile. 
> 
> Oh, but this is such an important tool.  
> 
> We need mc ;-)

I've filled in a pile of the obvious blanks and a few spec file fixes
- ftp.uk.linux.org as usual

  parent reply	other threads:[~1998-01-12 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-12  2:47 BlueBelt Linux for SGI Alex deVries
1998-01-12 16:56 ` ralf
1998-01-12 18:47 ` Miguel de Icaza
1998-01-12 19:33   ` Alex deVries
1998-01-12 19:52   ` Alan Cox [this message]
1998-01-12 19:52     ` Alan Cox

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=m0xrpuB-0005FsC@lightning.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=miguel@nuclecu.unam.mx \
    /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