Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Update ...
Date: Thu, 4 Dec 1997 04:05:35 +0100	[thread overview]
Message-ID: <19971204040535.06128@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.971203210446.3395A-100000@lager.engsoc.carleton.ca>; from Alex deVries on Wed, Dec 03, 1997 at 09:36:12PM -0500

On Wed, Dec 03, 1997 at 09:36:12PM -0500, Alex deVries wrote:

> I'm really, really stuck.  I'd love to help build packages, but I can't
> because my libc is old and out of date.
> 
> Great, I thought, I'll just cross compile my libc.  Except I'm back to
> where I was in August.  I can't for the life of me cross compile anything,
> especially the kernel.  I know I'm not using the correct gcc. I don't know
> where the correct patches are. And I'm frustrated. And I know that libc is
> the only thing I'm missing.

Ok ...  I'm brewing crosscompiler rpms ...

> Can someone _please_ break my cycle by uploading their functional libc?
> Please? If I get it, and can become a productive member of society again.

Hold your breath ;-)

  Ralf (Whipping his Indy to compile faster ...)

  reply	other threads:[~1997-12-04  3:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-04  1:08 Update ralf
1997-12-04  2:36 ` Update Alex deVries
1997-12-04  3:05   ` ralf [this message]
1997-12-04  3:37     ` Update Alex deVries
1997-12-04  4:27       ` Update ralf
1997-12-04  4:33       ` Update ralf
1997-12-04 14:19         ` Update Alan Cox
1997-12-04 14:09   ` Update Alan Cox
1997-12-04 14:09     ` Update Alan Cox
1997-12-04 22:18     ` Update ralf
  -- strict thread matches above, loose matches on Subject: below --
1997-12-05 17:07 Update ralf

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=19971204040535.06128@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