glusterfs.git/configure.ac, branch v3.10.4

build: ensure autoconf template expansions resolve variables

2017-05-24T00:16:24+00:00

Make sure the following autotools managed variables:

GLUSTERFS_LIBEXECDIR
GLUSTERD_MISCDIR
GLUSTERD_VOLFILE
LOCALSTATEDIR

get expanded to literal paths when the configure
script generates the installed versions of certain
text files from *.in templates.

This change is partly implemented by restoring some of
the "eval echo $variable" style forced expansions in
configure that were removed in

  mainline BUG: 1444228
  master https://review.gluster.org/17096

Change-Id: I3b31b1259c5101252bbc37861683894e6eae29e6
BUG: 1450947
Signed-off-by: Kaleb S. KEITHLEY 
Signed-off-by: Csaba Henk 
Reviewed-on: https://review.gluster.org/17298
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

build: libgfxdr.so calls GF_FREE(), needs to link with -lglusterfs

2017-03-21T17:12:15+00:00

build: libgfxdr.so calls GF_FREE(), needs to link with -lglusterfs

The previous change to remove the xdrgen script exposed (or
created) a recursive build dependency: libglusterfs needs the
generated headers, and libgfxdr should be linked with libglusterfs
for GF_FREE/__gf_free.

(Much grumbling about libglusterfs being the kitchen sink of gluster
elided. This would not be necessary if there were two more more libs,
a gluster "runtime" library with common gluster code shared by the
xlators and daemons, and a utility library with things like the
rbtree, memory allocation, and whatnot.)

So. Link at build time or link at runtime? For truth-and-beauty, link
with libglusterfs.so at build time. Without truth-and-beauty, don't
link with libglusterfs and rely on other the libs that link with
libglusterfs to provide resolution of __gf_free().

Truth-and-beauty it is. But how to generate the headers first, then
build libglusterfs, then come back and build libgfxdr? Autotools is a
maze of twisty passages, all different. Things that work with gnu
make on linux don't work with the BSD make. Finally I hit on this
solution. Add a shadow directory where make only generates the headers,
then build libglusterfs using the generated headers, and finally build
libgfxdr and link with libglusterfs.

See original BZ 1330604
change http://review.gluster.org/14085

master BZ 1429696
master change: https://review.gluster.org/#/c/16873/

Change-Id: Iede8a30e3103176cb8f0b054885f30fcb352492b
BUG: 1430512
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/16874
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

build/packaging: Debian and Ubuntu don't have /usr/libexec

2017-03-13T14:19:00+00:00

GLUSTERFS_LIBEXECDIR is effectively hard-coded to /usr/libexec/glusterfs
in configure(.ac)

Debian-based distributions don't have a /usr/libexec/ directory

This issues is partially mitigated by the use of $libexecdir in
some of the Makefile.am files, but even so the incorrectly defined
GLUSTERFS_LIBEXECDIR results in various things such as gsyncd,
glusterfind, eventsd, etc., trying to invoke other scripts and
programs from a location that doesn't exist.

And once we correctly define GLUSTERFS_LIBEXECDIR, then we might as
well use it appropriatedly.

master change https://review.gluster.org/16880
master BZ: 1430841

Change-Id: If5219cadc51ae316f7ba2e2831d739235c77902d
BUG: 1430844
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/16881
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Milind Changire 
Reviewed-by: Shyamsundar Ranganathan

build: fixes to build 3.9.0rc2 on Debian

2017-02-26T19:14:21+00:00

Add glustereventsd-Debian(.in) and associated Makefile(.am)
and configure(.ac) changes

Add UUIDLIBS to fdl's librecon

Change-Id: Ibff821691023704978140eaaff2c6532b74c50fa
BUG: 1426222
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/16735
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Joe Julian 
Reviewed-by: Shyamsundar Ranganathan 
CentOS-regression: Gluster Build System

common-ha: revert switch to storhaug

2017-02-20T23:21:27+00:00

we'll try again for 3.11.

Change-Id: Ib4c50414dc3d16a23dc7a49020445129da55843c
BUG: 1410843
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/16692
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

core: remove experimental xlators and associated tests

2017-01-24T13:25:58+00:00

experimental xlators not included in 3.10

Change-Id: I547480ee5e7912664784643e436feb198b6d16d0
BUG: 1415866
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/16447
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Shyamsundar Ranganathan

storhaug HA: first step, remove resource agents and setup script

2017-01-18T00:53:30+00:00

resource agents and setup script(s) are now in storhaug

This is a phased switch-over to storhaug. Ultimately all components
here should be (re)moved to the storhaug project and its packages.
But for now some will linger here.

Change-Id: Ied3956972b14b14d8a76e22c583b1fe25869f8e7
BUG: 1410843
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/16349
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

rpm: depend on firewalld-filesystem for directory ownership

2017-01-10T02:17:51+00:00

Also use the %firewalld_reload macro that is provided by the
firewalld-filesystem package.

BUG: 1410853
Change-Id: Ibbbc18cc394f8b1e5ba74927effc41c466667479
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/16351
Smoke: Gluster Build System 
Tested-by: Kaleb KEITHLEY 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

core: Disable the memory pooler in Gluster via a build flag

2017-01-04T11:42:40+00:00

Summary:
Passing --disable-mempool to configure will disable the mempool.

Change-Id: I60d5f70d54de507fe9f4695d7589f7ae1ba4bb0f
BUG: 1405165
Signed-off-by: Shreyas Siravara 
Reviewed-on: http://review.gluster.org/16148
Smoke: Gluster Build System 
Tested-by: Jeff Darcy 
Reviewed-by: Niels de Vos 
Reviewed-by: Kaleb KEITHLEY 
CentOS-regression: Gluster Build System 
Reviewed-by: Anoop C S 
NetBSD-regression: NetBSD Build System

build: python site-packages vs. dist-packages

2016-12-11T12:43:21+00:00

Unlike Fedora and RHEL/CentOS, where python has
/usr/{lib,lib64}/python2.7/site-packages/...,  Debian-based
distributions have /usr/lib/python2.7/dist-packages/...

On Debian our python scriptlet to determine this is broken and
incorrectly returns .../site-packages, not .../dist-packages.
Furthermore, the automake/autoconf/pkgconfig bits ahead of our
own scriptlet have already determined the correct location -- all
we need to do is use it.

This change also slightly reworks the BUILD_PYTHON_INC scriptlet
to bring it in line with the style/pattern of the other python
scriptlets provided by autoconf/pkgconfig.

(I do wonder though, why we have two sets of {C,CPP}FLAGS and
LD_FLAGS - PYTHONDEV_CPPFLAGS and BUILD_PYTHON_INC, and
PYTHONDEV_LDFLAGS and BUILD_PYTHON_LIB.

They both have very similar values, but, e.g. BUILD_PYTHON_INC
misses /usr/lib/x86_64-linux-gnu/python2.7 on Debian; even if that
ommission doesn't seem to be hurting us.)

Change-Id: I309a5c781a1d9aee4d7be2867223781bd2ae18fa
BUG: 1388861
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/15733
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Milind Changire 
Reviewed-by: Niels de Vos