On 27.05.2018 20:10, Kern Sibbald wrote:
> I have been a bit busy lately, and I did apply your patch only to find
> out that it did not work. I think you had updated some of the autoconf
> files or were using a different one from me, because the new macro call
> that you added to configure.in is
Hello Sven,
I have been a bit busy lately, and I did apply your patch only to find
out that it did not work. I think you had updated some of the autoconf
files or were using a different one from me, because the new macro call
that you added to configure.in is not in my autoconf macro files.
On 02.04.2018 09:43, Kern Sibbald wrote:
> Oh, sorry, I did not look closely enough at the first patch :-(.
> Everytime autoconf/configure.in is changed I run "make configure" in the
> main directory, which does the aclocal and autoconf. This way, as a
> convenience to users, I distribute an up t
On 02.04.2018 09:43, Kern Sibbald wrote:
> Everytime autoconf/configure.in is changed I run "make configure" in the
> main directory, which does the aclocal and autoconf.
Currently the aclocal part is disabled in the Makefile because of problems:
Quote from the Makefile, line 67++:
# Note, the
Hello Sven,
Oh, sorry, I did not look closely enough at the first patch :-(.
Everytime autoconf/configure.in is changed I run "make configure" in the
main directory, which does the aclocal and autoconf. This way, as a
convenience to users, I distribute an up to date configure with the
source
On 01.04.2018 09:06, Kern Sibbald wrote:
> Thanks for your patches. The first two look fine, but there is a
> problem with the third patch for configure. The problem is that if
> anyone builds starting from scratch from source, configure will be
> overwritten when "make configure" is called. Th
Hello Sven
Thanks for your patches. The first two look fine, but there is a
problem with the third patch for configure. The problem is that
if anyone builds starting from scratch from source, configure will
be overwritten when "make configure" is called. This is
