Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Randolph Chung" <randolph@tausq.org>
To: "Paul J.Y. Lahaie" <pjlahaie@linuxcare.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Weird compile problems
Date: Wed, 24 Jan 2001 22:58:35 -0700	[thread overview]
Message-ID: <20010124225835.Q4546@tausq.org> (raw)
In-Reply-To: <20010124162813.G19066@achilles.net>; from pjlahaie@linuxcare.com on Wed, Jan 24, 2001 at 04:28:13PM -0500

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

> I'm in the process of trying to get a working apt (still) and I'm getting
> the following with the latest kernel (updated this morning) and the
> toolchain from nfsroot-20010118.  The system is a C360 with 256MB of RAM.

FWIW I didn't run into this problem when I tried to compile apt using
the same nfsroot and a kernel that is a few days old (Jan20). I get
almost all the way through the end of the build. one of the files take a
lot of memory to build and fails on my gecko, but i've gotten it to work
before so i'm pretty sure it'll work if i increase my swap. i'll try to
give this a try this weekend.

randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-01-25  5:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24 21:28 [parisc-linux] Weird compile problems Paul J.Y. Lahaie
2001-01-25  5:58 ` Randolph Chung [this message]
     [not found] <20010130154256.D6704@achilles.net>
2001-01-30 23:25 ` Alan Modra
2001-01-30 23:36   ` Matt Taggart
2001-01-30 23:45     ` Alan Modra
2001-01-31  1:01   ` Alan Modra
2001-01-31  7:07     ` Alan Modra
2001-02-01  3:59       ` Alan Modra

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=20010124225835.Q4546@tausq.org \
    --to=randolph@tausq.org \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=pjlahaie@linuxcare.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