Stepan Kasal | 4 Jan 21:07 2006
Picon

Mac OS X 10.2 uses bash as /bin/sh

Hello.

On Wed, Jan 04, 2006 at 08:01:30PM +0100, Andreas Schwab wrote:
> Stepan Kasal <kasal <at> ucw.cz> writes:
> 
> > the Autoconf manual says:
> >
> >      Zsh 3.0.8 is the native `sh' on Mac OS X 10.0.3.
> 
> Note that this has been "fixed" in 10.2 (bash is now used).

Is it worth it to commit the following patch?

Stepan
2006-01-04  Stepan Kasal  <kasal <at> ucw.cz>

	* doc/autoconf.texi (Shellology): Document that Mac OS X 10.2
	  uses bash as /bin/sh.

Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.937
diff -u -r1.937 autoconf.texi
--- doc/autoconf.texi	29 Dec 2005 21:28:30 -0000	1.937
+++ doc/autoconf.texi	4 Jan 2006 20:04:37 -0000
 <at>  <at>  -9890,6 +9890,7  <at>  <at> 
 zsh, The Z Shell Manual}, for details.
(Continue reading)

Paul Eggert | 4 Jan 23:30 2006

Re: Mac OS X 10.2 uses bash as /bin/sh

Stepan Kasal <kasal <at> ucw.cz> writes:

> Is it worth it to commit the following patch?

Thanks.  I committed the following slightly different one.

2006-01-04  Paul Eggert  <eggert <at> cs.ucla.edu>

	* doc/autoconf.texi: Update copyright (and other) dates to 2006.
	* doc/autoconf.texi (Shellology): Mac OS X 10.2 changed the default
	shell from zsh to bash.

Index: autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.937
retrieving revision 1.939
diff -p -u -r1.937 -r1.939
--- autoconf.texi	29 Dec 2005 21:28:30 -0000	1.937
+++ autoconf.texi	4 Jan 2006 22:28:37 -0000	1.939
 <at>  <at>  -181,7 +181,7  <at>  <at>  a package for creating scripts to config
 templates and an M4 macro package.

 Copyright  <at> copyright{} 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000,
-2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
+2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.

  <at> quotation
 Permission is granted to copy, distribute and/or modify this document
 <at>  <at>  -9864,7 +9864,7  <at>  <at>  its own.  Similarly to Bash, you can det
(Continue reading)

Ralf Wildenhues | 5 Jan 11:10 2006
Picon
Picon

Re: AC_FC_LIBRARY_LDFLAGS

* Ralf Wildenhues wrote on Mon, Dec 12, 2005 at 04:06:09PM CET:
> * Ralf Wildenhues wrote on Sat, Dec 03, 2005 at 12:22:38PM CET:
> > * Christopher Hulbert wrote on Fri, Dec 02, 2005 at 07:12:02PM CET:
> > > I couldn't find any other solution to this, but when getting the
> > > library flags of pgf90 with -Mconcur or -Mipa (Runs pgipa) there is an
> 
> I have tested this patch myself (should've said that right away, sorry).
> Is it ok to apply?

No comments, so I applied this.

Cheers,
Ralf

	* lib/autoconf/fortran.m4 (_AC_FC_LIBRARY_LDFLAGS): Ignore
	singly- or doubly-quoted arguments to `-cmdline', `-ignore',
	`-def', for the benefit of Portland `pgf90 -Mipa'.
	Reported by Christopher Hulbert <cchgroupmail <at> gmail.com>.

Index: lib/autoconf/fortran.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/fortran.m4,v
retrieving revision 1.198
diff -u -r1.198 fortran.m4
--- lib/autoconf/fortran.m4	27 Oct 2005 06:16:04 -0000	1.198
+++ lib/autoconf/fortran.m4	5 Jan 2006 10:10:35 -0000
 <at>  <at>  -1,6 +1,6  <at>  <at> 
 # This file is part of Autoconf.                       -*- Autoconf -*-
 # Fortran languages support.
-# Copyright (C) 2001, 2003, 2004, 2005
(Continue reading)

Ralf Wildenhues | 5 Jan 14:20 2006
Picon
Picon

Re: depcomp: support newer HP compilers

