[SCM] GNU Libtool branch, praiskup-ARFLAGS, created. v2.4.6-6-ge503ccc

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Libtool".

The branch, praiskup-ARFLAGS has been created
        at  e503ccc64bcac5a80766876fe985937194d4cf12 (commit)

- Log -----------------------------------------------------------------
commit e503ccc64bcac5a80766876fe985937194d4cf12
Author: Pavel Raiskup <[email protected]>
Date:   Thu Jun 25 14:53:28 2015 +0200

    maint: relax 'sc_prohibit_test_dollar' check
    
    * cfg.mk (sc_prohibit_test_dollar): White-list the
    'test ${VAR+y}' construct because that is autoconf-suggested
    portable way to check for unset variable.

commit f589837a9cd2492b7022c159bddba770be9314a6
Author: Pavel Raiskup <[email protected]>
Date:   Thu Jun 25 11:43:32 2015 +0200

    maint: more readable ChangeLog
    
    * Makefile.am ($(changelog)): Generate each changelog entry with
    newline after the initial commit description.

commit 568263a75e3b6d6a6f700550dfc8cc07ac1a0c49
Author: Pavel Raiskup <[email protected]>
Date:   Fri Apr 17 16:54:58 2015 +0200

    ARFLAGS: use 'cr' instead of 'cru' by default
    
    In some GNU/Linux distributions people started to compile 'ar'
    binary with --enable-deterministic-archives (binutils project).
    That, however, in combination with our previous long time working
    default AR_FLAGS=cru causes warnings on such installations:
    ar: `u' modifier ignored since `D' is the default (see `U')
    
    The 'u' option (at least with GNU binutils) did small optimization
    during repeated builds because it instructed 'ar' to not
    open/close unchanged *.o files and to rather read their contents
    from old archive file.  However, its removal should not cause a
    big performance hit for usual workflows.
    
    Distributions started using --enable-deterministic-archives
    knowing that it would disable the 'u', just to rather have a bit
    more deterministic builds.
    
    Also, to justify this change a bit more, keeping 'u' in ARFLAGS
    could only result in many per-project changes to override
    Libtool's ARFLAGS default, just to silent such warnings.
    
    Fixes bug#19967.  Reported by Eric Blake.
    
    * m4/libtool.m4 (_LT_PROG_AR): Default AR_FLAGS to 'cr'.
    (_LT_REQUIRED_DARWIN_CHECKS): Use $AR_FLAGS instead 'cru' string.
    * doc/libtool.texi: Do 's/ar cru/ar cr/' in whole documentation.
    * NEWS: Document.

commit 6816ad8046352f1f7f66ca8b711854b0d423a16e
Author: Pavel Raiskup <[email protected]>
Date:   Fri Apr 17 15:05:42 2015 +0200

    libool.m4: add ARFLAGS variable
    
    Libtool has used $AR_FLAGS since 2000-05-29 commit
    8300de4c54e6f04f0d, Automake ARFLAGS since 2003-04-06 commit
    a71b3490639831ca.  Even though ARFLAGS is younger, it sounds like
    better name according GNU Coding Standards.
    
    Related to bug#20082.
    
    * m4/libtool.m4 (_LT_PROG_AR): Copy ARFLAGS value into AR_FLAGS
    variable if AR_FLAGS is not set.  Add new _LT_DECL'ed variable
    'lt_ar_flags' to keep the configure-time value of AR_FLAGS.  The
    new 'lt_ar_flags' is to be used as the default value for AR_FLAGS
    at libtool-runtime.
    * NEWS: Document.

-----------------------------------------------------------------------


hooks/post-receive
-- 
GNU Libtool