public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Mailing List: CygWin-Apps <cygwin-apps@cygwin.com>
Subject: Updated for cygwin-1.7: automake1.5-1.5-10
Date: Fri, 24 Oct 2008 03:23:00 -0000	[thread overview]
Message-ID: <49013F6F.3040704@cwilson.fastmail.fm> (raw)

Automake is a tool for automatically generating `Makefile.in' files
compliant with the GNU Coding Standards.

This cygwin package, automake1.5, can be installed without conflict
alongside the existing automake1.10, automake1.9, automake1.8,
automake1.7, automake1.6, and automake1.4 cygwin packages.

This is the first release specific for cygwin-1.7; the only differences
between this package and the simultaneously-released automake1.5-1.5-3
for cygwin-1.5 are documentation related (the README references
cygport-0.9.2 and cygwin-1.7.0-30, and the /usr/share/doc/ layout is
influenced by the cygport changes between 0.4.0 and 0.9.2).

There are some differences encountered when running the test suite, but
those aren't changes in the automake1.5 package itself; cygwin-1.7 just
does a better job and passes more tests.


Changes (automake1.5-1.5-2 ---> automake1.5-1.5-10)

* Fork from cygwin-1.5 package development stream
* Updated packaging to use stock cygport 0.9.2
  rather than custom version of cygport.
* Fix setup.hint
* Ensure /usr/share/aclocal directory is preserved.

Testsuite results:
=====================
3 of 323 tests failed
=====================
FAIL: dirname.test, insthook.test, subdircond.test

A few points:

1) pr87.test fails under cygwin-1.5 but passes here

2) lex3.test fails under cygwin-1.5 but passes here

3) dirname.test only fails the first time it is run. When run standalone
subsequently, I can't reproduce the failure. This is similar to behavior
under cygwin-1.5.

4) subdircond.test seems to be a false failure for both
automake1.5-1.5-3 on cygwin-1.5, and automake1.5-1.5-10 on cygwin-1.7.
In repeated tests, it is skipped (and was previously skipped on
automake1.5-1.5-2, the direct predecessor to each of these two versions
of the package). subdircond.test just fails once, the first time it is
run, as part of the entire suite. It is always skipped (as it should be)
when I attempt to run that test later standalone.

5) insthook.test seems to be an actual regression related to cygwin-1.7
-- but it's just a bug in the test suite (an incompatibility with the
new coreutils tail.exe):

this line in the test fails with an error message from tail:

test x$lnum != x && tail +$lnum Makefile.in | head -3 | grep
install-exec-hook

this version passes:

test x$lnum != x && tail --lines=+$lnum Makefile.in | head -3 | grep
install-exec-hook

So, to sum up: it appears that overall, automake1.5 on cygwin-1.5 failed
2 tests when all was said and done, but automake1.5 on cygwin-1.7 passes
all tests!

-- 
Charles Wilson
automake volunteer 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://sources.redhat.com/lists.html#unsubscribe-simple

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

                 reply	other threads:[~2008-10-24  3:23 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=49013F6F.3040704@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --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).