From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RDzwz-0003Qp-JT for garchives@archives.gentoo.org; Wed, 12 Oct 2011 14:38:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2CD2921C18E; Wed, 12 Oct 2011 14:38:20 +0000 (UTC) Received: from mail-qw0-f53.google.com (mail-qw0-f53.google.com [209.85.216.53]) by pigeon.gentoo.org (Postfix) with ESMTP id C9F8121C113 for ; Wed, 12 Oct 2011 14:37:28 +0000 (UTC) Received: by qafi31 with SMTP id i31so1262367qaf.40 for ; Wed, 12 Oct 2011 07:37:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=IFEdCPLZezL/l3soesIvzGabxUwJzlhL6ifBLhhp7Os=; b=Eh9NgLNyb50mH7qDFkQUyO0gfgKxJV9Bq+ivZ+zG4fsf9TdefmbaUlhDa4Lsqei+FQ EZJ5xEuWLOoIZDEnJvblz9k0IB5ib9HwuwyUuaNHy8E2eP28eeBKiExyjvsLg/keX4S8 dDm8wHSpfLz/Xnh05P4p/x3KDpy1dLzMMttTM= Received: by 10.42.155.133 with SMTP id u5mr35952761icw.8.1318430248065; Wed, 12 Oct 2011 07:37:28 -0700 (PDT) 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.42.179.7 with HTTP; Wed, 12 Oct 2011 07:37:08 -0700 (PDT) In-Reply-To: References: From: James Broadhead Date: Wed, 12 Oct 2011 15:37:08 +0100 Message-ID: Subject: Re: [gentoo-user] gentoo-user@lists.gentoo.org To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: X-Archives-Hash: 6d870dccd7efb62c69f37d90d02cc6d0 On 4 October 2011 13:21, Alex Sla <4k3nd0@googlemail.com> wrote: > Hi Guys, > > i got a problem build gconf. The problem is somehow emake again o.O emake is merely a wrapper around make - that line means that there was a compile failure. Thanks for attaching your build log, but please try searching through it for "Error", and find the actual build error. (hint: line 580 or so). Also: please take more care with Subject lines in emails to the list.