Summary: | [PATCH] update x11-toolkits/elementary | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | FreeBSD Ports <cpets> | ||||||
Component: | Individual Port(s) | Assignee: | freebsd-enlightenment (Nobody) <enlightenment> | ||||||
Status: | Closed Overcome By Events | ||||||||
Severity: | Affects Only Me | CC: | freebsd, gblach | ||||||
Priority: | --- | Keywords: | patch | ||||||
Version: | Latest | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Description
FreeBSD Ports
2015-06-12 20:02:39 UTC
Maintainer informed via mail (In reply to FreeBSD Ports from comment #0) You forgot to attach patch. I don't have one yet as build fails: http://grid.bsdjunk.com/data/FreeBSD10AMD64-cpet/2015-06-12_18h56m20s/logs/errors/elementary-1.14.1.log I am trying to see why. After that file edje_cc stays in a uwait state 48635 root 2 20 0 174M 16396K uwait 2 0:00 0.00% edje_cc 80665 root 2 52 0 174M 16392K uwait 0 0:00 0.00% edje_cc And then requires a manual ctrl-c and manual killing of procs. Please see note from bug 200817 an alpha version of the port update can be found here: http://fossil.bsdjunk.com/enlightenment/dir?ci=4a389d64e7460120&name=EPorts/x11-toolkits/elementary if anyone wants to help diagnose this error. doing a gdb it seems to have some thread issue with libeiena causing edje_cc to go into a loop. (gdb) bt #0 0x0000000801cab8cc in __error () from /lib/libthr.so.3 #1 0x0000000801ca9d8e in _pthread_cond_wait () from /lib/libthr.so.3 #2 0x0000000800fde7ac in evas_thread_queue_flush () from /usr/local/lib/libevas.so.1 #3 0x0000000801518962 in eina_thread_create () from /usr/local/lib/libeina.so.1 #4 0x0000000801ca04f5 in pthread_create () from /lib/libthr.so.3 #5 0x0000000000000000 in ?? () (gdb) I will recompile with debugging and see what I can dig up. Created attachment 159493 [details]
patch file
Update this to the latest working versiosn of 1.13.3 and await release of 1.15.0
Created attachment 159494 [details]
build log
This is a simple update, I noticed that 1.13.3 was release and decided to update the PR instead of submitting new ones, I am unsure if that's the correct approach but it saves possible confusing on a new/old PR. If this is not the way you may ping me by email :) This may be closed out as it was updated to 1.15.0 Port was upgraded to 1.15.0 |