public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: stunnel 5.44 build fails
Date: Tue, 30 Jan 2018 18:43:00 -0000	[thread overview]
Message-ID: <874ln3fari.fsf@Rainer.invalid> (raw)
In-Reply-To: <f1e1c180-2db9-e749-aa41-acc1f93679ba@cornell.edu> (Ken Brown's	message of "Mon, 29 Jan 2018 18:37:11 -0500")

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

  reply	other threads:[~2018-01-30 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 20:33 Andrew Schulman
2018-01-29 23:37 ` Ken Brown
2018-01-30 18:43   ` Achim Gratz [this message]
2018-02-01 14:33   ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ln3fari.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).