public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] NEW: automake1.14-1.14-1
Date: Fri, 02 Aug 2013 14:32:00 -0000	[thread overview]
Message-ID: <announce.20130802143117.469F16800A0@frontend2.nyi.mail.srv.osa> (raw)

Automake is a tool for automatically generating `Makefile.in's
suitable for use with Autoconf, compliant with the GNU Makefile
standards, and portable to various make implementations. This is
the first release in the automake-1.14 release series, and contains
the latest version of automake system, automake-1.14.

This cygwin package, automake1.14, can be installed without conflict
alongside the existing automake1.13 ... automake1.4 cygwin packages,

CHANGES (vs automake 1.13 series)
======================================================================
1.14.0: We are pleased to announce the GNU Automake 1.14 minor
1.14.0: release.
1.14.0: 
1.14.0: This release comes with two important changes:
1.14.0: 
1.14.0:   1. It introduces a new feature aimed at making the
1.14.0:   implementation of non-recursive build systems more
1.14.0:   convenient and manageable (thanks to the new support
1.14.0:   for the '%reldir%' and '%canon_reldir%' automake-time
1.14.0:   substitutions).
1.14.0: 
1.14.0:   2. It improves the handling of C compiles not
1.14.0:   supporting the conjunct use of the '-c' and '-o'
1.14.0:   options (unfortunately, this improvement comes with a
1.14.0:   couple of minor backward-incompatibilities, described
1.14.0:   in detail in the NEWS section below). Among th other
1.14.0:   things, this means that you no longer need to explicitly
1.14.0:   call the AM_PROG_CC_C_O macro yourself in configure.ac
1.14.0:   (pre-existing invocation of this macro are of course
1.14.0:   still accepted and correctly working, for the sake of
1.14.0:   backward-compatibility).
1.14.0: 
1.14.0: The 1.14 release also introduces new (non-fatal) runtime
1.14.0: warnings to simplify the transition to Automake 2.0. You are
1.14.0: free to ignore such warnings for now, but should address
1.14.0: them before the transition to Automake 2.0 (whose ETA is
1.14.0: about one year from now, maybe more, so no need to hurry
1.14.0: yet).
1.14.0:
1.14.0: See the official announcement for more information:
1.14.0: http://lists.gnu.org/archive/html/automake/2013-06/msg00040.html

Testsuite results:
=======================================================
Testsuite summary for GNU Automake 1.14
         cyg32  cyg64
=======================================================
# TOTAL: 3036   3036
# PASS:  2907   2927
# SKIP:  85       69
# XFAIL: 40       39
# FAIL:  4         1
# XPASS: 0         0
# ERROR: 0         0
=======================================================

Testsuite details:
=======================================================
The tests were executed with LANG=en_US.UTF-8, running as a regular
user on Windows 7 64bit with cygwin(32)-1.7.21-1 / cygwin(64)-1.7.21-7.

The four cyg32 failures were:
cyg32| FAIL: t/tap-signal.tap 2 - count of test results
cyg32| FAIL: t/tap-signal.tap 5 - TAP driver catch test term. by SIGQUIT
cyg32| FAIL: t/tap-signal-w.tap 2 - count of test results
cyg32| FAIL: t/tap-signal-w.tap 5 - TAP driver catch test term. by SIGQUIT
which appear to be due to a difference in signal handling with respect
to SIGQUIT between cygwin32 and cygwin64. This issue is being
investigated.

The sole cyg64 failure was:
FAIL: t/instspc.tap 33 - plus in builddir
which appears to reflect that '+' is not allowed in a directory name
on Windows, but the test expects it to be legal. The question is, why
does the test pass on cyg32? Unsure...

Still -- only 4 (or 1) failures out of over 3000 tests is not bad.

-- 
Charles Wilson
volunteer automake maintainer for cygwin

====================================================================

To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Then, run setup and answer all of the questions.

              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is
available starting at this URL.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

                 reply	other threads:[~2013-08-02 14:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=announce.20130802143117.469F16800A0@frontend2.nyi.mail.srv.osa \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin@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).