Try and make things more organized by creating a project to add in issues, this makes it easier to search for just FreeBSD issues. Also this opens doors to other users who enjoy using FreeBSD want to make E better.
Mon, Jun 15
Fri, Jun 12
Thank you @stefan_schmidt please go ahead and push this way thank you for your time and checking out :-)
@cederom if you want proper credit for this patch I would need a git format patch.
May 29 2020
Back port this?
This is fixed by
May 28 2020
Seems to be fixed by Raster's commit: 2bd98e830f51fa985cbc3a0ab2db4e759ec75354
May 27 2020
mhm, give me time until tomorrow. I think eina should drag in -lm for everyone that uses it. as eina includes math.h. Will check and investigate tomorrow.
diff --git a/src/lib/eo/meson.build b/src/lib/eo/meson.build index 9cd3377..3a4e1e9 100644 --- a/src/lib/eo/meson.build +++ b/src/lib/eo/meson.build @@ -2,6 +2,10 @@ eo_deps =  eo_pub_deps = [eina] eo_ext_deps = [valgrind, dl, execinfo]
May 25 2020
fixed it... use current sched when SCHED_BATCH and IDLE not available.
I think, it is safe to
May 17 2020
May 15 2020
Thank you @Peter2121.. I had to modify one header that was linux specific in order to make VNC server work:
It seems that has_header meson function is not recursive.
I could reproduce your problem creating symlinks of epoll.h in /usr/local/include/sys or in /usr/include/sys
I don't know why do you have such links (or strange CFLAGS=I/usr/local/include/libepoll-shim) but anyway it is not a standard situation. So I think that libepoll-shim package installed would not prevent correct building of EFL without epoll.
I cannot reproduce your problem on my test PC under FreeBSD 12.1.
I have libepoll-shim package installed, but during the configuration of EFL meson does not detect sys/epoll.h header. I have it installed in /usr/local/include/libepoll-shim/sys/epoll.h and I have CFLAGS=-I/usr/local/include exported, but meson does not detect it. Don't you have a symlink of this file in /usr/include for any reason?
I can confirm that this is the EFL build time configuration issue. Older EFL build works fine with Terminology 1.7.0. I will looks into that epoll stuff in a free moment. Thank you!! :-)
May 14 2020
Thank you for your feedback that it works for you, this is valuable input.
Try to build EFL and Terminology in jail with the strict minimum of other software installed. Terminology and Enlightenment from Git work fine here with EFL 1.24 on FreeBSD 11.3.
Your terminology 1.6.0 is probably linked with an other version of efl, one that was compiled when epoll-shim wasn't installed.
You cannot build a port package with all this other software installed.
Did you build EFL with those flags?
The problem with Terminology 1.7.0 is not fixed, exactly the same setup and 1.6.0 works fine, I cannot remove libepoll-shim from system because other applications depend on it. Will report a working solution if I find one. Thanks for your quick response :-)
meson build -Dsystemd=false -Deeze=false
Well, it looks like I am updating the port, because no one did that so far ;-)
Please advise the FreeBSD port maintainers not to build with wayland support . It does not work, it merely builds.
Follow that guide - remove the libepoll-shim package as suggested by @arrowdodger
These goes the port updates tickets and whole ports sources / patches are there too:
That sounds about right @arrowdodger
@cederom Are you building in unclean environment? It might be that build system picks stuff from libepoll-shim FreeBSD package.
I'm runnning E 24.0 and EFL 1.24 and Terminology 1.7.0 on FreeBSD 12.1 and OpenBSD 6.7-beta
Hey @netstar :-) Which version of Terminology on which E and EFL?
I'm running terminology fine here on OpenBSD and FreeBSD.
Can you show the build options for EFL? There should be no reference to epoll
There are some changes in src/bin/termpty.c but I don't see why it should fail.
Sure thing, I am porting EFL+E to FreeBSD so no problem with building and patching :-)
Would it be possible for you to compile terminology 1.6.0 with the same efl version?
Hello @billiob and thank you for quick response :-)
If you create a new terminal from the menu, is it better?
What if you focus/unfocus the window?