Okay Al Poole, netstar, committed a fix to Ephoto that involved changing the order of including config.h ... says that made it work. So Ephoto should be good. I imagine Terminology needs the same.
On Mon, Dec 18, 2017 at 1:05 PM Carsten Haitzler <ras...@rasterman.com> wrote: > On Mon, 18 Dec 2017 13:27:21 +0100 Quelrond <quelr...@gmail.com> said: > > > Hello, > > > > Dear developers, please, test your builds on FreeBSD. > > > > Recently checked - neither Terminology nor Ephoto git versions cannot be > > built... > > > > Enlightenment from git - OK. > > it'd be great if freebsd were not broken. > gcc: doesn't work (libstdc++ thread at exit symbol issues). > clang: just bizarre. errors like: > > /usr/local/include/eina-1/eina/eina_inline_lock_posix.x:418:25: error: > use > of undeclared identifier 'ETIMEDOUT' > > but... > > ... > #ifdef EINA_HAVE_POSIX_SPINLOCK > # include <sched.h> > #endif > > #include <errno.h> > #ifndef __USE_UNIX98 > # define __USE_UNIX98 > ... > > there's the errno.h include and: > > @ 3:36AM /usr/local/include > grep ETIMEDOUT /usr/include/errno.h > #define ETIMEDOUT 60 /* Operation timed out */ > > it's there. only #ifdef there is the complete header protection ... > > my point here is... just simple stuff seems broken on freebsd. like gcc not > working. clang somehow deciding to ignore the default system headers and > do some > other magic of its own (or some other header magic i have yet to track down > where the obvious proper headers are not the ones being used)... > > stuff like: > > ../src/bin/tyls.c:58:14: warning: implicitly declaring library function > 'snprintf' with type 'int (char *, unsigned long, const char > *, ...)' [-Wimplicit-function-declaration] > snprintf(buf, bufsz, "%4lld", size); > > and yet... > > #include <stdio.h> > > is there ... :/ > > FYI the compile command is: > > clang -Isrc/bin/tyls@exe -Isrc/bin -I../src/bin -I. -I../ > -I/usr/local/include/efl-1 -I/usr/local/include/edje-1 > -I/usr/local/include/ecore-audio-1 -I/usr/local/include/emile-1 > -I/usr/local/include/eo-1 -I/usr/local/include/eina-1 > -I/usr/local/include/eina-1/eina -I/usr/local/include > -I/usr/local/include/eet-1 -I/usr/local/include/ecore-1 > -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include > -I/usr/local/include/eio-1 -I/usr/local/include/efreet-1 > -I/usr/local/include/ecore-ipc-1 -I/usr/local/include/ecore-con-1 > -I/usr/local/include/ecore-file-1 -I/usr/local/include/embryo-1 > -I/usr/local/include/ecore-imf-evas-1 -I/usr/local/include/evas-1 > -I/usr/local/include/evas-1/canvas -I/usr/local/include/libpng16 > -I/usr/local/include/harfbuzz -I/usr/local/include/fribidi > -I/usr/local/include/freetype2 -I/usr/local/include/luajit-2.0 > -I/usr/local/include/ecore-imf-1 -I/usr/local/include/ecore-input-1 > -I/usr/local/include/ecore-evas-1 -I/usr/local/include/ecore-input-evas-1 > -I/usr/local/include/elementary-1 -I/usr/local/include/ecore-x-1 > -I/usr/local/include/elocation-1 -I/usr/local/include/eldbus-1 > -I/usr/local/include/dbus-1.0 -I/usr/local/lib/dbus-1.0/include > -I/usr/local/include/emotion-1 -I/usr/local/include/ethumb-client-1 > -I/usr/local/include/ethumb-1 -L/usr/local/lib -Xclang -fcolor-diagnostics > -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g > -DHAVE_CONFIG_H=1 -O3 -ffast-math -ftree-vectorize -march=native > -fvisibility=hidden -g -W -Wall -Wextra -pthread -MMD -MQ > 'src/bin/tyls@exe/tyls.c.o' -MF 'src/bin/tyls@exe/tyls.c.o.d' -o > 'src/bin/tyls@exe/tyls.c.o' -c ../src/bin/tyls.c > > and the errno.h's on fbsd: > > /usr/src/contrib/libstdc++/include/c_compatibility/errno.h > /usr/src/contrib/libc++/include/errno.h > /usr/src/sys/compat/linuxkpi/common/include/linux/errno.h > /usr/src/sys/xen/interface/errno.h > /usr/src/sys/sys/errno.h > /usr/include/sys/errno.h > /usr/include/c++/v1/tr1/errno.h > /usr/include/c++/v1/errno.h > /usr/include/errno.h > > the errno.h and sys/errno.h ones define the above rtimednout define. the > c++ > ones shouldnt be involved. ... > > also for a long time freebsd's pkg was broken for me due to whatever CDN > freebsd's pkg servers were using was basically failing to connect/work from > korea. > > i'm not a bsd user. i'll maybe bother with the freebsd vm i have. but if i > have > to fight it on basic stuff like above which just makes no sense... what > should > i do? up at almost 4am trying to get freebsd compiles to work at all... > and it > simply isn't being "logical". :( > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > Carsten Haitzler - ras...@rasterman.com > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
