'ac_add_options --enable-x32' does not seem to make any difference, same error, same place.
I also follow the sugestion by stevepusser to try the debian way, again, same error, same place:
Code: Select all
In file included from /usr/include/x86_64-linux-gnux32/sys/sysctl.h:63:0,
from ../../dist/system_wrappers/sys/sysctl.h:3,
from /opt/BUILD/debian/palemoon-27.1.1~repack/ipc/chromium/src/third_party/libevent/./arc4random.c:62,
from /opt/BUILD/debian/palemoon-27.1.1~repack/ipc/chromium/src/third_party/libevent/evutil_rand.c:104:
/usr/include/x86_64-linux-gnux32/bits/sysctl.h:19:3: error: #error "sysctl system call is unsupported in x32 kernel"
# error "sysctl system call is unsupported in x32 kernel"
^
/opt/BUILD/debian/palemoon-27.1.1~repack/config/rules.mk:904: recipe for target 'evutil_rand.o' failed
make[7]: *** [evutil_rand.o] Error 1
make[7]: Leaving directory '/opt/BUILD/debian/palemoon-27.1.1~repack/obj-x86_64-pc-linux-gnu/ipc/chromium'
#ifdef _EVENT_HAVE_SYS_SYSCTL_H
#include <sys/sysctl.h>
#endif
but, if there is no <sys/sysctl.h>, the build will also error, of course.
Now a question, why the Palemoon build needs to build a libevent, instead of using the system libevent, that is installed and available??
ii libevent-2.0-5:x32 2.0.21-stable-3 x32 Asynchronous event notification library
ii libevent-core-2.0-5:x32 2.0.21-stable-3 x32 Asynchronous event notification library (core)
ii libevent-dev 2.0.21-stable-3 x32 Asynchronous event notification library (development files)
ii libevent-extra-2.0-5:x32 2.0.21-stable-3 x32 Asynchronous event notification library (extra)
ii libevent-openssl-2.0-5:x32 2.0.21-stable-3 x32 Asynchronous event notification library (openssl)
ii libevent-pthreads-2.0-5:x32 2.0.21-stable-3 x32 Asynchronous event notification library (pthreads)
( and the same goes for other libs, like libssl3, libnss3, etc. )