From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D3FE0138010 for ; Thu, 23 Aug 2012 00:26:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9119121C010; Thu, 23 Aug 2012 00:26:18 +0000 (UTC) Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 74B7BE0793 for ; Thu, 23 Aug 2012 00:24:12 +0000 (UTC) Received: by vbbfc26 with SMTP id fc26so220996vbb.40 for ; Wed, 22 Aug 2012 17:24:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=QWeTMqYjAq0gwYaFVyY4lv6FrbtInEk9ohbu9YoZSoc=; b=aVxS3Xf5oJ3EfJXGLxEx4nXbfQpXFvehoGSjkmBSe7uxLhdkW0XdlI0PKtgNp+ecqf 6LKRQJq53s+3K7y8JYZZ20lArRjhkIPeLZ6tAnMCpEnHIgF93i8KD68TrpHW+1lFKkMv JcW5lqpRubhnUu7zuS5OdBWFG2+VI2N1DT0s8Li5jkoY5TqrvsWWmKPKoYCaPG4fkcEp b04ONSAdu7CaRu9GOGUR3j5CCvaLCG1+2vR8Zknojb5+7LfCN479ZF2YVA6uUGw4pLuf wysH6yF4d3MdVex6npF+IIAxO9Ts+KSETWmNiH+XwLMCGC2CeJHqwmwzPAQdnXawZ95Y 87uw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.52.156.46 with SMTP id wb14mr15563373vdb.30.1345681451725; Wed, 22 Aug 2012 17:24:11 -0700 (PDT) Received: by 10.58.102.228 with HTTP; Wed, 22 Aug 2012 17:24:11 -0700 (PDT) In-Reply-To: References: <5035439E.6090707@binarywings.net> Date: Thu, 23 Aug 2012 01:24:11 +0100 Message-ID: Subject: Re: [gentoo-user] xz memory hungry? From: Jorge Almeida To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 9e7e3499-89f0-4f06-bb31-827cf62e87dc X-Archives-Hash: 53779798c63e14d86118387817ba61ed On Wed, Aug 22, 2012 at 11:19 PM, Jorge Almeida wrote: > On Wed, Aug 22, 2012 at 10:42 PM, Michael Mol wrote: >> On Wed, Aug 22, 2012 at 5:16 PM, Jorge Almeida wrote: >> >> My bet is that it's an incompatibility between the Arch kernel and the >> version of glibc in the chroot. >> > Well, the kernel in Arch is 3.4.4 and glibc is 2.15. In the chroot, the glibc > is 2.14. Maybe I should update system et al. But then emerge system > asks for m4 (but not for glibc, which I find surprising). > Well, I found the problem: ulimit problem. Not the first time this crap bites me, but I always forget. I just wish this was better documented, somewhere. Sorry for the noise, and thanks to everyone. Jorge Almeida