On Thu, Sep 05, 2013 at 06:22:06PM +0200, Grzegorz Blach wrote: > On 09/05/13 18:16, Baptiste Daroussin wrote: > > On Thu, Sep 05, 2013 at 05:49:51PM +0200, Grzegorz Blach wrote: > >> On 09/05/13 17:42, Matthieu Volat wrote: > >>> Hi e17 users, > >>> > >>> I can't get e17 to start a session from xdm, and it's quite unreliable > >>> from startx too... There's no big error message in .xsession, it just > >>> seems to hang after : > >>> RUN INIT: /usr/local/lib/enlightenment/utils/enlightenment_init > >>> '/usr/local/share/enlightenment/data/themes/default.edj' '0' > >>> 'Enlightenment' '0.17.4' > >>> > >>> There's no problem if I rollback to 0.17.3... I'm in 9.2-RC3 amd64 with > >>> clang set as port compiler... (tried to rebuild just enlightenment with > >>> gcc with no avail). Does anybody has found this problem and maybe a > >>> solution? > >>> > >> > >> Hi Matthieu, > >> > >> You need to rebuild graphics/evas-core using gcc, this should resolve > >> your problem. > > > > That means I removed USE_GCC=any by mistake, this is weird, as I am able to > > run > > e17 on head using clang (meaning clang33)? > > > > did I miss something? > > > > I don't tried clang33 yet, but I'm sure that building evas-core using > clang32 at last on amd64 make e17 unusable. >
I'll readd USE_GCC=any for now then and see later how to better handle it. regards, Bapt
pgpU_41hhvBue.pgp
Description: PGP signature