From owner-freebsd-ports@FreeBSD.ORG Mon Dec 24 10:37:48 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E3246B for ; Mon, 24 Dec 2012 10:37:48 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 43F8D8FC0A for ; Mon, 24 Dec 2012 10:37:47 +0000 (UTC) Received: from mobileKamikaze.norad (dslb-094-219-054-243.pools.arcor-ip.net [94.219.54.243]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 80F0286141; Mon, 24 Dec 2012 11:37:44 +0100 (CET) Message-ID: <50D83078.2020203@bsdforen.de> Date: Mon, 24 Dec 2012 11:37:44 +0100 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Grzegorz Blach Subject: Re: E17 won't start References: <20121223201822.e7f2721dff31029a87d5c551@alkumuna.eu> <50D7BB9A.5000005@bsdforen.de> <50D7BDCF.4040401@bsdforen.de> <50D7C1F3.3030809@bsdforen.de> <1356343067.12879.4.camel@silver.nine> In-Reply-To: <1356343067.12879.4.camel@silver.nine> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 10:37:48 -0000 On 24/12/2012 10:57, Grzegorz Blach wrote: > On Mon, 2012-12-24 at 03:46 +0100, Dominic Fandrey wrote: >> On 24/12/2012 03:28, Dominic Fandrey wrote: >>> On 24/12/2012 03:19, Dominic Fandrey wrote: >>>> >>>> On 23/12/2012 20:18, Matthieu Volat wrote: >>>>> I've been unable to start an enlightenment session after the recent upgrade to the release. >>>> >>> >> >> I managed to fix it by building all evas-* packages with base gcc! >> > > I rebuilt all EFL and E17 with clang and I get black screen issue, > but E17 start to work after I rebuilt only evas-core with gcc. > Can anyone confirm that, building evas-core with gcc fixes this issue. I rebuilt everything with clang except for evas-core. It still works, so yes rebuilding evas-core with gcc is the fix/workaround. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?