above all thx for replying, dunno what was it, but i rebuild all in
sequence ad described on http://enlightenment.freedesktop.org/ only with
"-O2 -fomit-frame-pointer", all went smooth but when i tryed to edit an
e_util_eapp_edit (taken from cvs) it segfault with i open a directory
with images files, here is the bt:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 4044)]
0x402bc678 in evas_list_remove_list () from /usr/lib/libevas.so.1
#0 0x402bc678 in evas_list_remove_list () from /usr/lib/libevas.so.1
#1 0x402bc61e in evas_list_remove () from /usr/lib/libevas.so.1
#2 0x402a9700 in evas_object_rectangle_add () from /usr/lib/libevas.so.1
#3 0x402baa49 in evas_render_updates () from /usr/lib/libevas.so.1
#4 0x402babe2 in evas_render () from /usr/lib/libevas.so.1
#5 0x40047864 in ewl_idle_render () from /usr/lib/libewl.so.0
#6 0x40047810 in ewl_idle_render () from /usr/lib/libewl.so.0
#7 0x402816ea in _ecore_idle_enterer_call () from /usr/lib/libecore.so.1
#8 0x40281648 in _ecore_idle_enterer_call () from /usr/lib/libecore.so.1
#9 0x40283aee in _ecore_main_shutdown () from /usr/lib/libecore.so.1
#10 0x4000a269 in fixup () from /lib/ld-linux.so.2
#11 0x4061c469 in __libc_start_main () from /lib/libc.so.6
#12 0x08049781 in ?? ()
note that all modules where compiled with "-O2 -fomit-frame-pointer"
evas was then ricompiled without any CFLAGS setted after this error,
i'll try to recompile eet without any flag.
thx for support :)
ps always cc me :)
Carsten Haitzler (The Rasterman) wrote:
> On Thu, 24 Feb 2005 18:57:05 +0100 Marco Mazzoni <ipermason@...> babbled:
>>Hi, i've got a strange problem with ewl, making it unusable.
>>i've compiled all from cvs, and when i tried to make enlightment start
>>all went fine but the menus are unasable, so i tryed all the test in the
>>libs (evas, etox, and other show something or had an output that seemed
>>to me right, the only one suspicious is "edje_test gentoo.eet images"
>>that showed a white canvas, where gentoo.eet is from the engage package
>>) package and all went fine(according to me anyway) but the ewl showed
>>some mistakes, like the attached picture.
>>i dunno how to solve it, any hint?
> i bet you evas built without eet loader support :) check the configure output :)
> check config.log to see why it decided not to build with eet support.
>>infos: gl from nvidia with last one binary driver
>>CFLAGS=-march=athlon -Os -fomit-frame-pointer
>>ps cc me, i'm not registered with ml.
>>pss great libs, keep up the great work