Re: stunnel 5.44 build fails

2018-02-01 Thread Andrew Schulman
> > configure.ac:9: error: version mismatch.  This is Automake 1.15.1,
> > configure.ac:9: but the definition used by this AM_INIT_AUTOMAKE
> > configure.ac:9: comes from Automake 1.15.  You should recreate
> > configure.ac:9: aclocal.m4 with aclocal and run automake again.
> 
> you've patched src/Makefile.am, causing src/Makefile to run automake.
> 
> If you drop stunnel-ldflags.patch and just patch src/Makefile.in as you 
> did for 5.42 in stunnel-5.42-1.src.patch, I think you should be OK.

Yes, that worked, thanks.

That's weird about stunnel-5.42-1.src.patch. The source patch has always
been to src/Makefile.am, not src/Makefile.in. You can see that in
stunnel-ldflags.patch. I see that stunnel-5.42-1.src.patch patches
src/Makefile.in, and I have no idea where that came from. Something that
cygport did I guess.

Anyway thanks for the suggestion. Patching Makefile.in is more brittle than
Makefile.am, but it works for now.

Andrew



Re: stunnel 5.44 build fails

2018-01-30 Thread Achim Gratz
Ken Brown writes:
> On 1/29/2018 3:32 PM, Andrew Schulman wrote:
>> Prior to stunnel 5.42, I could build stunnel in Cygport with no src_compile
>> function, just
>>
>> CYGCONF=--disable-fips
>>
>> Beginning with stunnel 5.42, the build fails with errors about "possibly
>> undefined macro" AC_MSG_NOTICE and AC_DEFINE:
>
> I don't know why this is happening, but...
>
>> configure.ac:9: error: version mismatch.  This is Automake 1.15.1,
>> configure.ac:9: but the definition used by this AM_INIT_AUTOMAKE
>> configure.ac:9: comes from Automake 1.15.  You should recreate
>> configure.ac:9: aclocal.m4 with aclocal and run automake again.

I think this is caused by a fix that Yaakov made that gets things out of
sync when you do a full reconf.  I've had the same problem with another
package and it's easily fixed by adding a specification for version 1.15
or lower as the minimum autmomake version in Makefile.am.  Most
Makefile.am already have some minimum version specified so they never
run into that particular problem.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra


Re: stunnel 5.44 build fails

2018-01-29 Thread Ken Brown

On 1/29/2018 3:32 PM, Andrew Schulman wrote:

Prior to stunnel 5.42, I could build stunnel in Cygport with no src_compile
function, just

CYGCONF=--disable-fips

Beginning with stunnel 5.42, the build fails with errors about "possibly
undefined macro" AC_MSG_NOTICE and AC_DEFINE:


I don't know why this is happening, but...


configure.ac:9: error: version mismatch.  This is Automake 1.15.1,
configure.ac:9: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:9: comes from Automake 1.15.  You should recreate
configure.ac:9: aclocal.m4 with aclocal and run automake again.


you've patched src/Makefile.am, causing src/Makefile to run automake.

If you drop stunnel-ldflags.patch and just patch src/Makefile.in as you 
did for 5.42 in stunnel-5.42-1.src.patch, I think you should be OK.


Ken


stunnel 5.44 build fails

2018-01-29 Thread Andrew Schulman
Prior to stunnel 5.42, I could build stunnel in Cygport with no src_compile
function, just

CYGCONF=--disable-fips

Beginning with stunnel 5.42, the build fails with errors about "possibly
undefined macro" AC_MSG_NOTICE and AC_DEFINE:

$ cygport stunnel.cygport build
>>> Compiling stunnel-5.44-1.x86_64
autoreconf-2.69: Entering directory `.'
autoreconf-2.69: configure.ac: not using Gettext
autoreconf-2.69: running: aclocal --force -I m4
autoreconf-2.69: configure.ac: tracing
autoreconf-2.69: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'auto'.
libtoolize: copying file 'auto/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf-2.69: running: /usr/bin/autoconf-2.69 --force
configure.ac:4: error: possibly undefined macro: AC_MSG_NOTICE
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure.ac:23: error: possibly undefined macro: AC_DEFINE
autoreconf-2.69: /usr/bin/autoconf-2.69 failed with exit status: 1
*** ERROR: autoreconf failed

Nice. So I tried adding a custom src_compile:

src_compile ()
{
cd "${B}"
cygconf
cygmake
}

But then although configure completes, the build fails with

configure.ac:9: error: version mismatch.  This is Automake 1.15.1,
configure.ac:9: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:9: comes from Automake 1.15.  You should recreate
configure.ac:9: aclocal.m4 with aclocal and run automake again.

The full build log is below.

Can someone please suggest how to get past this? autoconf and automake are
mysteries to me.

Thanks,
Andrew

$ cygport stunnel.cygport build
>>> Compiling stunnel-5.44-1.x86_64
/home/ASchulma/dev/cygwin/stunnel/stunnel-5.44-1.x86_64/src/stunnel-5.44/configure
--srcdir=/home/ASchulma/dev/cygwin/stunnel/stunnel-5.44-1.x86_64/src/stunnel-5.44
--prefix=/usr -
-exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc
--docdir=/usr/share/doc/stunnel --htmldir=/usr/share/doc/stunnel/html -C
--disable-fips
configure: loading site script /usr/share/config.site
configure: creating cache config.cache
configure:  initialization
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-unknown-cygwin
checking host system type... x86_64-unknown-cygwin
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
checking whether make supports nested variables... (cached) yes
configure:  thread model
checking for a sed that does not truncate output... /usr/bin/sed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking whether gcc is Clang... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking whether more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... no
configure: PTHREAD thread model detected
configure:  compiler/linker flags
checking whether C compiler accepts -Wall... yes
checking whether C compiler accepts -Wextra... yes
checking whether C compiler accepts -Wpedantic... yes
checking whether C compiler accepts -Wformat=2... yes
checking whether C compiler accepts -Wconversion... yes
checking whether C compiler accepts -Wno-long-long... yes
checking whether C compiler accepts -Wno-deprecated-declarations... yes
checking whether C compiler accepts -fPIE... yes
checking whether C compiler accepts -fstack-protector... yes
checking whether the linker accepts -fPIE... yes
checking whether the linker accepts -pie... yes
checking whether the linker accepts -Wl,-z,relro... no
checking whether the linker accepts -Wl,-z,now... no
checking whether the linker accepts -Wl,-z,noexecstack... no
checking whether C compiler accepts -D_FORTIFY_SOURCE=2... yes
configure: