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 5E461138010 for ; Thu, 23 Aug 2012 00:59:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CA371E064E; Thu, 23 Aug 2012 00:59:02 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id A7F44E068C for ; Thu, 23 Aug 2012 00:56:47 +0000 (UTC) Received: by bkwj4 with SMTP id j4so48902bkw.40 for ; Wed, 22 Aug 2012 17:56:46 -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=n1IACsj24qfT8CpW+cHxuPxmFr0EY1dzQlyr7Bkft/Y=; b=pezn3mcCUP4OWb/ghD7kxYuk5Y/qqtMYN/n1/9BbKyAzK95Ww8vnP3p1oIIriegDFS TvgRSxuTcrjjhDiq93JFbfiZzJbdIsq75Y7cNp1FFZvaZKKWMH8Ro5rBMdUX1RLdAvwT PnsGPi2b8FAUO2AfFnQNyk9BIP4Lw+uOoru0kAqsb/m2O2wZLBdLRJ6IZvv67t/UFvJp lmJTQpJevmysHXxEgTFuOYIKkqtSau32/6Tz8SoQy7DDWeM8tSdBMXsEsm5+PdQwpfzo dslwKDJRjT2wsOC1D7BtSxyfSPW86tCiHO2sT9OB2iT/uzHVz7FN9LRmtztID/zTevUe 4Y9g== 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.204.148.78 with SMTP id o14mr7033978bkv.38.1345683406715; Wed, 22 Aug 2012 17:56:46 -0700 (PDT) Received: by 10.205.25.8 with HTTP; Wed, 22 Aug 2012 17:56:46 -0700 (PDT) In-Reply-To: References: <5035439E.6090707@binarywings.net> Date: Wed, 22 Aug 2012 20:56:46 -0400 Message-ID: Subject: Re: [gentoo-user] xz memory hungry? From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: d3f6e0e8-88f4-4270-aeef-ce6c1f143e81 X-Archives-Hash: c4312c3ebcd2b493e575e746668577c7 On Wed, Aug 22, 2012 at 8:24 PM, Jorge Almeida wrote: > 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. Hey, I learned something today. No complaints here. :) -- :wq