[ moving from automake-patches to autoconf-patches; see
http://thread.gmane.org/gmane.comp.sysutils.automake.patches/2074 ]

* Zack Weinberg wrote on Wed, Jan 04, 2006 at 05:43:32AM CET:
> On Wed, Jan 04, 2006 at 12:23:44AM +0100, Ralf Wildenhues wrote:
> > 
> > Do you have any idea which system might expose this?  None of the
> > ones I have access to do, and it helps both for adding a note to
> > the Autoconf doc portability section, and assessing whether we
> > should check the autotools for more instances of this.
> 
> Try, um, older Solaris /bin/sed?  I don't honestly remember how
> long ago I tripped over this -- I've just been sticking the semicolon
> in defensively ever since.  I had thought, though, that the
> proprietary Unix vendors froze the utilities in /bin and /usr/bin
> in a pre-SuS state, and thus that any such problem would be present
> always and forevermore.  A *lot* of these issues are masked if you
> put the directory with the standard-compliant binaries (usually
> /usr/xpg4/bin or something like that) ahead of /usr/bin in your
> PATH, or if your sysadmin installs GNU coreutils on everything.

Well, I don't have access to Solaris older that 2.6, and all newer ones
do not expose the issue.  And yes, I usually test all tools I can find
on a given system; users have the tendency to change PATH anyway.

* Stepan Kasal wrote on Wed, Jan 04, 2006 at 07:36:13AM CET:
> 
> actually, I always thought that only Solaris has this problem.
> 
> Yes, other proprieatar Unices are natural years behind, but I think they
(Continue reading)

Ralf Wildenhues | 5 Jan 16:17 2006
Picon
Picon

small typo in status.m4

I have applied this tiny patch, in the hope that it was ok to do so.

Aside: by the old copyright year rules, this would be a small patch
not needing an update; by the new ones, apparently either none or
all files could be changed at once;  it may be good to know how
Autoconf developers choose to do.

Cheers,
Ralf

	* lib/autoconf/status.m4: Fix typo.

Index: lib/autoconf/status.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/status.m4,v
retrieving revision 1.80
diff -u -r1.80 status.m4
--- lib/autoconf/status.m4	10 Nov 2005 18:57:59 -0000	1.80
+++ lib/autoconf/status.m4	5 Jan 2006 15:14:41 -0000
 <at>  <at>  -318,7 +318,7  <at>  <at> 
 # This code was written by Dan Manthey.
 #
 # This macro is expanded inside a here document.  If the here document is
-# closed, it has to be reopen with "cat >>$CONFIG_STATUS <<\_ACEOF".
+# closed, it has to be reopened with "cat >>$CONFIG_STATUS <<\_ACEOF".
 #
 m4_define([_AC_OUTPUT_FILES_PREPARE],
 [#

(Continue reading)

Paul Eggert | 5 Jan 22:45 2006

Portable use of "{", ";", etc. within sed scripts

Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> writes:

> +verbs.  On the other hand, commands after  <at> samp{ <at> {} should be preceded
> +by  <at> samp{;} unless preceded by a newline.

That's not strict enough, I'm afraid.  The POSIX rule is that you
cannot use semicolons inside { } at all, in a sed script.  Nor can you
use addresses like 1 or $ or /x/ inside { }; nor can you use !; and
there are some other limits.

Automake uses '{' within sed commands, so it should be swept for these
problems, too.  I'll follow up on bug-automake.

I have added documentation for this in the Autoconf manual, as
described below.  I also swept Autoconf for instances of this problem
and fixed all the ones that I found.

Here's the patch I installed.

2006-01-05  Paul Eggert  <eggert <at> cs.ucla.edu>

	Fix Posix-conformance bugs re use of { command in sed scripts,
	and improve the sed-related documentation a bit.
	* doc/autoconf.texi (Installation Directory Variables): Use
	our own style advice re 's,a,b,' versus 's|a|b|'.  Use "Sed"
	rather than "sed" when talking about Sed in general.
	(Particular Programs): Likewise.
	(Coding Style): y is like s with respect to / and ,.
	(Limitations of Usual Tools): Document the weird restrictions
	that Posix has about { }.  Use better quoting.
(Continue reading)

Noah Misch | 5 Jan 23:20 2006
Picon

Re: Portable use of "{", ";", etc. within sed scripts

[ cc: trimmed somewhat ]

On Thu, Jan 05, 2006 at 01:45:59PM -0800, Paul Eggert wrote:
> 	* doc/autoconf.texi (Installation Directory Variables): Use
> 	our own style advice re 's,a,b,' versus 's|a|b|'.  Use "Sed"
> 	rather than "sed" when talking about Sed in general.

> 	* tests/semantics.at (AC_CHECK_PROG & AC_CHECK_PROGS):
> 	Use our own style advice re 's,a,b,' versus 's|a|b|'.

You introduced the `s|a|b|' convention to much of Autoconf in a change dated
2005-03-22, to support file names containing `,'.  The `s,a,b,' recommendation
in the manual predates that change.  Is `s,a,b' preferable after all, or is it
the manual's recommendation that should change?

Paul Eggert | 6 Jan 01:02 2006

Re: Portable use of "{", ";", etc. within sed scripts

Noah Misch <noah <at> cs.caltech.edu> writes:

> You introduced the `s|a|b|' convention to much of Autoconf in a change dated
> 2005-03-22, to support file names containing `,'.  The `s,a,b,' recommendation
> in the manual predates that change.  Is `s,a,b' preferable after all, or is it
> the manual's recommendation that should change?

Ouch.  Good catch.  I reverted that part of the change, found some
more instances where Autoconf should be tasting its own medicine, and
installed the following.

2006-01-05  Paul Eggert  <eggert <at> cs.ucla.edu>

	* Makefile.maint (sc_root_tests): Use recommend style s/a/b/ for
	sed substitutions.
	* doc/autoconf.texi (Installation Directory Variables): Use s|a|b|
	for file names, again.  Reported by Noah Misch.
	(Coding Style): Explain that s|a|b| is preferred for file names.
	* lib/autoconf/status.m4 (_AC_OUTPUT_FILES_PREPARE): Prefer s/a/b/.
	(AC_OUTPUT_MAKE_DEFS): Likewise.
	* lib/autotest/general.m4 (AT_INIT): Likewise.
	* lib/m4sugar/m4sh.m4 (_AS_LINENO_PREPARE): Likewise.
	* tests/local.at (AT_CHECK_AUTOM4TE): Likewise.

Index: Makefile.maint
===================================================================
RCS file: /cvsroot/autoconf/autoconf/Makefile.maint,v
retrieving revision 1.32
diff -p -u -r1.32 Makefile.maint
--- Makefile.maint	23 Aug 2005 07:46:54 -0000	1.32
(Continue reading)

Steven G. Johnson | 9 Jan 23:53 2006
Picon

patch - bug fix for AC_F77_DUMMY_MAIN and AC_FC_DUMMY_MAIN

Hi, I just noticed a silly bug that crept in when the F77 -> F77+FC 
change was made: the abovementioned two macros ignore their arguments!

2006-01-09  Steven G. Johnson  <stevenj <at> alum.mit.edu>

         * lib/autoconf/fortran.m4 (AC_F77_DUMMY_MAIN, AC_FC_DUMMY_MAIN):
         Don't ignore the macro arguments.

Patch follows:

diff -u -r1.199 fortran.m4
--- lib/autoconf/fortran.m4     5 Jan 2006 10:11:22 -0000       1.199
+++ lib/autoconf/fortran.m4     9 Jan 2006 22:49:15 -0000
 <at>  <at>  -828,7 +828,7  <at>  <at> 
  AC_DEFUN([AC_F77_DUMMY_MAIN],
  [AC_REQUIRE([AC_F77_LIBRARY_LDFLAGS])dnl
  AC_LANG_PUSH(Fortran 77)dnl
-_AC_FC_DUMMY_MAIN
+_AC_FC_DUMMY_MAIN([$1],[$2])
  AC_LANG_POP(Fortran 77)dnl
  ])# AC_F77_DUMMY_MAIN

 <at>  <at>  -838,7 +838,7  <at>  <at> 
  AC_DEFUN([AC_FC_DUMMY_MAIN],
  [AC_REQUIRE([AC_FC_LIBRARY_LDFLAGS])dnl
  AC_LANG_PUSH(Fortran)dnl
-_AC_FC_DUMMY_MAIN
+_AC_FC_DUMMY_MAIN([$1],[$2])
  AC_LANG_POP(Fortran)dnl
  ])# AC_FC_DUMMY_MAIN
(Continue reading)

Ralf Wildenhues | 10 Jan 18:56 2006
Picon
Picon

Fix AS_HELP_STRING (AC_HELP_STRING) with quadrigraphs

A bit ugly.  But works for AS_HELP_STRING.  :-)

OK to apply (including copyright year updates)?
Does this break any other m4_text_wrap uses?
If yes, are they important enough to worry about?  I could only find
the autoheader one, which should not be impacted by the patch below.

Cheers,
Ralf

	* lib/m4sugar/m4sugar.m4 (m4_text_wrap): Handle quadrigraphs
	correctly: pad with spaces after FIRST_PREFIX if necessary,
	and compute string lenghts with `m4_qlen' instead of `m4_len'.
	* lib/m4sugar/m4sh.m4 (AS_HELP_STRING): Comments updated.
	* tests/m4sh.at (AS_HELP_STRING): Test extended.
	Reported by numerous people, numerous times.

Index: lib/m4sugar/m4sh.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/m4sugar/m4sh.m4,v
retrieving revision 1.154
diff -u -r1.154 m4sh.m4
--- lib/m4sugar/m4sh.m4	6 Jan 2006 00:02:26 -0000	1.154
+++ lib/m4sugar/m4sh.m4	10 Jan 2006 19:05:20 -0000
 <at>  <at>  -1171,16 +1171,8  <at>  <at> 
 #  column 0                  column 26
 #
 #
-# FIXME: Handle quadrigraphs in LHS correctly.
-# another one:
(Continue reading)


Gmane