Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Dec 2012 10:57:47 +0100
From:      Grzegorz Blach <magik@roorback.net>
To:        freebsd-ports@freebsd.org
Subject:   Re: E17 won't start
Message-ID:  <1356343067.12879.4.camel@silver.nine>
In-Reply-To: <50D7C1F3.3030809@bsdforen.de>
References:  <20121223201822.e7f2721dff31029a87d5c551@alkumuna.eu> <50D7BB9A.5000005@bsdforen.de> <50D7BDCF.4040401@bsdforen.de> <50D7C1F3.3030809@bsdforen.de>

next in thread | previous in thread | raw e-mail | index | archive | help
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 have the same issue.
> >>
> >>> I just have a black screen with the mouse (that can move) and nothing else. There is nothing that can help in ~/.xession-errors...
> >>
> >> Well it's noteworthy that after the first ESTART: SLEEP message I've
> >> got a line that says "PAUSE !". As far as I can figure this is unusual.
> >>
> >> If there's anything /unusual/ in my install, it's that all ports that
> >> can be built witch clang, were built with clang.
> > 
> > I just ran it in gdb. But gdb reports a series of signals:
> > SIGTRAP
> > SIGTRAP
> > SIGTTIN
> > SIGTRAP
> > Now, finally the startup procedures are executed until:
> > ESTART: 0.34318 [0.00001] - Manage all windows
> > ESTART: 0.36315 [0.01997] - MAIN LOOP AT LAST
> > ESTART: 0.64266 [0.27951] - SLEEP
> > 
> > at which point gdb catches a SIGSEV!
> > 
> > If I continue from here I end up with the single "PAUSE !" line and
> > nothing at all happens from here on.
> > 
> 
> 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.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1356343067.12879.4.camel>