From MAILER-DAEMON Fri Dec 07 08:59:40 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TgySq-0004O6-Q2
	for mharc-autoconf@gnu.org; Fri, 07 Dec 2012 08:59:40 -0500
Received: from eggs.gnu.org ([208.118.235.92]:59802)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TgySm-0004LL-Px
	for autoconf@gnu.org; Fri, 07 Dec 2012 08:59:37 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TgySg-0005ms-Cv
	for autoconf@gnu.org; Fri, 07 Dec 2012 08:59:36 -0500
Received: from mx1.redhat.com ([209.132.183.28]:38320)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TgySg-0005ml-52
	for autoconf@gnu.org; Fri, 07 Dec 2012 08:59:30 -0500
Received: from int-mx01.intmail.prod.int.phx2.redhat.com
	(int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qB7DxRGf021485
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Fri, 7 Dec 2012 08:59:27 -0500
Received: from [10.3.112.21] (ovpn-112-21.phx2.redhat.com [10.3.112.21])
	by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id qB7DxQD3028718; Fri, 7 Dec 2012 08:59:26 -0500
Message-ID: <50C1F63D.6050004@redhat.com>
Date: Fri, 07 Dec 2012 06:59:25 -0700
From: Eric Blake <eblake@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Nick Bowler <nbowler@elliptictech.com>
Subject: Re: Can packages rely on AC_PROVIDE_IFELSE?
References: <20121126150215.GA18142@elliptictech.com>
In-Reply-To: <20121126150215.GA18142@elliptictech.com>
X-Enigmail-Version: 1.4.6
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature";
	boundary="------------enig12044683BF12BDAC531A5792"
X-Scanned-By: MIMEDefang 2.67 on 10.5.11.11
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 209.132.183.28
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 13:59:38 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig12044683BF12BDAC531A5792
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 11/26/2012 08:02 AM, Nick Bowler wrote:
> Hi folks,
>=20
> Autoconf defines a macro called AC_PROVIDE_IFELSE, which can allow
> one to hook into the AC_REQUIRE machinery in order to do potentially
> interesting things.  For a specific example, I recently wanted to emit =
a
> (hopefully) helpful warning message if LT_INIT had not been previously
> expanded, and it seems that I can do that very easily with something
> like:
>=20
>   AC_PROVIDE_IFELSE([LT_INIT], , [m4_warn([syntax], [blah blah])])

Good question - looks like you found a real hole in the documentation.
It looks like AC_PROVIDE vs. AC_PROVIDE_IFELSE should be documented
together; and also that m4_provide and m4_provide_if should be
documented together.  What's more, the manual mentions that macros can
call AC_PROVIDE but does not document what it does.

>=20
> However, AC_PROVIDE_IFELSE is not described in the Autoconf manual,
> which makes me wonder if the macro should be used by packages.  The fac=
t
> that it's defined at all (as an alias for m4_provide_if) seems to
> suggest that it was intended to be used...

Yes, the macros are stable and intended to be usable; we're just missing
the documentation patch.

>=20
> Also, on a related note, AC_PROVIDE is referred to several times in the=

> Autoconf manual (in a manner that suggests that packages can use it) bu=
t
> the manual never actually explains what AC_PROVIDE does or how to invok=
e
> it properly.

Yep, I just came to the same conclusion after reading just your first
paragraph and searching for myself.

>=20
> So, are these macros intended to be used by packages?  If so, can they
> be documented in the manual?

Absolutely.  Want to help write the patch?

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--------------enig12044683BF12BDAC531A5792
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBCAAGBQJQwfY9AAoJEKeha0olJ0NqzlYIAJALP8EAdI7cmeybTqfrbaK9
m2UC8c9DeeYkLrIfF2U98fMC6TfpSAOyJhEdI23OvLuAXjWbF75bqc1wTEftbTSj
ov3xEfJzIJhPebo2EWB83YoLYYVF1Cyd+dKRg1IE4ez/4KPBg/Re+hnX78uG1mDN
84lyHidkwgHRfEnZ+RwWbKlZo56tISvfTIk61OVPizSrjpS32Ff/NmlPkDHsZxWI
zJME1lrtOd8116tA4vAwYqqM5sjIUbCrauAmD6/jCzqyOC3ym0lK2hs/mgkxOZ0g
JZqdlR+ZqatknrGtOEcvSqg7yrpgVYPuefq+DE930lQXggBKrdQUu2K5BSGqW1A=
=nsFD
-----END PGP SIGNATURE-----

--------------enig12044683BF12BDAC531A5792--


From MAILER-DAEMON Sat Dec 08 09:32:18 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThLRy-0000MN-2P
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 09:32:18 -0500
Received: from eggs.gnu.org ([208.118.235.92]:56016)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <picca@synchrotron-soleil.fr>) id 1ThI1a-0004a0-DH
	for autoconf@gnu.org; Sat, 08 Dec 2012 05:52:51 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <picca@synchrotron-soleil.fr>) id 1ThI1Z-0002IJ-4p
	for autoconf@gnu.org; Sat, 08 Dec 2012 05:52:50 -0500
Received: from smtp25.services.sfr.fr ([93.17.128.118]:10307)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <picca@synchrotron-soleil.fr>) id 1ThI1Y-0002E8-Uw
	for autoconf@gnu.org; Sat, 08 Dec 2012 05:52:49 -0500
Received: from filter.sfr.fr (localhost [127.0.0.1])
	by msfrf2502.sfr.fr (SMTP Server) with ESMTP id F3EC47000558
	for <autoconf@gnu.org>; Sat,  8 Dec 2012 11:52:08 +0100 (CET)
Received: from mordor (219.129.88.79.rev.sfr.net [79.88.129.219])
	by msfrf2502.sfr.fr (SMTP Server) with ESMTP id D7DE27000556
	for <autoconf@gnu.org>; Sat,  8 Dec 2012 11:52:08 +0100 (CET)
X-SFR-UUID: 20121208105208884.D7DE27000556@msfrf2502.sfr.fr
Received: from picca by mordor
	with local (Exim 4.80)	(envelope-from <picca@synchrotron-soleil.fr>)
	id 1ThI0t-0006aB-N5	for autoconf@gnu.org;
	Sat, 08 Dec 2012 11:52:07 +0100
From: picca@debian.org
To: autoconf@gnu.org
Subject: rm -f core cause some troubles
Date: Sat, 08 Dec 2012 11:52:02 +0100
Message-ID: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
MIME-Version: 1.0
Content-Type: text/plain
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 93.17.128.118
X-Mailman-Approved-At: Sat, 08 Dec 2012 09:32:17 -0500
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 10:52:51 -0000


Hello, I have a problem with one of the projet I am trying to convert to
autoconf/automake.

during the configure process, I got plenty of

rm: cannot remove `core': Is a directory
yes
checking for sys/types.h... rm: cannot remove `core': Is a directory
yes
checking for sys/stat.h... rm: cannot remove `core': Is a directory
yes
checking for stdlib.h... rm: cannot remove `core': Is a directory
yes
checking for string.h... rm: cannot remove `core': Is a directory
yes
checking for memory.h... rm: cannot remove `core': Is a directory
yes
checking for strings.h... rm: cannot remove `core': Is a directory
yes
checking for inttypes.h... rm: cannot remove `core': Is a directory
yes
checking for stdint.h... rm: cannot remove `core': Is a directory
yes
checking for unistd.h... rm: cannot remove `core': Is a directory
yes
checking for dlfcn.h... rm: cannot remove `core': Is a directory
yes

Indeed one directory of the project is named 'core'.

Nevertheless once done with the configuration, 'make' works like a charm
and I obtain the right library.

now to trigger the real effect of this annoying message, the distcheck
target need to be be used

It gives this error

ERROR: files left in build directory after distclean:
./confdefs.h

so it seems to me that it should be allow to have a core directory in a
projetc, this is a valid name. So the logic when removing core files,
would be to check first thta they are real file and not a directory.

what is you opinion, is it an autoconf bug ?

Thanks

Frederic


ii  autoconf                             2.69-1                  all                     automatic configure script builder


From MAILER-DAEMON Sat Dec 08 12:27:36 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThOBc-0001Tx-FP
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 12:27:36 -0500
Received: from eggs.gnu.org ([208.118.235.92]:58717)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThOBa-0001TG-9W
	for autoconf@gnu.org; Sat, 08 Dec 2012 12:27:35 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThOBZ-0002hU-61
	for autoconf@gnu.org; Sat, 08 Dec 2012 12:27:34 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:60537)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThOBY-0002hQ-Vs
	for autoconf@gnu.org; Sat, 08 Dec 2012 12:27:33 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 77C64A60002;
	Sat,  8 Dec 2012 09:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iTCwwT5B0SMi; Sat,  8 Dec 2012 09:27:32 -0800 (PST)
Received: from [192.168.1.3] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id D5D37A60001;
	Sat,  8 Dec 2012 09:27:31 -0800 (PST)
Message-ID: <50C37888.2080002@cs.ucla.edu>
Date: Sat, 08 Dec 2012 09:27:36 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: picca@debian.org
Subject: Re: rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
In-Reply-To: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 17:27:35 -0000

On 12/08/2012 02:52 AM, picca@debian.org wrote:
> So the logic when removing core files,
> would be to check first thta they are real file and not a directory.

That would slow down 'configure' everywhere.

It might make sense to have an Autoconf option that would
add that behavior as an option, for people who want to have
directories named 'core', and who don't mind the slowdown.

> ERROR: files left in build directory after distclean:
> ./confdefs.h

I don't see how this is related to the problem with 'core'.
It appears to be a separate bug.

For your immediate problem, the simplest thing might be
for you to rename the directory 'core', to 'Core', say.
If that's not possible, you could run 'configure' in
a subdirectory perhaps.


From MAILER-DAEMON Sat Dec 08 15:11:19 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThQk3-0002Vt-MQ
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 15:11:19 -0500
Received: from eggs.gnu.org ([208.118.235.92]:36046)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <frederic-emmanuel.picca@synchrotron-soleil.fr>)
	id 1ThOtT-0005Xn-CM
	for autoconf@gnu.org; Sat, 08 Dec 2012 13:12:58 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <frederic-emmanuel.picca@synchrotron-soleil.fr>)
	id 1ThOtQ-0004dG-U0
	for autoconf@gnu.org; Sat, 08 Dec 2012 13:12:55 -0500
Received: from dns.synchrotron-soleil.fr ([195.221.0.3]:50094
	helo=sucette.synchrotron-soleil.fr)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <frederic-emmanuel.picca@synchrotron-soleil.fr>)
	id 1ThOtQ-0004a2-Mu
	for autoconf@gnu.org; Sat, 08 Dec 2012 13:12:52 -0500
Received: from localhost (unknown [127.0.0.1])
	by sucette.synchrotron-soleil.fr (Postfix) with ESMTP id EBFC42C053;
	Sat,  8 Dec 2012 18:12:18 +0000 (UTC)
X-Virus-Scanned: amavisd-new at synchrotron-soleil.fr
Received: from sucette.synchrotron-soleil.fr ([127.0.0.1])
	by localhost (sucette.synchrotron-soleil.fr [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id vhxBKW0qEf+E; Sat,  8 Dec 2012 19:12:12 +0100 (CET)
Received: from SUN-CAS1.synchrotron-soleil.fr (unknown [195.221.0.169])
	by sucette.synchrotron-soleil.fr (Postfix) with ESMTP id 6023C2C037;
	Sat,  8 Dec 2012 19:12:12 +0100 (CET)
Received: from SUN-DAG1.synchrotron-soleil.fr ([169.254.1.207]) by
	SUN-CAS1.synchrotron-soleil.fr ([195.221.0.169]) with mapi id
	14.01.0289.001; Sat, 8 Dec 2012 19:12:12 +0100
From: =?iso-8859-1?Q?PICCA_Fr=E9d=E9ric-Emmanuel?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>
To: Paul Eggert <eggert@cs.ucla.edu>,
	"picca@debian.org" <picca@debian.org>
Subject: RE : rm -f core cause some troubles
Thread-Topic: rm -f core cause some troubles
Thread-Index: AQHN1WloQ5ir4Q45g0CuZpY0papTlZgPK+MI
Date: Sat, 8 Dec 2012 18:12:10 +0000
Message-ID: <A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>,
	<50C37888.2080002@cs.ucla.edu>
In-Reply-To: <50C37888.2080002@cs.ucla.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [195.221.0.18]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x
X-Received-From: 195.221.0.3
X-Mailman-Approved-At: Sat, 08 Dec 2012 15:11:19 -0500
Cc: "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 18:12:58 -0000

> That would slow down 'configure' everywhere.

how much ?

> It might make sense to have an Autoconf option that would
> add that behavior as an option, for people who want to have
> directories named 'core', and who don't mind the slowdown.

but if you add an option each time a directory name or other file is not al=
lowed...

> > ERROR: files left in build directory after distclean:
> > ./confdefs.h

> I don't see how this is related to the problem with 'core'.
> It appears to be a separate bug.

what can cause this problem, I find only this line in the configure script

# confdefs.h avoids OS command line length limits that DEFS can exceed.
rm -f -r conftest* confdefs.h

I renamed core -> Core, and this issue just gone.
=20
> For your immediate problem, the simplest thing might be
> for you to rename the directory 'core', to 'Core', say.
> If that's not possible, you could run 'configure' in
> a subdirectory perhaps.

I can not rename it as Core, I need to convince the upstream.
If I run configure in a subdirectory, everythings run fine the first time, =
then the
core/Makefile is created and the 'rm' problem is triggerred.

cheers,

Frederic=


From MAILER-DAEMON Sat Dec 08 15:13:19 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThQlz-0005cu-QV
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 15:13:19 -0500
Received: from eggs.gnu.org ([208.118.235.92]:51612)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThQlx-0005c2-Pf
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:13:18 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThQlw-0006za-T1
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:13:17 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:37366)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThQlw-0006zR-Mx
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:13:16 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 86FFA39E8106;
	Sat,  8 Dec 2012 12:13:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id haVWXGk07wFK; Sat,  8 Dec 2012 12:13:15 -0800 (PST)
Received: from [192.168.1.3] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 2CC2639E8008;
	Sat,  8 Dec 2012 12:13:15 -0800 (PST)
Message-ID: <50C39F60.7040702@cs.ucla.edu>
Date: Sat, 08 Dec 2012 12:13:20 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: =?UTF-8?B?UElDQ0EgRnLDqWTDqXJpYy1FbW1hbnVlbA==?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>
Subject: Re: RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>,
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
In-Reply-To: <A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: "picca@debian.org" <picca@debian.org>,
	"autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 20:13:19 -0000

On 12/08/2012 10:12 AM, PICCA Fr=C3=A9d=C3=A9ric-Emmanuel wrote:
>> That would slow down 'configure' everywhere.
>=20
> how much ?

I don't know.  I expect it'd be measurable, though.

> if you add an option each time a directory name or other file is not al=
lowed...

Yes, perhaps it's not a good idea.

> I renamed core -> Core, and this issue just gone.

I don't know why that would be, but perhaps more digging
on your end can find out.

Here's another idea.  Define your own 'rm',
which will be a simple shell script that invokes the
real 'rm', except it ignores any 'core' argument.  Put
it in your PATH, before the real 'rm'.  Then run
configure with that PATH.  That should work.

And here's another another idea.  When building
'configure', do it like this:

   autoconf
   sed 's/ core / /g' configure >config.cache
   cp config.cache configure

That way, your 'configure' won't try to remove 'core'.
It's a bit of a hack, but it should work.


From MAILER-DAEMON Sat Dec 08 15:31:18 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThR3O-0000T1-RR
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 15:31:18 -0500
Received: from eggs.gnu.org ([208.118.235.92]:54574)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <frederic-emmanuel.picca@synchrotron-soleil.fr>)
	id 1ThR3K-0000S3-Ab
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:31:17 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <frederic-emmanuel.picca@synchrotron-soleil.fr>)
	id 1ThR3H-0002yM-NO
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:31:14 -0500
Received: from dns2.synchrotron-soleil.fr ([195.221.0.6]:36082
	helo=raclette.synchrotron-soleil.fr)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <frederic-emmanuel.picca@synchrotron-soleil.fr>)
	id 1ThR3H-0002y4-GH
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:31:11 -0500
Received: from localhost (unknown [127.0.0.1])
	by raclette.synchrotron-soleil.fr (Postfix) with ESMTP id D882D30FB2;
	Sat,  8 Dec 2012 20:30:51 +0000 (UTC)
X-Virus-Scanned: amavisd-new at synchrotron-soleil.fr
Received: from raclette.synchrotron-soleil.fr ([127.0.0.1])
	by localhost (raclette.synchrotron-soleil.fr [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id GMDN1rUi1VMB; Sat,  8 Dec 2012 21:30:46 +0100 (CET)
Received: from SUN-CAS1.synchrotron-soleil.fr (unknown [195.221.0.169])
	by raclette.synchrotron-soleil.fr (Postfix) with ESMTP id E3C4530FA0;
	Sat,  8 Dec 2012 21:30:46 +0100 (CET)
Received: from SUN-DAG1.synchrotron-soleil.fr ([169.254.1.207]) by
	SUN-CAS1.synchrotron-soleil.fr ([195.221.0.169]) with mapi id
	14.01.0289.001; Sat, 8 Dec 2012 21:30:46 +0100
From: =?iso-8859-1?Q?PICCA_Fr=E9d=E9ric-Emmanuel?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>
To: Paul Eggert <eggert@cs.ucla.edu>
Subject: RE : RE : rm -f core cause some troubles
Thread-Topic: RE : rm -f core cause some troubles
Thread-Index: AQHN1WloQ5ir4Q45g0CuZpY0papTlZgPK+MIgAAZdQCAABNhwg==
Date: Sat, 8 Dec 2012 20:30:46 +0000
Message-ID: <A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>,
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>,
	<50C39F60.7040702@cs.ucla.edu>
In-Reply-To: <50C39F60.7040702@cs.ucla.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [195.221.0.18]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x
X-Received-From: 195.221.0.6
Cc: "picca@debian.org" <picca@debian.org>,
	"autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 20:31:17 -0000

> > I renamed core -> Core, and this issue just gone.

> I don't know why that would be, but perhaps more digging
> on your end can find out.

Yes I need to investigate on this

> Here's another idea.  Define your own 'rm',
> which will be a simple shell script that invokes the
> real 'rm', except it ignores any 'core' argument.  Put
> it in your PATH, before the real 'rm'.  Then run
> configure with that PATH.  That should work.

yes this could work but it is really a nasty hack...

> And here's another another idea.  When building
> 'configure', do it like this:

>   autoconf
>   sed 's/ core / /g' configure >config.cache
>   cp config.cache configure

> That way, your 'configure' won't try to remove 'core'.
> It's a bit of a hack, but it should work.

You mean , I need to maintain a fork of autoconf for this project ;)
To me even if this is slower, the right fix is to avoid removing core if th=
is is a directory.
It will be difficult for me to convince upstream to use autoconf if it need=
s to change it's
code due to this bug.

cheers,

Frederic


From MAILER-DAEMON Sat Dec 08 15:38:14 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThRA6-0001WU-GV
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 15:38:14 -0500
Received: from eggs.gnu.org ([208.118.235.92]:55231)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1ThRA4-0001Vx-Bz
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:38:13 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1ThRA3-0004Bo-6V
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:38:12 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:43882)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1ThRA2-0004Ba-VU
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:38:11 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qB8KbuOW017619; Sat, 8 Dec 2012 14:37:56 -0600 (CST)
Date: Sat, 8 Dec 2012 14:37:56 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: rm -f core cause some troubles
In-Reply-To: <50C37888.2080002@cs.ucla.edu>
Message-ID: <alpine.GSO.2.01.1212081435580.19664@freddy.simplesystems.org>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Sat, 08 Dec 2012 14:37:56 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 20:38:13 -0000

On Sat, 8 Dec 2012, Paul Eggert wrote:
>
> For your immediate problem, the simplest thing might be
> for you to rename the directory 'core', to 'Core', say.
> If that's not possible, you could run 'configure' in
> a subdirectory perhaps.

Renaming to 'Core' would likely not be suitable for Microsoft Windows 
and other case-insensitive systems where 'Core' is treated the same as 
'core'.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Sat Dec 08 15:48:34 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThRK6-0003AI-RW
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 15:48:34 -0500
Received: from eggs.gnu.org ([208.118.235.92]:56361)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jhawk@mit.edu>) id 1ThRK4-00038j-Cl
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:48:33 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jhawk@mit.edu>) id 1ThRK3-0006dH-I6
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:48:32 -0500
Received: from dmz-mailsec-scanner-3.mit.edu ([18.9.25.14]:53578)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jhawk@mit.edu>) id 1ThRK3-0006dA-E0
	for autoconf@gnu.org; Sat, 08 Dec 2012 15:48:31 -0500
X-AuditID: 1209190e-b7f516d0000008e4-9f-50c3a79d4dc4
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39])
	by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP
	id DE.56.02276.D97A3C05; Sat,  8 Dec 2012 15:48:29 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id qB8KmTiQ032011; 
	Sat, 8 Dec 2012 15:48:29 -0500
Received: from localhost (CONTENTS-VNDER-PRESSVRE.MIT.EDU [18.9.64.11])
	(authenticated bits=0) (User authenticated as jhawk@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qB8KmRee019043;
	Sat, 8 Dec 2012 15:48:28 -0500 (EST)
Date: Sat, 8 Dec 2012 15:48:27 -0500
From: John Hawkinson <jhawk@MIT.EDU>
To: autoconf@gnu.org
Subject: Re: rm -f core cause some troubles
Message-ID: <20121208204827.GL1032@ringworld.MIT.EDU>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50C37888.2080002@cs.ucla.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBIsWRmVeSWpSXmKPExsUixG6nrjt3+eEAg+lb9S0aH31ns3g9pYXV
	gcmjbZqZx8KHPYwBTFFcNimpOZllqUX6dglcGV1nJ7EVXGWq6Jp8nqmBcRpTFyMnh4SAicST
	549YIWwxiQv31rN1MXJxCAnsY5R4cWU2C4SznlHi6sTrzBBOI5PE6RdNYO0sAioSq9esZgGx
	2YDsOd9vsoPYIgIiEr/7pgI1cHAIC2hLdB0TBQnzCphK7N31kA3EFhIIllhyZBY7RFxQ4uTM
	J2BjmAW0JG78e8kE0sosIC2x/B8HiMkJNKXjrjBIhSjQoiknt7FNYBSYhaR5FpLmWQjNCxiZ
	VzHKpuRW6eYmZuYUpybrFicn5uWlFuka6+VmluilppRuYgQFKKck3w7GrweVDjEKcDAq8fDe
	EDkUIMSaWFZcmXuIUZKDSUmU99DiwwFCfEn5KZUZicUZ8UWlOanFhxglOJiVRHhflgPleFMS
	K6tSi/JhUtIcLErivFdSbvoLCaQnlqRmp6YWpBbBZGU4OJQkeFcsA2oULEpNT61Iy8wpQUgz
	cXCCDOcBGr4apIa3uCAxtzgzHSJ/ilFRSpx3M0hCACSRUZoH1wtLIK8YxYFeEebdBVLFA0w+
	cN2vgAYzAQ0+KQg2uCQRISXVwNizSeKm/WGtL4w9hrwqd49l8NzMajEo488MVZ+ZUrw/0v6g
	5a3KzyeqvF4zuQn1rultZfJsbU/JTr+wz4In5VJ2dvvNBe43fBneq2sceae9d/b04rR85rvu
	+ye8lN0vWPNdZKr6urvLfN/bxMsfiLVIOcHmFXZKUE1CMXOT7CLVhd5ZOXEFSizFGYmGWsxF
	xYkAe/fj0vsCAAA=
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 18.9.25.14
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 20:48:33 -0000

autoconf should not help programmers write packages that
support "core" as a directory name. That's just going to cause
problems on traditional unix systems. Do not use directory
(or filenames) called "core" if your software is intended to be
portable!

This package should rename this directory.

--jhawk@mit.edu
  John Hawkinson


From MAILER-DAEMON Sat Dec 08 16:01:33 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThRWf-00056I-Ba
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 16:01:33 -0500
Received: from eggs.gnu.org ([208.118.235.92]:57260)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1ThRWc-00054d-Mj
	for Autoconf@gnu.org; Sat, 08 Dec 2012 16:01:31 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1ThRWb-0000x5-5F
	for Autoconf@gnu.org; Sat, 08 Dec 2012 16:01:30 -0500
Received: from mx.meyering.net ([88.168.87.75]:44998)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1ThRWa-0000wv-Uw
	for Autoconf@gnu.org; Sat, 08 Dec 2012 16:01:29 -0500
Received: from rho.meyering.net (rho.meyering.net [127.0.0.1])
	by rho.meyering.net (Acme Bit-Twister) with ESMTP id 343A96036B;
	Sat,  8 Dec 2012 22:01:28 +0100 (CET)
From: Jim Meyering <jim@meyering.net>
To: Marko Lindqvist <cazfi74@gmail.com>
Subject: Re: Future autoconf package compression
In-Reply-To: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	(Marko Lindqvist's message of "Sat, 24 Nov 2012 10:16:06 +0200")
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
Date: Sat, 08 Dec 2012 22:01:28 +0100
Message-ID: <87zk1oqmvr.fsf@rho.meyering.net>
Lines: 30
MIME-Version: 1.0
Content-Type: text/plain
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 88.168.87.75
Cc: Autoconf <Autoconf@gnu.org>, Eric Blake <eblake@redhat.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 21:01:32 -0000

Marko Lindqvist wrote:
> On 2 March 2012 06:45, Eric Blake <eblake@redhat.com> wrote:
>>
>> The Autoconf team is considering releasing only .xz files for 2.69; if
>> this would be a hardship for you, and you need the .gz or .bz2 release,
>> please speak up now.
>
>  I just encountered new argument for providing .gz of autoconf also in
> the future.
>
>  I were updating automake version used in OpenEmbedded, and though to
> switch from tar.gz to tar.xz package while at it. That failed because
> of circular dependency. In short: building xz decompressor requires
> automake.

Hi Marko,

I have simulated building xz with a broken version of automake:
(similar to when automake is not installed)

    wget http://www.tukaani.org/xz/xz-5.0.4.tar.xz
    tar xf xz-5.0.4.tar.xz
    cd xz-5.0.4
    mkdir x; printf '#!/bin/sh\nexit 1\n' > x/automake; chmod a+x x/automake
    PATH=x:$PATH ./configure && make && make check

All of those commands succeeded, so it is clear to me that building
xz that way does not depend on automake.

Jim


From MAILER-DAEMON Sat Dec 08 16:15:43 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThRkM-0007ED-Vu
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 16:15:42 -0500
Received: from eggs.gnu.org ([208.118.235.92]:58414)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1ThRkL-0007E7-35
	for Autoconf@gnu.org; Sat, 08 Dec 2012 16:15:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1ThRkJ-00046P-MW
	for Autoconf@gnu.org; Sat, 08 Dec 2012 16:15:40 -0500
Received: from mx.meyering.net ([88.168.87.75]:45017)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1ThRkJ-00046L-FS
	for Autoconf@gnu.org; Sat, 08 Dec 2012 16:15:39 -0500
Received: from rho.meyering.net (rho.meyering.net [127.0.0.1])
	by rho.meyering.net (Acme Bit-Twister) with ESMTP id CFBFC600E3;
	Sat,  8 Dec 2012 22:15:38 +0100 (CET)
From: Jim Meyering <jim@meyering.net>
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Subject: Re: Future autoconf package compression
In-Reply-To: <alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
	(Bob Friesenhahn's message of "Sat, 24 Nov 2012 09:45:39 -0600 (CST)")
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
Date: Sat, 08 Dec 2012 22:15:38 +0100
Message-ID: <87txrwqm85.fsf@rho.meyering.net>
Lines: 42
MIME-Version: 1.0
Content-Type: text/plain
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 88.168.87.75
Cc: Autoconf <Autoconf@gnu.org>, Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 21:15:42 -0000

Bob Friesenhahn wrote:
> On Sat, 24 Nov 2012, Marko Lindqvist wrote:
>> On 2 March 2012 06:45, Eric Blake <eblake@redhat.com> wrote:
>>>
>>> The Autoconf team is considering releasing only .xz files for 2.69; if
>>> this would be a hardship for you, and you need the .gz or .bz2 release,
>>> please speak up now.
>>
>> I just encountered new argument for providing .gz of autoconf also in
>> the future.
>
> There is no tangible benefit offered to the world by removing the
> gzip-compressed autoconf package.  Xz is excessively complex,
> excessively large, and has limited portability and stability compared
> with gzip.

Hi Bob,

I don't know of significant portability problems.
In my experience, if they are reported and affect significant
(sometimes even insignificant) portability targets, they will be
addressed promptly.  Can you point to reported problems that
have not been resolved?

There is no shortage of reasons to avoid gzip these days.  One that
strikes home for me (as a package maintainer) is that there have
been exploitable CVEs against gzip in the recent past, and the code
is surprisingly ugly (hence hard to audit).  I do not want to require
tarball consumers to use a tool that I do not feel good about, and gzip
is one of those.  Just because it is still used by so many people (due
mostly to inertia) does not mean that we should ignore its faults.

> The XZ Utils project obviously has issues.  As an example, I clicked
> on the NEWS link offered by its web site (http://www.tukaani.org/xz/)
> to see what has changed and saw this
> "http://git.tukaani.org/?p=xz.git;a=blob;f=NEWS;hb=HEAD".  Further
> investigation reveals that its git repository has vaporized.

While reading your message (catching up, now), I clicked on
that link, and it works fine now.  Even if the site were off-line
for a few days, that is no reason to reject the technology.
If we did that across the board, very few projects would still be with us.


From MAILER-DAEMON Sat Dec 08 18:45:12 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThU52-0003eC-TS
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 18:45:12 -0500
Received: from eggs.gnu.org ([208.118.235.92]:47001)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThU50-0003cR-M6
	for autoconf@gnu.org; Sat, 08 Dec 2012 18:45:11 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThU4z-0002u5-K1
	for autoconf@gnu.org; Sat, 08 Dec 2012 18:45:10 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:43594)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThU4z-0002ty-Eh
	for autoconf@gnu.org; Sat, 08 Dec 2012 18:45:09 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 1D80039E810A;
	Sat,  8 Dec 2012 15:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R2A8lxenG3+q; Sat,  8 Dec 2012 15:45:07 -0800 (PST)
Received: from [192.168.1.3] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id A1F4F39E8106;
	Sat,  8 Dec 2012 15:45:07 -0800 (PST)
Message-ID: <50C3D10A.3000604@cs.ucla.edu>
Date: Sat, 08 Dec 2012 15:45:14 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: =?UTF-8?B?UElDQ0EgRnLDqWTDqXJpYy1FbW1hbnVlbA==?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>
Subject: Re: RE : RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>,
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>,
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
In-Reply-To: <A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: "picca@debian.org" <picca@debian.org>,
	"autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Dec 2012 23:45:11 -0000

On 12/08/2012 12:30 PM, PICCA Fr=C3=A9d=C3=A9ric-Emmanuel wrote:
> You mean , I need to maintain a fork of autoconf for this project ;)

No, you don't need to change autoconf at all.
You merely edit its output, with 'sed',
before running it.  It's easy.

> the right fix is to avoid removing core if this is a directory.

Autoconf-generated 'configure' files already do that.
That's not the issue.

The only issue that has been identified is that
'configure' issues some annoying warnings.  There may be
some other issues, but that's all we've found so far.
And the above-mentioned fix resolves that issue.


From MAILER-DAEMON Sat Dec 08 19:12:42 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThUVd-0000m6-Vp
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 19:12:41 -0500
Received: from eggs.gnu.org ([208.118.235.92]:50114)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1ThUVc-0000m0-6G
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:12:41 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1ThUVb-0000W4-5Q
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:12:40 -0500
Received: from mail-ia0-f175.google.com ([209.85.210.175]:43995)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1ThUVb-0000Vy-0d
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:12:39 -0500
Received: by mail-ia0-f175.google.com with SMTP id z3so2710413iad.20
	for <autoconf@gnu.org>; Sat, 08 Dec 2012 16:12:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=cTaiQO/3mB9VBjXbZR5NsADfyK/AaOjYeTjiYavbgek=;
	b=Ak1sJIoOOaqidefmfTHK61BJLJ2QTShyVHbWunLQbczTSZfYL3rXu5T6Hs+cyGU23z
	4Azj7n/suUGpgvV/RASu9kOhe9d9nInCvRFQPTkbi4vI/4AbgT0lmVDHGBXEqtR6/9+y
	nV0bi2UfAEpVNOFRMLEr0axzcSzCdQ7VuiBtHgeza2iiDgq8Qr3ktQCY9eAD6Po2TFrx
	/3A0OnN4E0LNoV/9PPglNcJ13kHt8v29BzHSzUtGBkh4JI2If8Hm3GoTt/0iYKO/ttGm
	0ECV4gwVjDC1I+EtkRqzplJwf2iuOapUk9BdozcVet9nAc3C6tjDszGd8+HiW+vF7Phr
	XlZQ==
MIME-Version: 1.0
Received: by 10.50.152.132 with SMTP id uy4mr2950676igb.3.1355011958185; Sat,
	08 Dec 2012 16:12:38 -0800 (PST)
Received: by 10.64.24.175 with HTTP; Sat, 8 Dec 2012 16:12:38 -0800 (PST)
In-Reply-To: <50C3D10A.3000604@cs.ucla.edu>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
Date: Sun, 9 Dec 2012 02:12:38 +0200
Message-ID: <CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
From: Marko Lindqvist <cazfi74@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.210.175
Cc: =?UTF-8?Q?PICCA_Fr=C3=A9d=C3=A9ric=2DEmmanuel?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>,
	"picca@debian.org" <picca@debian.org>,
	"autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 00:12:41 -0000

On 9 December 2012 01:45, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 12/08/2012 12:30 PM, PICCA Fr=C3=A9d=C3=A9ric-Emmanuel wrote:
>
>> the right fix is to avoid removing core if this is a directory.
>
> Autoconf-generated 'configure' files already do that.
> That's not the issue.
>
> The only issue that has been identified is that
> 'configure' issues some annoying warnings.

 So you are saing that "we try to do the wrong thing, but as that
reliably fails, only problem are the error messages from the failure
(to do the wrong thing)"?

 As hackish solutions go, I'd consider this particular way of thinking
bad. If reliability of the normal use increases -> failure happens
less reliably when it's hackishly counted on.


 - ML


From MAILER-DAEMON Sat Dec 08 19:13:33 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThUWT-000139-6a
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 19:13:33 -0500
Received: from eggs.gnu.org ([208.118.235.92]:50256)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThUWR-000132-RO
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:13:32 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThUWQ-0000cc-TF
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:13:31 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:44498)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1ThUWQ-0000cY-NX
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:13:30 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id DC00A39E8106;
	Sat,  8 Dec 2012 16:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2A0k5jcs7UMO; Sat,  8 Dec 2012 16:13:29 -0800 (PST)
Received: from [192.168.1.3] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 6C7B439E8008;
	Sat,  8 Dec 2012 16:13:29 -0800 (PST)
Message-ID: <50C3D7B0.8060909@cs.ucla.edu>
Date: Sat, 08 Dec 2012 16:13:36 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Marko Lindqvist <cazfi74@gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
In-Reply-To: <CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: =?UTF-8?B?UElDQ0EgRnLDqWTDqXJpYy1FbW1hbnVlbA==?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>,
	"picca@debian.org" <picca@debian.org>,
	"autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 00:13:32 -0000

On 12/08/2012 04:12 PM, Marko Lindqvist wrote:
> So you are saing that

No.


From MAILER-DAEMON Sat Dec 08 19:16:48 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThUZc-0001cp-Nt
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 19:16:48 -0500
Received: from eggs.gnu.org ([208.118.235.92]:50623)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1ThUZb-0001cj-BC
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:16:48 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1ThUZX-0001Mb-R6
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:16:47 -0500
Received: from mail-vb0-f41.google.com ([209.85.212.41]:33637)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1ThUZX-0001MW-Ml
	for autoconf@gnu.org; Sat, 08 Dec 2012 19:16:43 -0500
Received: by mail-vb0-f41.google.com with SMTP id l22so1789778vbn.0
	for <autoconf@gnu.org>; Sat, 08 Dec 2012 16:16:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type:content-transfer-encoding;
	bh=kvG7Vyn716jM/r8FlQwSnkXAHlr1LX7BV2NmKfk2l2I=;
	b=0bRiKwgsPcVCr7WpV1KkJybqAGtKYXBEug2mhjbIMUmeIicWKWypdM7Bs9gYq7qBvb
	sjxz8/K0t+jcdvuer27wt4JZMMwMP7UZ13T7GmOywt0VgJ3pKkQeaQbCFWSRvQMJ3FFP
	JoNefnF5Mgy/qJ+44tNkfgoO6F/IE+Pbv6G/iVcK0/hU2CJIgC2CR77NMTm/TEnEXUbH
	MnvbMMMM7Ye3Wqd+9KZcOW3+DG7qFW93HAwT1lzLWVbJKLkgm8n1nqKrmYGjx5UXeqGT
	juHdAbP53oZt6SpF4AqvxhGs/aMPXshiEhsIkuI9zg+wMBXs4I54CoWjHtL76vr5Ejd8
	AQ4A==
MIME-Version: 1.0
Received: by 10.52.17.70 with SMTP id m6mr5625737vdd.92.1355012203012; Sat, 08
	Dec 2012 16:16:43 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Sat, 8 Dec 2012 16:16:42 -0800 (PST)
In-Reply-To: <CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
Date: Sat, 8 Dec 2012 19:16:42 -0500
Message-ID: <CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
From: Jeffrey Walton <noloader@gmail.com>
To: Marko Lindqvist <cazfi74@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.41
Cc: =?UTF-8?Q?PICCA_Fr=C3=A9d=C3=A9ric=2DEmmanuel?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>,
	Paul Eggert <eggert@cs.ucla.edu>, "autoconf@gnu.org" <autoconf@gnu.org>,
	"picca@debian.org" <picca@debian.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 00:16:48 -0000

On Sat, Dec 8, 2012 at 7:12 PM, Marko Lindqvist <cazfi74@gmail.com> wrote:
> On 9 December 2012 01:45, Paul Eggert <eggert@cs.ucla.edu> wrote:
>> On 12/08/2012 12:30 PM, PICCA Fr=C3=A9d=C3=A9ric-Emmanuel wrote:
>>
>>> the right fix is to avoid removing core if this is a directory.
>>
>> Autoconf-generated 'configure' files already do that.
>> That's not the issue.
>>
>> The only issue that has been identified is that
>> 'configure' issues some annoying warnings.
>
>  So you are saing that "we try to do the wrong thing, but as that
> reliably fails, only problem are the error messages from the failure
> (to do the wrong thing)"?
>
>  As hackish solutions go, I'd consider this particular way of thinking
> bad. If reliability of the normal use increases -> failure happens
> less reliably when it's hackishly counted on.
Agreed. Before anything, the program has to be correct. Trying to
remove a directory named 'core' does not follow the intention
(informally 'specification') of removing crash dump files.

Special rules (i.e., no 'core' directories) that can only be found by
grepping mailing lists also seems to be less than desirable.

What happens if a user aliases `rm` to `rm -rf`?

Jeff


From MAILER-DAEMON Sat Dec 08 20:13:38 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThVSc-0000HM-Bs
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 20:13:38 -0500
Received: from eggs.gnu.org ([208.118.235.92]:59133)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1ThVSZ-0000E8-IM
	for Autoconf@gnu.org; Sat, 08 Dec 2012 20:13:36 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1ThVSY-0005us-6e
	for Autoconf@gnu.org; Sat, 08 Dec 2012 20:13:35 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:44574)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1ThVSX-0005ul-Uj
	for Autoconf@gnu.org; Sat, 08 Dec 2012 20:13:34 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qB91DUEg018464; Sat, 8 Dec 2012 19:13:31 -0600 (CST)
Date: Sat, 8 Dec 2012 19:13:30 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Jim Meyering <jim@meyering.net>
Subject: Re: Future autoconf package compression
In-Reply-To: <87txrwqm85.fsf@rho.meyering.net>
Message-ID: <alpine.GSO.2.01.1212081848590.19664@freddy.simplesystems.org>
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
	<87txrwqm85.fsf@rho.meyering.net>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Sat, 08 Dec 2012 19:13:31 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: Autoconf <Autoconf@gnu.org>, Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 01:13:36 -0000

On Sat, 8 Dec 2012, Jim Meyering wrote:
>>>
>>> I just encountered new argument for providing .gz of autoconf also in
>>> the future.
>>
>> There is no tangible benefit offered to the world by removing the
>> gzip-compressed autoconf package.  Xz is excessively complex,
>> excessively large, and has limited portability and stability compared
>> with gzip.
>
> Hi Bob,
>
> I don't know of significant portability problems.
> In my experience, if they are reported and affect significant
> (sometimes even insignificant) portability targets, they will be
> addressed promptly.  Can you point to reported problems that
> have not been resolved?

As far as I am aware, xz still fails to link successfully under x86 
(x86-64 kernel) Solaris when built with GCC since xz requests to build 
the objects with some special addressing model.  This is a well known 
issue (see 
http://sourceforge.net/projects/lzmautils/forums/forum/708858/topic/3500014). 
The documented workaround does not work properly. In order to 
circumvent the issue, I had to use the commercial Oracle compiler.  I 
have not encountered any other software with this sort of issue.

> There is no shortage of reasons to avoid gzip these days.  One that
> strikes home for me (as a package maintainer) is that there have
> been exploitable CVEs against gzip in the recent past, and the code
> is surprisingly ugly (hence hard to audit).  I do not want to require

This may indeed be true.  However, if autoconf itself stops using gzip 
then the effect on the world will be imperceptible except that people 
who want to install autoconf and who don't have 'xz' will suffer.  If 
Automake (and GNU tar) was to refuse to create gzip archives, and new 
gzip releases could only decompress, then there would be noticeable 
impact.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Sat Dec 08 20:51:04 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThW2p-0001xC-WD
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 20:51:04 -0500
Received: from eggs.gnu.org ([208.118.235.92]:36300)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1ThW2n-0001x3-44
	for Autoconf@gnu.org; Sat, 08 Dec 2012 20:51:02 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1ThW2l-0005Zp-Lc
	for Autoconf@gnu.org; Sat, 08 Dec 2012 20:51:01 -0500
Received: from mail-ie0-f169.google.com ([209.85.223.169]:35746)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1ThW2l-0005Zl-Gf
	for Autoconf@gnu.org; Sat, 08 Dec 2012 20:50:59 -0500
Received: by mail-ie0-f169.google.com with SMTP id c14so6070732ieb.0
	for <Autoconf@gnu.org>; Sat, 08 Dec 2012 17:50:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=u213+sqEJnm5i8Z/f9xWAX7NSN35+XHqGvXd3kw6xSI=;
	b=OxqyYIn2JreRS+ox2DK86IqiZrLg4o1oM0IHm+89jwbJwwiK8Y3QtbREkDqCAREU4v
	cfwFKJYGQQz2ojt0l2Dgbbw1nBg+/7FdJJhhEXE1FtKm6m/hwj7ycdESORorBxGU9n9J
	jSlMWC0p/KuW7f2kHs8QB6YSnZ2Q00b+iPM/ocOCzKiBbebR49mLKfODNFoexh9zcI+A
	UEXZ6lnyYkUgHdCJ/8nU7uqKWKv9ALI2GYR5zY9O1m1xOkl/s2Mr8jQ2t5Yp4KwqaHP+
	mfXMTzr15W2xiVfAyX5WcO+hHtI8ez9ubzlf24es2sbNpeN+CnhCj1JkHVUatLxWaLni
	hkMg==
MIME-Version: 1.0
Received: by 10.50.153.169 with SMTP id vh9mr2874845igb.67.1355017858736; Sat,
	08 Dec 2012 17:50:58 -0800 (PST)
Received: by 10.64.24.175 with HTTP; Sat, 8 Dec 2012 17:50:58 -0800 (PST)
In-Reply-To: <87zk1oqmvr.fsf@rho.meyering.net>
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<87zk1oqmvr.fsf@rho.meyering.net>
Date: Sun, 9 Dec 2012 03:50:58 +0200
Message-ID: <CAF6bG8da36wWd4m3Z9HxtaOPQ5v4NkxcK=i6ubYWcz+6xE8OSw@mail.gmail.com>
Subject: Re: Future autoconf package compression
From: Marko Lindqvist <cazfi74@gmail.com>
To: Jim Meyering <jim@meyering.net>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.223.169
Cc: Autoconf <Autoconf@gnu.org>, Eric Blake <eblake@redhat.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 01:51:02 -0000

On 8 December 2012 23:01, Jim Meyering <jim@meyering.net> wrote:
> Marko Lindqvist wrote:
>> On 2 March 2012 06:45, Eric Blake <eblake@redhat.com> wrote:
>>>
>>> The Autoconf team is considering releasing only .xz files for 2.69; if
>>> this would be a hardship for you, and you need the .gz or .bz2 release,
>>> please speak up now.
>>
>>  I just encountered new argument for providing .gz of autoconf also in
>> the future.
>>
>>  I were updating automake version used in OpenEmbedded, and though to
>> switch from tar.gz to tar.xz package while at it. That failed because
>> of circular dependency. In short: building xz decompressor requires
>> automake.
>
> Hi Marko,
>
> I have simulated building xz with a broken version of automake:
> (similar to when automake is not installed)
>
>     wget http://www.tukaani.org/xz/xz-5.0.4.tar.xz
>     tar xf xz-5.0.4.tar.xz
>     cd xz-5.0.4
>     mkdir x; printf '#!/bin/sh\nexit 1\n' > x/automake; chmod a+x x/automake
>     PATH=x:$PATH ./configure && make && make check
>
> All of those commands succeeded, so it is clear to me that building
> xz that way does not depend on automake.

 The fact that I were talking about OpenEmbedded build is significant.
OpenEmbedded adds the dependency. AFAIK every tool (autotools, xz,
OpenEmbedded) works correctly as designed, but there's conflict
between their designs.
 I have no power to make changes to any of the projects - I can only
suggest things, but overall I think it's OpenEmbedded where changes
should be made (and are easiest to make). But until we have right
thing(tm) fix in place, simply providing also gzip compressed tarballs
of autotools would workaround the problem.


 - ML


From MAILER-DAEMON Sat Dec 08 22:17:59 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1ThXOx-0005Pk-89
	for mharc-autoconf@gnu.org; Sat, 08 Dec 2012 22:17:59 -0500
Received: from eggs.gnu.org ([208.118.235.92]:44428)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1ThXOt-0005Pb-9l
	for autoconf@gnu.org; Sat, 08 Dec 2012 22:17:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1ThXOs-0006tk-1p
	for autoconf@gnu.org; Sat, 08 Dec 2012 22:17:55 -0500
Received: from mail-vc0-f169.google.com ([209.85.220.169]:44754)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1ThXOr-0006tg-R3
	for autoconf@gnu.org; Sat, 08 Dec 2012 22:17:53 -0500
Received: by mail-vc0-f169.google.com with SMTP id gb23so1818570vcb.0
	for <autoconf@gnu.org>; Sat, 08 Dec 2012 19:17:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=hFODYX20RPrCB+kQI/UfrAGPnc8fxRf0Xejvjjjd4Uk=;
	b=JVFqMbe3N+AjTQpxue46TlXwQQ2QfZKtDiGgsRCk7bMPt9hL1ftyqWJtcFHtdAkCcy
	yOsFWgZhqcNczJPet3Pz2+2UDbxPeFFEAYDlWbHRws1q5kUUqVMJ7G+rvByMLDrYsMeu
	NxRcMdB9XwE15uwwVHDmvVrHO7JyP3QyU08B5aRIucOLWI67Y+3T3mEYkcxExWbBX5sA
	Pnwu2p0RhHIQcW4wGD/MnmwEClvI8skTSCuTPuCsieDad+lRbmpcWFqA9uq8eOA3fdT4
	zcFuIsyo+SOxihpeukbUWRAtSv8zs3EOyt2t4e+Z3oYd6Fa4GDVj0Y2NV4NzvZMAQT4R
	4G9g==
MIME-Version: 1.0
Received: by 10.220.218.197 with SMTP id hr5mr6503704vcb.8.1355023073451; Sat,
	08 Dec 2012 19:17:53 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Sat, 8 Dec 2012 19:17:53 -0800 (PST)
In-Reply-To: <alpine.GSO.2.01.1212081435580.19664@freddy.simplesystems.org>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<alpine.GSO.2.01.1212081435580.19664@freddy.simplesystems.org>
Date: Sat, 8 Dec 2012 22:17:53 -0500
Message-ID: <CAH8yC8mazsVBsrY9WwOyNnpA4NedhtvvfxiWvAKyBKXOouB12w@mail.gmail.com>
Subject: Re: rm -f core cause some troubles
From: Jeffrey Walton <noloader@gmail.com>
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.220.169
Cc: Paul Eggert <eggert@cs.ucla.edu>, autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 03:17:57 -0000

On Sat, Dec 8, 2012 at 3:37 PM, Bob Friesenhahn
<bfriesen@simple.dallas.tx.us> wrote:
> On Sat, 8 Dec 2012, Paul Eggert wrote:
>>
>> For your immediate problem, the simplest thing might be
>> for you to rename the directory 'core', to 'Core', say.
>> If that's not possible, you could run 'configure' in
>> a subdirectory perhaps.
>
> Renaming to 'Core' would likely not be suitable for Microsoft Windows and
> other case-insensitive systems where 'Core' is treated the same as 'core'.
Apple, too. https://www.google.com/#q=case+sensitive+filesystem+site:apple.com


From MAILER-DAEMON Mon Dec 10 08:36:40 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Ti3XE-0002aH-Jk
	for mharc-autoconf@gnu.org; Mon, 10 Dec 2012 08:36:40 -0500
Received: from eggs.gnu.org ([208.118.235.92]:55411)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1Ti3X7-0002YD-2E
	for autoconf@gnu.org; Mon, 10 Dec 2012 08:36:39 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1Ti3X2-0003SO-NG
	for autoconf@gnu.org; Mon, 10 Dec 2012 08:36:32 -0500
Received: from mx1.redhat.com ([209.132.183.28]:16439)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1Ti3X2-0003SB-FS
	for autoconf@gnu.org; Mon, 10 Dec 2012 08:36:28 -0500
Received: from int-mx11.intmail.prod.int.phx2.redhat.com
	(int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qBADaGpl002347
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 10 Dec 2012 08:36:16 -0500
Received: from [10.3.112.2] ([10.3.112.2])
	by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP
	id qBADaEJi030188; Mon, 10 Dec 2012 08:36:15 -0500
Message-ID: <50C5E54E.1080103@redhat.com>
Date: Mon, 10 Dec 2012 06:36:14 -0700
From: Eric Blake <eblake@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: noloader@gmail.com
Subject: Re: RE : RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
In-Reply-To: <CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature";
	boundary="------------enigE1C87BBBF3B3FCC2E1263EE2"
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 209.132.183.28
Cc: "picca@debian.org" <picca@debian.org>,
	=?UTF-8?B?UElDQ0EgRnLDqWTDqXJpYy0=?= =?UTF-8?B?RW1tYW51ZWw=?=
	<frederic-emmanuel.picca@synchrotron-soleil.fr>,
	Paul Eggert <eggert@cs.ucla.edu>, "autoconf@gnu.org" <autoconf@gnu.org>,
	Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 13:36:39 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE1C87BBBF3B3FCC2E1263EE2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/08/2012 05:16 PM, Jeffrey Walton wrote:
> Agreed. Before anything, the program has to be correct. Trying to
> remove a directory named 'core' does not follow the intention
> (informally 'specification') of removing crash dump files.

Naming a directory 'core' is dangerous and non-portable, because the
name 'core' is traditionally reserved for core dumps.  Similarly, naming
a directory 'aux' is dangerous and non-portable, because the name 'aux'
opens a special device on Windows.  Similarly, naming two files with a
case-sensitive clash is unsupported.  In short, autoconf sticks with the
philosophy that it is better for you to name your files portably than
for autoconf to bend over backward to special case when those
non-portable names exist on platforms where they happen to work, but
will fall apart on platforms where they do not work.

>=20
> Special rules (i.e., no 'core' directories) that can only be found by
> grepping mailing lists also seems to be less than desirable.

If you think we need to more fully document that both 'core' and 'aux'
are recommended to be avoided in your project, patches are welcome.

>=20
> What happens if a user aliases `rm` to `rm -rf`?

Precisely why we are suggesting that you should fix your package to
avoid 'core' as a directory, and not that we fix 'autoconf' to bend over
backwards to support this fringe case.

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--------------enigE1C87BBBF3B3FCC2E1263EE2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBCAAGBQJQxeVOAAoJEKeha0olJ0NqQJUH/0JzHX5mhS72/FRfovTEvwoJ
iiXk99eyY3xfAjS3W2NIng3JgNZ6TnyZjkcebb5va4Xr41w/u4dC9NgjWvmBnG24
0NgM6DJ4xZH0XskQ9S/hxs6CO6lW+4IRY1+1gHZDFIzZPCqZnwPsTtznmJWry9St
HjgNT3Xk3z9I/peGMVYS9lg/PJmozDM6mdl92Sxl5Hotzb3K03X7WPUq7HKFr+at
CmfFq0oK3BKuqrzSpbk26ITPaKz9TY1kObFua+W3gEJaggB+9xGVcKhBfla26SVL
mlKBbzV0yUHP/Ojijh0PJBT67JpKQ+ajwgNq7CBZ6Th5nN1a4+KL0CnbBFSeXos=
=11pb
-----END PGP SIGNATURE-----

--------------enigE1C87BBBF3B3FCC2E1263EE2--


From MAILER-DAEMON Thu Dec 13 07:58:46 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tj8NC-0004x2-3A
	for mharc-autoconf@gnu.org; Thu, 13 Dec 2012 07:58:46 -0500
Received: from eggs.gnu.org ([208.118.235.92]:33363)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefano.lattarini@gmail.com>) id 1Tj8N7-0004uT-4a
	for Autoconf@gnu.org; Thu, 13 Dec 2012 07:58:44 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefano.lattarini@gmail.com>) id 1Tj8N2-0004XK-89
	for Autoconf@gnu.org; Thu, 13 Dec 2012 07:58:41 -0500
Received: from mail-la0-f41.google.com ([209.85.215.41]:34699)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefano.lattarini@gmail.com>) id 1Tj8N1-0004XA-V6
	for Autoconf@gnu.org; Thu, 13 Dec 2012 07:58:36 -0500
Received: by mail-la0-f41.google.com with SMTP id m15so1693130lah.0
	for <Autoconf@gnu.org>; Thu, 13 Dec 2012 04:58:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=Pw5GjXSBNC1bFrzO3o72zvJnUPQKRIP0v85pt6Y3x3U=;
	b=n0QSWvT2xCQQMKRxoyGfzPTrfWVr0RqD4H9pGzP/X63l4qbYy+bzOEAfYuRS8Omff9
	8D6fPoSo0WNAxFxG7eB/UIrKwq5ZxRMZSMcAoWOfbChLp37hdS9pLL35eD0y8GPBa68Q
	W2RVnqqLl0vHMQqKVnJofkPQNx+nhPFC1/H4p3035USQYY9xdoX+dRasgCfro5BVtTHm
	P7tPwGEe8Lb7nkpM+gMCZhw5SqSzPpeq8hRi4Nxr6Puf7wZgOACgXPI6MpoIPM9ar1am
	0kCFPvcQD4LYP91FnYmazsUSr0xV4vZp3Oc69M7mx94nsiCvYG7zRGB9KEI7qFrFSOSk
	QSMQ==
Received: by 10.112.38.103 with SMTP id f7mr807999lbk.120.1355403514561;
	Thu, 13 Dec 2012 04:58:34 -0800 (PST)
Received: from [192.168.178.21]
	(host137-94-dynamic.4-87-r.retail.telecomitalia.it. [87.4.94.137])
	by mx.google.com with ESMTPS id ne2sm618962lab.10.2012.12.13.04.58.32
	(version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 04:58:33 -0800 (PST)
Message-ID: <50C9D0F6.5040002@gmail.com>
Date: Thu, 13 Dec 2012 13:58:30 +0100
From: Stefano Lattarini <stefano.lattarini@gmail.com>
MIME-Version: 1.0
To: Eduardo Costa <ecosta.tmp@gmail.com>
Subject: Re: About dynamic configure options.
References: <CAKTLjWk_8OGyTShr1Bio8J2g3Uzhfv+ws2PYsxFvFJYjLFdi5A@mail.gmail.com>
In-Reply-To: <CAKTLjWk_8OGyTShr1Bio8J2g3Uzhfv+ws2PYsxFvFJYjLFdi5A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.215.41
Cc: Autoconf <Autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 12:58:44 -0000

Hi Eduardo.

On 12/11/2012 12:57 AM, Eduardo Costa wrote:
> Hi,
> 
> Is it possible at all to have a configure option whose help message can expand a
> variable, or can otherwise accept the output of a command at configure-time?
> 
> For example, imagine this as part of the output of `./configure':
> 
> --with-user=user        Who to complain to (default X)
> 
> Where X could be, say, the output of the command `whoami'.
> 
> This might be done by usual means (couldn't do it) or just with some
> trickery to to inject the string manually at the end of some section
> (say HELP_CANON or other), and giving the output of the command on a
> new line, so it doesn't get inside the `cat << LABEL ... LABEL'
> constructs that seem to be used to output options and help messages.
> 
> Thanks,
> 
This question really pertains to Autoconf, not Automake.  I'm thus
forwarding it to the Autoconf list, where somebody might be willing
to answer it (I haven't looked at it in detail, since I'm busy with
other stuff right now; I might give it a shot in a few days maybe,
but no promise).

HTH,
  Stefano


From MAILER-DAEMON Thu Dec 13 12:27:59 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TjCZj-00006L-3H
	for mharc-autoconf@gnu.org; Thu, 13 Dec 2012 12:27:59 -0500
Received: from eggs.gnu.org ([208.118.235.92]:46007)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TjCZg-0008Vf-Bp
	for Autoconf@gnu.org; Thu, 13 Dec 2012 12:27:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TjCZd-00045U-38
	for Autoconf@gnu.org; Thu, 13 Dec 2012 12:27:56 -0500
Received: from mx1.redhat.com ([209.132.183.28]:19001)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TjCZc-00045Q-Qh
	for Autoconf@gnu.org; Thu, 13 Dec 2012 12:27:53 -0500
Received: from int-mx09.intmail.prod.int.phx2.redhat.com
	(int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qBDHRpA7016007
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Thu, 13 Dec 2012 12:27:51 -0500
Received: from [10.3.113.29] (ovpn-113-29.phx2.redhat.com [10.3.113.29])
	by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP
	id qBDHKaec017054; Thu, 13 Dec 2012 12:20:44 -0500
Message-ID: <50CA0E5E.8090808@redhat.com>
Date: Thu, 13 Dec 2012 10:20:30 -0700
From: Eric Blake <eblake@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Stefano Lattarini <stefano.lattarini@gmail.com>
Subject: Re: About dynamic configure options.
References: <CAKTLjWk_8OGyTShr1Bio8J2g3Uzhfv+ws2PYsxFvFJYjLFdi5A@mail.gmail.com>
	<50C9D0F6.5040002@gmail.com>
In-Reply-To: <50C9D0F6.5040002@gmail.com>
X-Enigmail-Version: 1.4.6
OpenPGP: url=http://people.redhat.com/eblake/eblake.gpg
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature";
	boundary="------------enig233FD584493353FAC87039D4"
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 209.132.183.28
Cc: Eduardo Costa <ecosta.tmp@gmail.com>, Autoconf <Autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 17:27:57 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig233FD584493353FAC87039D4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/13/2012 05:58 AM, Stefano Lattarini wrote:
> Hi Eduardo.
>=20
> On 12/11/2012 12:57 AM, Eduardo Costa wrote:
>> Hi,
>>
>> Is it possible at all to have a configure option whose help message ca=
n expand a
>> variable, or can otherwise accept the output of a command at configure=
-time?
>>
>> For example, imagine this as part of the output of `./configure':
>>
>> --with-user=3Duser        Who to complain to (default X)
>>
>> Where X could be, say, the output of the command `whoami'.
>>
>> This might be done by usual means (couldn't do it) or just with some
>> trickery to to inject the string manually at the end of some section
>> (say HELP_CANON or other), and giving the output of the command on a
>> new line, so it doesn't get inside the `cat << LABEL ... LABEL'
>> constructs that seem to be used to output options and help messages.

Unfortunately, it looks like the current setup of autoconf is pretty
hard-coded to constant strings determined at m4-time; making it use
shell variables for dynamic output would require quite a bit of patching
(maybe by introducing new macros such as AC_ARG_WITH_UNQUOTED, to take
care of the tweaks needed to close the quoted heredoc, open an unquoted
heredoc to do the substitution, then reopen the quoted heredoc for the
rest of the script).  It sounds like a useful request, though.

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--------------enig233FD584493353FAC87039D4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBCAAGBQJQyg5fAAoJEKeha0olJ0Nq8C4H/jj2o0IyudC2H1zw+T/Y2JGg
+AdbvVSBpulvQMOneIiyiOWT5NnBIp8t3VoGAbl99mFc40b7nHIiWWzq+ZzEhOPv
w9KReg59Eruc6evPEIdAdJJNGxYuHCBeA9hjPNNC64wXVqzsEoGFyHVRAAo4ze9S
6ppmraT6zYGWbvgmjwcgtJ38cOkO4bEXGDrP6d8RpQ/BG7/gwpd79WQM9JaiN4A6
iTCs14D/+qpR1OX+iZ224gxhtywAy8TIqFElPqBvS72mf8uausfmP9wrhZJSUtQU
hCCDSY2TiWttINdsXTHdvLeEiaZS7k8879tJqw26CxA9xi4OvN/Ox/9PEl/PU10=
=KOlK
-----END PGP SIGNATURE-----

--------------enig233FD584493353FAC87039D4--


From MAILER-DAEMON Thu Dec 13 14:26:04 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TjEQ0-0008JI-Mt
	for mharc-autoconf@gnu.org; Thu, 13 Dec 2012 14:26:04 -0500
Received: from eggs.gnu.org ([208.118.235.92]:35023)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <prvs=nbowler=6876e6517@elliptictech.com>)
	id 1TjEPt-0008IW-8W
	for Autoconf@gnu.org; Thu, 13 Dec 2012 14:26:03 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <prvs=nbowler=6876e6517@elliptictech.com>)
	id 1TjEPr-0002SO-Ry
	for Autoconf@gnu.org; Thu, 13 Dec 2012 14:25:57 -0500
Received: from mx.scalarmail.ca ([98.158.95.75]:7544
	helo=ironport-01.sms.scalar.ca)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <prvs=nbowler=6876e6517@elliptictech.com>)
	id 1TjEPr-0002SK-Ng
	for Autoconf@gnu.org; Thu, 13 Dec 2012 14:25:55 -0500
Received: from unknown (HELO sms-zimbra-mta-01.sms.scalar.ca) ([192.168.32.56])
	by ironport-01.sms.scalar.ca with ESMTP; 13 Dec 2012 14:25:55 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by sms-zimbra-mta-01.sms.scalar.ca (Postfix) with ESMTP id E0DCA17F57; 
	Thu, 13 Dec 2012 14:25:54 -0500 (EST)
Received: from sms-zimbra-mta-01.sms.scalar.ca ([127.0.0.1])
	by localhost (sms-zimbra-mta-01.sms.scalar.ca [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id BCvHwnnd9YrS; Thu, 13 Dec 2012 14:25:54 -0500 (EST)
Received: from mail.ellipticsemi.com (dsl-67-204-24-19.acanac.net
	[67.204.24.19]) (Authenticated sender: nbowler@elliptictech.com)
	by sms-zimbra-mta-01.sms.scalar.ca (Postfix) with ESMTPSA id BBD6E17F4D;
	Thu, 13 Dec 2012 14:25:53 -0500 (EST)
Date: Thu, 13 Dec 2012 14:25:53 -0500
From: Nick Bowler <nbowler@elliptictech.com>
To: Eric Blake <eblake@redhat.com>
Subject: Re: About dynamic configure options.
Message-ID: <20121213192553.GA4520@elliptictech.com>
References: <CAKTLjWk_8OGyTShr1Bio8J2g3Uzhfv+ws2PYsxFvFJYjLFdi5A@mail.gmail.com>
	<50C9D0F6.5040002@gmail.com> <50CA0E5E.8090808@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50CA0E5E.8090808@redhat.com>
Organization: Elliptic Technologies Inc.
User-Agent: Mutt/1.5.21 (2010-09-15)
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 98.158.95.75
Cc: Eduardo Costa <ecosta.tmp@gmail.com>, Autoconf <Autoconf@gnu.org>,
	Stefano Lattarini <stefano.lattarini@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 19:26:03 -0000

On 2012-12-13 10:20 -0700, Eric Blake wrote:
> On 12/13/2012 05:58 AM, Stefano Lattarini wrote:
> > On 12/11/2012 12:57 AM, Eduardo Costa wrote:
> >> Is it possible at all to have a configure option whose help message can expand a
> >> variable, or can otherwise accept the output of a command at configure-time?
> >>
> >> For example, imagine this as part of the output of `./configure':
> >>
> >> --with-user=user        Who to complain to (default X)
> >>
> >> Where X could be, say, the output of the command `whoami'.
> >>
> >> This might be done by usual means (couldn't do it) or just with some
> >> trickery to to inject the string manually at the end of some section
> >> (say HELP_CANON or other), and giving the output of the command on a
> >> new line, so it doesn't get inside the `cat << LABEL ... LABEL'
> >> constructs that seem to be used to output options and help messages.
> 
> Unfortunately, it looks like the current setup of autoconf is pretty
> hard-coded to constant strings determined at m4-time; making it use
> shell variables for dynamic output would require quite a bit of patching
> (maybe by introducing new macros such as AC_ARG_WITH_UNQUOTED, to take
> care of the tweaks needed to close the quoted heredoc, open an unquoted
> heredoc to do the substitution, then reopen the quoted heredoc for the
> rest of the script).  It sounds like a useful request, though.

FWIW it's not too hard to hack it:

  AC_ARG_WITH([user], [_ACEOF
    # Eschew error handling!
    me=`whoami`
    cat <<EOF dnl
    m4_newline([AS_HELP_STRING([--with-user],
                               [Who to complain to (default $me)])])dnl
    m4_newline([EOF])
    cat <<\_ACEOF])

but that is, of course, relying on internal details of how Autoconf
generates the code to produce --help output.  But there remain other
problems: firstly, the --help text appears quite early in the configure
output -- much earlier than the position of AC_ARG_WITH in configure.ac
would imply.  This may make it hard to put anything useful in the help
text, without computing it directly in AC_ARG_WITH_UNQUOTED or whatever
(as done in the above example).

Secondly, regarding this specific example, I don't know if whoami is
universally available.  So determining the default username is probably
within the realm of a "full" configure test, with at least one invocation
of AC_CHECK_PROGS.  Such a test is almost certainly too much to do before
printing --help output.

Normally it is sufficient to just write the --help text as a static
string explaining how the default is determined.  In the case of a
username like above, I would probably do something like:

  --with-user=user        Who to complain to (default: current user)

and then make the configure script print a line such as:

  Checking which user will receive complaints... nbowler

Cheers,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)


From MAILER-DAEMON Thu Dec 13 18:11:57 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TjHwb-00075v-22
	for mharc-autoconf@gnu.org; Thu, 13 Dec 2012 18:11:57 -0500
Received: from eggs.gnu.org ([208.118.235.92]:37127)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ecosta.tmp@gmail.com>) id 1TjHBC-0001nL-Up
	for Autoconf@gnu.org; Thu, 13 Dec 2012 17:23:00 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ecosta.tmp@gmail.com>) id 1TjHBB-0004G2-9C
	for Autoconf@gnu.org; Thu, 13 Dec 2012 17:22:58 -0500
Received: from mail-we0-f169.google.com ([74.125.82.169]:42443)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ecosta.tmp@gmail.com>) id 1TjHBB-0004Fy-2m
	for Autoconf@gnu.org; Thu, 13 Dec 2012 17:22:57 -0500
Received: by mail-we0-f169.google.com with SMTP id t49so1228721wey.0
	for <Autoconf@gnu.org>; Thu, 13 Dec 2012 14:22:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=j8UkMV2bZQIuZBVlPoHbA86hw8Ad1nXQQlyARkvtLMc=;
	b=SUJKgtsi/ytJd6gqTq1jEtW7JKQbl1YOV8O9WhpNNqlHFlTm5e/ZitZMes08utKnLn
	IPlESVQK7LNFoGgxXNQM81vn39EzPy/bKq3dLOnxWb91vyBTxD4fhlYPwGpL6Ej03OBp
	Ses/9bdYNnroyr6FQiuunDBr8trr1OAdtABgVxkId91VuKUEF5ZfEggN6JAttQXqRcpW
	8sWUAbpwuICYjdbz3HYWB47f1yUZMJSwx9tZspclAAtDDUgP2FhZQ5Ja28JNIsOd7AQm
	SJ1yKB0TL53EaMczg8c5UB/8/c4gJN6r3o3M2999lIeMmkPYMJ9eGKEw18JI+rtQutLA
	O7jQ==
MIME-Version: 1.0
Received: by 10.180.107.197 with SMTP id he5mr5898861wib.1.1355437375763; Thu,
	13 Dec 2012 14:22:55 -0800 (PST)
Received: by 10.194.9.68 with HTTP; Thu, 13 Dec 2012 14:22:55 -0800 (PST)
In-Reply-To: <20121213192553.GA4520@elliptictech.com>
References: <CAKTLjWk_8OGyTShr1Bio8J2g3Uzhfv+ws2PYsxFvFJYjLFdi5A@mail.gmail.com>
	<50C9D0F6.5040002@gmail.com> <50CA0E5E.8090808@redhat.com>
	<20121213192553.GA4520@elliptictech.com>
Date: Thu, 13 Dec 2012 22:22:55 +0000
Message-ID: <CAKTLjW=Lnpgab5xcW5qRTvjSvi=wR04PvnwLptmhP+7D801UZw@mail.gmail.com>
Subject: Re: About dynamic configure options.
From: Eduardo Costa <ecosta.tmp@gmail.com>
To: Nick Bowler <nbowler@elliptictech.com>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 74.125.82.169
X-Mailman-Approved-At: Thu, 13 Dec 2012 18:11:56 -0500
Cc: Stefano Lattarini <stefano.lattarini@gmail.com>,
	Autoconf <Autoconf@gnu.org>, Eric Blake <eblake@redhat.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 22:23:00 -0000

Thanks guys,

I actually sent a "solution" much like yours Nick. Don't know why
Stefano didn't send my answer. This is what I came up with:

AC_DEFUN([TRICK],
[m4_divert_text([HELP_CANON], [_ACEOF
echo -en "\n* --option=VAL            Date: `date`"
cat <<\_ACEOF])])

TRICK

You can see automake's archives for my whole message.

Te code above will get hooked at the end of `HELP_CANON' (before the
`heredoc' ends), or after the `Fine tuning' options if canonical
support macros hasn't been called.

Something that did surprise by looking at `general.m4' is that
sections such as HELP_CANON, HELP_BEGIN, etc, have all been allocated
sequentially, leaving no room for per-project customization.

This is just my ignorant's opinion. I'm far from being a m4, autoconf,
or automake specialist.

Thanks,



On 13/12/2012, Nick Bowler <nbowler@elliptictech.com> wrote:
> On 2012-12-13 10:20 -0700, Eric Blake wrote:
>> On 12/13/2012 05:58 AM, Stefano Lattarini wrote:
>> > On 12/11/2012 12:57 AM, Eduardo Costa wrote:
>> >> Is it possible at all to have a configure option whose help message can
>> >> expand a
>> >> variable, or can otherwise accept the output of a command at
>> >> configure-time?
>> >>
>> >> For example, imagine this as part of the output of `./configure':
>> >>
>> >> --with-user=user        Who to complain to (default X)
>> >>
>> >> Where X could be, say, the output of the command `whoami'.
>> >>
>> >> This might be done by usual means (couldn't do it) or just with some
>> >> trickery to to inject the string manually at the end of some section
>> >> (say HELP_CANON or other), and giving the output of the command on a
>> >> new line, so it doesn't get inside the `cat << LABEL ... LABEL'
>> >> constructs that seem to be used to output options and help messages.
>>
>> Unfortunately, it looks like the current setup of autoconf is pretty
>> hard-coded to constant strings determined at m4-time; making it use
>> shell variables for dynamic output would require quite a bit of patching
>> (maybe by introducing new macros such as AC_ARG_WITH_UNQUOTED, to take
>> care of the tweaks needed to close the quoted heredoc, open an unquoted
>> heredoc to do the substitution, then reopen the quoted heredoc for the
>> rest of the script).  It sounds like a useful request, though.
>
> FWIW it's not too hard to hack it:
>
>   AC_ARG_WITH([user], [_ACEOF
>     # Eschew error handling!
>     me=`whoami`
>     cat <<EOF dnl
>     m4_newline([AS_HELP_STRING([--with-user],
>                                [Who to complain to (default $me)])])dnl
>     m4_newline([EOF])
>     cat <<\_ACEOF])
>
> but that is, of course, relying on internal details of how Autoconf
> generates the code to produce --help output.  But there remain other
> problems: firstly, the --help text appears quite early in the configure
> output -- much earlier than the position of AC_ARG_WITH in configure.ac
> would imply.  This may make it hard to put anything useful in the help
> text, without computing it directly in AC_ARG_WITH_UNQUOTED or whatever
> (as done in the above example).
>
> Secondly, regarding this specific example, I don't know if whoami is
> universally available.  So determining the default username is probably
> within the realm of a "full" configure test, with at least one invocation
> of AC_CHECK_PROGS.  Such a test is almost certainly too much to do before
> printing --help output.
>
> Normally it is sufficient to just write the --help text as a static
> string explaining how the default is determined.  In the case of a
> username like above, I would probably do something like:
>
>   --with-user=user        Who to complain to (default: current user)
>
> and then make the configure script print a line such as:
>
>   Checking which user will receive complaints... nbowler
>
> Cheers,
> --
> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
>


From MAILER-DAEMON Fri Dec 14 03:49:34 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TjQxa-0004YG-GC
	for mharc-autoconf@gnu.org; Fri, 14 Dec 2012 03:49:34 -0500
Received: from eggs.gnu.org ([208.118.235.92]:42168)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefano.lattarini@gmail.com>) id 1TjQxY-0004Xp-DX
	for Autoconf@gnu.org; Fri, 14 Dec 2012 03:49:33 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefano.lattarini@gmail.com>) id 1TjQxU-0008R0-Ug
	for Autoconf@gnu.org; Fri, 14 Dec 2012 03:49:32 -0500
Received: from mail-bk0-f41.google.com ([209.85.214.41]:56938)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefano.lattarini@gmail.com>) id 1TjQxU-0008Qq-DV
	for Autoconf@gnu.org; Fri, 14 Dec 2012 03:49:28 -0500
Received: by mail-bk0-f41.google.com with SMTP id jg9so1496559bkc.0
	for <Autoconf@gnu.org>; Fri, 14 Dec 2012 00:49:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=lmrZPx5RGiBykRENr5Jwli/+tlkus8Cik0ZvkdktzHg=;
	b=nATusJgFGEPbYsVJZqcBzJ93ClLUIl4ZyxO0cyTMDoTe6isW8u1B8u24p4+2LVeGdJ
	R0/iTXiQs6ZV7dAQjas9q5/+6IspSv88XbhCH3b1R3kEoFpEv5WKmNqt4/ZuWsdZ8yS2
	IBCrUlnj7oyZLJ5M9ts3UOVMdRekIez6zGTO93eKT3hOzcyPupwwlMeCaPiDJ2M7bu5B
	15D0nihMEHSdvPWvUeDx8y+Tw3c+eys9FvcJ+nU9RazxSiSRrHElixiS4jQY0AAbxRWL
	DaacURtlpKofWJwknzWcbKSPAuJKiZ2OgQuekvqlFx57zlFeX7mxCLSMnOHqdILrxBjv
	fUdA==
Received: by 10.204.156.11 with SMTP id u11mr2421848bkw.106.1355474967460;
	Fri, 14 Dec 2012 00:49:27 -0800 (PST)
Received: from [192.168.178.21]
	(host137-94-dynamic.4-87-r.retail.telecomitalia.it. [87.4.94.137])
	by mx.google.com with ESMTPS id f24sm3495611bkv.7.2012.12.14.00.49.25
	(version=SSLv3 cipher=OTHER); Fri, 14 Dec 2012 00:49:26 -0800 (PST)
Message-ID: <50CAE814.60707@gmail.com>
Date: Fri, 14 Dec 2012 09:49:24 +0100
From: Stefano Lattarini <stefano.lattarini@gmail.com>
MIME-Version: 1.0
To: Eduardo Costa <ecosta.tmp@gmail.com>
Subject: Re: About dynamic configure options.
References: <CAKTLjWk_8OGyTShr1Bio8J2g3Uzhfv+ws2PYsxFvFJYjLFdi5A@mail.gmail.com>
	<50C9D0F6.5040002@gmail.com> <50CA0E5E.8090808@redhat.com>
	<20121213192553.GA4520@elliptictech.com>
	<CAKTLjW=Lnpgab5xcW5qRTvjSvi=wR04PvnwLptmhP+7D801UZw@mail.gmail.com>
In-Reply-To: <CAKTLjW=Lnpgab5xcW5qRTvjSvi=wR04PvnwLptmhP+7D801UZw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.214.41
Cc: Nick Bowler <nbowler@elliptictech.com>, Autoconf <Autoconf@gnu.org>,
	Eric Blake <eblake@redhat.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 08:49:33 -0000

On 12/13/2012 11:22 PM, Eduardo Costa wrote:
> Thanks guys,
> 
> I actually sent a "solution" much like yours Nick. Don't know
> why Stefano didn't send my answer.
>
You mean this part?

  This might be done by usual means (couldn't do it) or just with some
  trickery to to inject the string manually at the end of some section
  (say HELP_CANON or other), and giving the output of the command on a
  new line, so it doesn't get inside the `cat << LABEL ... LABEL'
  constructs that seem to be used to output options and help messages.

But I did send it ...

> This is what I came up with:
> 
> AC_DEFUN([TRICK],
> [m4_divert_text([HELP_CANON], [_ACEOF
> echo -en "\n* --option=VAL            Date: `date`"
> cat <<\_ACEOF])])
> 
> TRICK
> 
> You can see automake's archives for my whole message.
>
Here's the link BTW:

  <http://lists.gnu.org/archive/html/automake/2012-12/msg00022.html>

And looking at my forward to the Autoconf list:

  <http://lists.gnu.org/archive/html/autoconf/2012-12/msg00018.html>

you can see I quoted your original message in its entirety.  Am I
missing something else here?

Regards,
  Stefano


From MAILER-DAEMON Fri Dec 14 12:23:06 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TjYyY-0004sK-0n
	for mharc-autoconf@gnu.org; Fri, 14 Dec 2012 12:23:06 -0500
Received: from eggs.gnu.org ([208.118.235.92]:42738)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ecosta.tmp@gmail.com>) id 1TjYyV-0004rT-IK
	for Autoconf@gnu.org; Fri, 14 Dec 2012 12:23:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ecosta.tmp@gmail.com>) id 1TjYyQ-0004sK-Q5
	for Autoconf@gnu.org; Fri, 14 Dec 2012 12:23:03 -0500
Received: from mail-wi0-f169.google.com ([209.85.212.169]:41608)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ecosta.tmp@gmail.com>) id 1TjYyQ-0004sB-IW
	for Autoconf@gnu.org; Fri, 14 Dec 2012 12:22:58 -0500
Received: by mail-wi0-f169.google.com with SMTP id hq12so716421wib.0
	for <Autoconf@gnu.org>; Fri, 14 Dec 2012 09:22:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=RLsU3winmsPjGKOLInSl8/FOPW4AUOeDUThMurBcrFY=;
	b=ptmLaWw9sO3+oixpP8sJbBi2ch6a1xHZsxG53Q3kN0Be3UrOXKjxckKCD7clCTK9Xn
	NbvsQiwiNlaOqmWRfCDzPXmT8fPpm/UUHo75FFCOcgNob3Ve/vm7M/ErJzDRXvZawhRC
	acVBdzYvSx99nMOFbahBVyKF/NhHDPikr4K2PUL6NWPPj2l/JDipkUsNUiVL15mrJ3tq
	U+Vj9ubBxJ0YX4PBIqwZ+f4Ib97XE2yRkBT6aIEso10163UbH3FjFY1DLaRIFYtDWcWJ
	wOMVIw7bKvPyXE/JSC0L1ewGCmPwI0/bxLRuTHIpD5tTgt6BQkiqGOkdWqP+R+/fdgml
	Zk0w==
MIME-Version: 1.0
Received: by 10.180.98.8 with SMTP id ee8mr3946499wib.4.1355505777538; Fri, 14
	Dec 2012 09:22:57 -0800 (PST)
Received: by 10.194.9.68 with HTTP; Fri, 14 Dec 2012 09:22:57 -0800 (PST)
In-Reply-To: <50CAE814.60707@gmail.com>
References: <CAKTLjWk_8OGyTShr1Bio8J2g3Uzhfv+ws2PYsxFvFJYjLFdi5A@mail.gmail.com>
	<50C9D0F6.5040002@gmail.com> <50CA0E5E.8090808@redhat.com>
	<20121213192553.GA4520@elliptictech.com>
	<CAKTLjW=Lnpgab5xcW5qRTvjSvi=wR04PvnwLptmhP+7D801UZw@mail.gmail.com>
	<50CAE814.60707@gmail.com>
Date: Fri, 14 Dec 2012 17:22:57 +0000
Message-ID: <CAKTLjW=taWTyfPVdd4OO-d-D7jmhxMcZEUgTKswL6hk8v9Ohqg@mail.gmail.com>
Subject: Re: About dynamic configure options.
From: Eduardo Costa <ecosta.tmp@gmail.com>
To: Stefano Lattarini <stefano.lattarini@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.169
Cc: Nick Bowler <nbowler@elliptictech.com>, Autoconf <Autoconf@gnu.org>,
	Eric Blake <eblake@redhat.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 17:23:04 -0000

Hi Stefano,

Sorry then!, I was a bit in a hurry yesterday. So they can have an idea then.

Thanks,



On 14/12/2012, Stefano Lattarini <stefano.lattarini@gmail.com> wrote:
> On 12/13/2012 11:22 PM, Eduardo Costa wrote:
>> Thanks guys,
>>
>> I actually sent a "solution" much like yours Nick. Don't know
>> why Stefano didn't send my answer.
>>
> You mean this part?
>
>   This might be done by usual means (couldn't do it) or just with some
>   trickery to to inject the string manually at the end of some section
>   (say HELP_CANON or other), and giving the output of the command on a
>   new line, so it doesn't get inside the `cat << LABEL ... LABEL'
>   constructs that seem to be used to output options and help messages.
>
> But I did send it ...
>
>> This is what I came up with:
>>
>> AC_DEFUN([TRICK],
>> [m4_divert_text([HELP_CANON], [_ACEOF
>> echo -en "\n* --option=VAL            Date: `date`"
>> cat <<\_ACEOF])])
>>
>> TRICK
>>
>> You can see automake's archives for my whole message.
>>
> Here's the link BTW:
>
>   <http://lists.gnu.org/archive/html/automake/2012-12/msg00022.html>
>
> And looking at my forward to the Autoconf list:
>
>   <http://lists.gnu.org/archive/html/autoconf/2012-12/msg00018.html>
>
> you can see I quoted your original message in its entirety.  Am I
> missing something else here?
>
> Regards,
>   Stefano
>


From MAILER-DAEMON Sat Dec 15 15:32:08 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TjyP2-0000IN-JG
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 15:32:08 -0500
Received: from eggs.gnu.org ([208.118.235.92]:52705)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TjyOz-0000HU-04
	for autoconf@gnu.org; Sat, 15 Dec 2012 15:32:06 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TjyOv-0004wf-0S
	for autoconf@gnu.org; Sat, 15 Dec 2012 15:32:04 -0500
Received: from mail-vc0-f169.google.com ([209.85.220.169]:56114)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TjyOu-0004wY-SK
	for autoconf@gnu.org; Sat, 15 Dec 2012 15:32:00 -0500
Received: by mail-vc0-f169.google.com with SMTP id gb23so5822700vcb.0
	for <autoconf@gnu.org>; Sat, 15 Dec 2012 12:32:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=pT1683YtY5pVWaUozH0o6d1qRyMhsKLhrIOukl5ozpk=;
	b=1FZLwEXXjwtExShlTmHpTCOhKH2J1jr1Ec0p7tHMaF/Gr0SdQ9Ib248tdcuKlDjOHE
	vkXZpKNwWVKXRaLKie/N5iqtY1wAN28Ms+grzSCsR1p6I+xl8qZ5IHVEtpd3RaewPh9C
	Wbif/2ExgoiNPS2sm7N1et8sILbAmtPLyQXKXcf1KnxbZMgVcEYF1Cd68++WSP/WU6CD
	SdUPEsaOVk6xuY/wSZQ+V5/BUOxfDn0TAR9bgmvlruvcxwSAWZVCioXZ2Ftc+YfuUk5m
	5AUh9i3z4OtHwk+F1ySzBz0ZgsjzfQQglKeFAz01rbd3X5xFaxhqQJuCvXXzjYI9aRxp
	j6OQ==
MIME-Version: 1.0
Received: by 10.58.132.229 with SMTP id ox5mr16199209veb.46.1355603520122;
	Sat, 15 Dec 2012 12:32:00 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Sat, 15 Dec 2012 12:31:59 -0800 (PST)
In-Reply-To: <50C5E54E.1080103@redhat.com>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
Date: Sat, 15 Dec 2012 15:31:59 -0500
Message-ID: <CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
From: Jeffrey Walton <noloader@gmail.com>
To: Eric Blake <eblake@redhat.com>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.220.169
Cc: "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Dec 2012 20:32:06 -0000

On Mon, Dec 10, 2012 at 8:36 AM, Eric Blake <eblake@redhat.com> wrote:
> On 12/08/2012 05:16 PM, Jeffrey Walton wrote:
>> Agreed. Before anything, the program has to be correct. Trying to
>> remove a directory named 'core' does not follow the intention
>> (informally 'specification') of removing crash dump files.
>
> Naming a directory 'core' is dangerous and non-portable, because the
> name 'core' is traditionally reserved for core dumps.
Agreed, but the program is still not correct (assuming the
specification is to remove old core dumps).

Before anything, the program has to be correct. After correctness, the
program should be secure and can be efficient.

Jeff


From MAILER-DAEMON Sat Dec 15 17:59:03 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk0hD-0005VD-2i
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 17:59:03 -0500
Received: from eggs.gnu.org ([208.118.235.92]:38476)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk0hB-0005UB-5N
	for autoconf@gnu.org; Sat, 15 Dec 2012 17:59:01 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk0hA-0004Pt-5n
	for autoconf@gnu.org; Sat, 15 Dec 2012 17:59:01 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:43489)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk0hA-0004PJ-02
	for autoconf@gnu.org; Sat, 15 Dec 2012 17:59:00 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 03E8DA60001;
	Sat, 15 Dec 2012 14:58:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bDL5XaV3YUxF; Sat, 15 Dec 2012 14:58:51 -0800 (PST)
Received: from [192.168.1.6] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id A6DC839E8106;
	Sat, 15 Dec 2012 14:58:51 -0800 (PST)
Message-ID: <50CD00AB.7060107@cs.ucla.edu>
Date: Sat, 15 Dec 2012 14:58:51 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: noloader@gmail.com
Subject: Re: RE : RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
In-Reply-To: <CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Dec 2012 22:59:02 -0000

On 12/15/2012 12:31 PM, Jeffrey Walton wrote:
> the program is still not correct

Correctness is in the eye of the beholder.
For most people 'configure' behaves as intended,
but it doesn't match your intent.  Unfortunately
the discussion we've all had so far suggests that
it's not likely Autoconf will change its behavior
in this area, so I suggest following some of the
advice that I and others already gave to work
around the problem.


From MAILER-DAEMON Sat Dec 15 18:08:24 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk0qG-0007De-25
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 18:08:24 -0500
Received: from eggs.gnu.org ([208.118.235.92]:39431)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tk0qC-0007CX-Uw
	for autoconf@gnu.org; Sat, 15 Dec 2012 18:08:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tk0qB-0006gf-Pn
	for autoconf@gnu.org; Sat, 15 Dec 2012 18:08:20 -0500
Received: from mail-vb0-f41.google.com ([209.85.212.41]:59114)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tk0qB-0006gb-M4
	for autoconf@gnu.org; Sat, 15 Dec 2012 18:08:19 -0500
Received: by mail-vb0-f41.google.com with SMTP id l22so5809523vbn.0
	for <autoconf@gnu.org>; Sat, 15 Dec 2012 15:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=f0gGGeVd8zpuMONRtwfitjxcFIENpiw6Ba2EQHXVol0=;
	b=oiLSFF+TA7nvR8PcjHKbDa9PF6YMRvAoHcrVSIb5M9yb8xJFwPbhHUPAACTpIgKKVX
	UxIopfUY06qH+jSpczXkl1kFd+7sG285SsF1hRnlGxx0eOkoycw87BEylI9FyPnQvxK3
	dVPMjD8Golon+uPBhMzn80ZBz57hfGabsiSI1/6jrKpozudC9pDu8g8VfYTAKZCK3EFB
	edlvIdPjl5uZ0Qa20FcFn4ZjRrqMyNwkjPxcGtrSxbY9dfLhcu0eCmiJ/qlxQxytU38Q
	F2Z4eGty2iNnt7g5eIyo1lrNy/kIaiauxeYbAj2FPCvkBH0Ywr+8AVLvxydMPwMc6yWF
	hMJw==
MIME-Version: 1.0
Received: by 10.58.187.84 with SMTP id fq20mr16772970vec.25.1355612899091;
	Sat, 15 Dec 2012 15:08:19 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Sat, 15 Dec 2012 15:08:18 -0800 (PST)
In-Reply-To: <50CD00AB.7060107@cs.ucla.edu>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
	<50CD00AB.7060107@cs.ucla.edu>
Date: Sat, 15 Dec 2012 18:08:18 -0500
Message-ID: <CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
From: Jeffrey Walton <noloader@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.41
Cc: "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Dec 2012 23:08:22 -0000

On Sat, Dec 15, 2012 at 5:58 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 12/15/2012 12:31 PM, Jeffrey Walton wrote:
>>
>> the program is still not correct
>
> Correctness is in the eye of the beholder.
Hmmm....

> For most people 'configure' behaves as intended,
> but it doesn't match your intent.
I'm not sure its my intent. Is the program designed to remove old core
files as part of the autoconf process? Perhaps that's where the
confusion lies.

Perhaps it would be easier (easiest?) to remove that step in the
process? That is, no longer make it a specification of the autoconf
process.

> the discussion we've all had so far suggests that
> it's not likely Autoconf will change its behavior
> in this area, so I suggest following some of the
> advice that I and others already gave to work
> around the problem.
That's fine - I'm used to it (Closed, Won't Fix). It reminds me of
http://linuxhaters.blogspot.com/2008/08/one-bug-report-to-rule-them-all.html
:)

Jeff


From MAILER-DAEMON Sat Dec 15 19:18:24 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk1w0-0003XA-D9
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 19:18:24 -0500
Received: from eggs.gnu.org ([208.118.235.92]:47535)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk1vu-0003V6-NA
	for autoconf@gnu.org; Sat, 15 Dec 2012 19:18:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk1vp-00062e-KU
	for autoconf@gnu.org; Sat, 15 Dec 2012 19:18:18 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:45421)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk1vp-00062U-EW
	for autoconf@gnu.org; Sat, 15 Dec 2012 19:18:13 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 70A13A60001;
	Sat, 15 Dec 2012 16:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uKMyKT37cdMj; Sat, 15 Dec 2012 16:18:12 -0800 (PST)
Received: from [192.168.1.6] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 2371139E8106;
	Sat, 15 Dec 2012 16:18:12 -0800 (PST)
Message-ID: <50CD1343.6050601@cs.ucla.edu>
Date: Sat, 15 Dec 2012 16:18:11 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: noloader@gmail.com
Subject: Re: RE : RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
	<50CD00AB.7060107@cs.ucla.edu>
	<CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
In-Reply-To: <CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 00:18:22 -0000

On 12/15/2012 03:08 PM, Jeffrey Walton wrote:
> Is the program designed to remove old core
> files as part of the autoconf process?

No, new cores.  'configure' regularly generates
programs that dump core, as part of its ordinary
working procedure.


From MAILER-DAEMON Sat Dec 15 20:01:42 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk2bu-0008Ts-7H
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 20:01:42 -0500
Received: from eggs.gnu.org ([208.118.235.92]:51494)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1Tk2bq-0008T2-JQ
	for autoconf@gnu.org; Sat, 15 Dec 2012 20:01:40 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1Tk2bp-0007Z0-DR
	for autoconf@gnu.org; Sat, 15 Dec 2012 20:01:38 -0500
Received: from mail-pb0-f41.google.com ([209.85.160.41]:35796)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cazfi74@gmail.com>) id 1Tk2bp-0007Yq-6X
	for autoconf@gnu.org; Sat, 15 Dec 2012 20:01:37 -0500
Received: by mail-pb0-f41.google.com with SMTP id xa7so2913101pbc.0
	for <autoconf@gnu.org>; Sat, 15 Dec 2012 17:01:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=ZfruoUP8E8VR4GBYm7FX6jGjUWn9mZ09kzFmU+Qu9/U=;
	b=BB4+snD6nkPJd8+9CPHz6dyTj3sZb3s4fPOieL1pSI8v72FgRLgrAPbay4Bg1+hQv2
	OA+bWJPHTxV1O03UaVY3ZkjaNL4DGf14mXpFmZxl506N+8sL/+vhzo86l8+WrT+zt6Qi
	bIpw+zkgpnBeaMl2Y4v1VBcciU9uqbgpGJx2FJQ56Yg4WcUQVA7XoE8IV9kft8lDYEkw
	1WsSvNdWcoylwV2CJCq991jqBSk2grBI2Mqt5ICW/lACUF5BjtEcTWaWVejknwty9pYr
	Qjin4xLAVtlgtEEVTuaWP1aDzDnoWOYBXs2AflTY3xHBtD9ds2U6ts0gABvX68dibgt/
	eDAw==
MIME-Version: 1.0
Received: by 10.68.252.168 with SMTP id zt8mr29382252pbc.43.1355619695738;
	Sat, 15 Dec 2012 17:01:35 -0800 (PST)
Received: by 10.68.63.6 with HTTP; Sat, 15 Dec 2012 17:01:35 -0800 (PST)
In-Reply-To: <50CD1343.6050601@cs.ucla.edu>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
	<50CD00AB.7060107@cs.ucla.edu>
	<CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
	<50CD1343.6050601@cs.ucla.edu>
Date: Sun, 16 Dec 2012 03:01:35 +0200
Message-ID: <CAF6bG8eeQ9Jwg_+CuGS-k78pPqQkJf33B7kQN8dKfVPMRXw-YA@mail.gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
From: Marko Lindqvist <cazfi74@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.160.41
Cc: noloader@gmail.com, "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 01:01:40 -0000

On 16 December 2012 02:18, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 12/15/2012 03:08 PM, Jeffrey Walton wrote:
>>
>> Is the program designed to remove old core
>> files as part of the autoconf process?
>
>
> No, new cores.  'configure' regularly generates
> programs that dump core, as part of its ordinary
> working procedure.

 Does it make sure core is new one it has created. Granted that if one
wants to play with core generated by the program being developet,
(s)he shouldn't be rebuilding program before those investigations, but
potentially core file is valuable.

 Is the performance issue in the checking of nature of "core" *every
time* configure has potentially created one to be removed? Could it
just check existing situation in the beginning (is there something
named 'core' already) and to store it to variable for later parts to
use?


 - ML


From MAILER-DAEMON Sat Dec 15 20:54:56 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk3RQ-0006fs-0L
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 20:54:56 -0500
Received: from eggs.gnu.org ([208.118.235.92]:56673)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1Tk3RM-0006dx-Mq
	for Autoconf@gnu.org; Sat, 15 Dec 2012 20:54:53 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1Tk3RL-0002Tf-MN
	for Autoconf@gnu.org; Sat, 15 Dec 2012 20:54:52 -0500
Received: from mx.meyering.net ([88.168.87.75]:56363)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1Tk3RL-0002Ta-FW
	for Autoconf@gnu.org; Sat, 15 Dec 2012 20:54:51 -0500
Received: from rho.meyering.net (rho.meyering.net [127.0.0.1])
	by rho.meyering.net (Acme Bit-Twister) with ESMTP id AF9AE600DF;
	Sun, 16 Dec 2012 02:54:50 +0100 (CET)
From: Jim Meyering <jim@meyering.net>
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Subject: Re: Future autoconf package compression
In-Reply-To: <87txrwqm85.fsf@rho.meyering.net> (Jim Meyering's message of
	"Sat, 08 Dec 2012 22:15:38 +0100")
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
	<87txrwqm85.fsf@rho.meyering.net>
Date: Sun, 16 Dec 2012 02:54:50 +0100
Message-ID: <87mwxezrpx.fsf@rho.meyering.net>
Lines: 38
MIME-Version: 1.0
Content-Type: text/plain
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 88.168.87.75
Cc: Autoconf <Autoconf@gnu.org>, Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 01:54:53 -0000

Jim Meyering wrote:
> Bob Friesenhahn wrote:
>> On Sat, 24 Nov 2012, Marko Lindqvist wrote:
>>> On 2 March 2012 06:45, Eric Blake <eblake@redhat.com> wrote:
>>>>
>>>> The Autoconf team is considering releasing only .xz files for 2.69; if
>>>> this would be a hardship for you, and you need the .gz or .bz2 release,
>>>> please speak up now.
>>>
>>> I just encountered new argument for providing .gz of autoconf also in
>>> the future.
>>
>> There is no tangible benefit offered to the world by removing the
>> gzip-compressed autoconf package.  Xz is excessively complex,
>> excessively large, and has limited portability and stability compared
>> with gzip.
>
> Hi Bob,
>
> I don't know of significant portability problems.
> In my experience, if they are reported and affect significant
> (sometimes even insignificant) portability targets, they will be
> addressed promptly.  Can you point to reported problems that
> have not been resolved?
>
> There is no shortage of reasons to avoid gzip these days.  One that
> strikes home for me (as a package maintainer) is that there have
> been exploitable CVEs against gzip in the recent past, and the code
> is surprisingly ugly (hence hard to audit).  I do not want to require
> tarball consumers to use a tool that I do not feel good about, and gzip
> is one of those.  Just because it is still used by so many people (due
> mostly to inertia) does not mean that we should ignore its faults.

FYI, a couple of weeks ago, Aki Helin exposed still more problems in
gzip's unpacking code.  Paul Eggert fixed them just a few days ago:

  http://git.sv.gnu.org/cgit/gzip.git/commit/?id=f2be148c3d956c2dd19bd6fdbe6d
  http://git.sv.gnu.org/cgit/gzip.git/commit/?id=16977ae732bf60f79c9a4fd6d183


From MAILER-DAEMON Sat Dec 15 21:21:32 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk3rA-0001Xv-PK
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 21:21:32 -0500
Received: from eggs.gnu.org ([208.118.235.92]:58251)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk3r8-0001Xp-1H
	for autoconf@gnu.org; Sat, 15 Dec 2012 21:21:31 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk3r7-0008DZ-0v
	for autoconf@gnu.org; Sat, 15 Dec 2012 21:21:29 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:48443)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk3r6-0008Bz-Ra
	for autoconf@gnu.org; Sat, 15 Dec 2012 21:21:28 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 2A72F39E810A;
	Sat, 15 Dec 2012 18:21:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pUmttcFYE8mH; Sat, 15 Dec 2012 18:21:26 -0800 (PST)
Received: from [192.168.1.12] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id A16B039E8106;
	Sat, 15 Dec 2012 18:21:26 -0800 (PST)
Message-ID: <50CD3020.60409@cs.ucla.edu>
Date: Sat, 15 Dec 2012 18:21:20 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Marko Lindqvist <cazfi74@gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
	<50CD00AB.7060107@cs.ucla.edu>
	<CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
	<50CD1343.6050601@cs.ucla.edu>
	<CAF6bG8eeQ9Jwg_+CuGS-k78pPqQkJf33B7kQN8dKfVPMRXw-YA@mail.gmail.com>
In-Reply-To: <CAF6bG8eeQ9Jwg_+CuGS-k78pPqQkJf33B7kQN8dKfVPMRXw-YA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: noloader@gmail.com, "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 02:21:31 -0000

On 12/15/2012 05:01 PM, Marko Lindqvist wrote:
> Does it make sure core is new one it has created.

No.

>  Is the performance issue in the checking of nature of "core" *every
> time* configure has potentially created one to be removed?

Yes.


From MAILER-DAEMON Sat Dec 15 21:24:57 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk3uT-0001rc-Mo
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 21:24:57 -0500
Received: from eggs.gnu.org ([208.118.235.92]:58495)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk3uR-0001rV-6k
	for Autoconf@gnu.org; Sat, 15 Dec 2012 21:24:56 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk3uQ-0000AH-BB
	for Autoconf@gnu.org; Sat, 15 Dec 2012 21:24:55 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:48502)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tk3uQ-0000AC-5W
	for Autoconf@gnu.org; Sat, 15 Dec 2012 21:24:54 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id B5E0D39E810A;
	Sat, 15 Dec 2012 18:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aeNyocyvx482; Sat, 15 Dec 2012 18:24:53 -0800 (PST)
Received: from [192.168.1.12] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 05BB239E8106;
	Sat, 15 Dec 2012 18:24:53 -0800 (PST)
Message-ID: <50CD30F4.5070703@cs.ucla.edu>
Date: Sat, 15 Dec 2012 18:24:52 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Jim Meyering <jim@meyering.net>
Subject: Re: Future autoconf package compression
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
	<87txrwqm85.fsf@rho.meyering.net> <87mwxezrpx.fsf@rho.meyering.net>
In-Reply-To: <87mwxezrpx.fsf@rho.meyering.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: Autoconf <Autoconf@gnu.org>, Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 02:24:56 -0000

On 12/15/2012 05:54 PM, Jim Meyering wrote:
> FYI, a couple of weeks ago, Aki Helin exposed still more problems in
> gzip's unpacking code.

Well, to be fair, I also have a similar problem with 'tar'
in my inbox, from Aki, but I'm not inclined to suggest that
we stop using 'tar'....


From MAILER-DAEMON Sat Dec 15 21:35:55 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk455-0003BQ-HJ
	for mharc-autoconf@gnu.org; Sat, 15 Dec 2012 21:35:55 -0500
Received: from eggs.gnu.org ([208.118.235.92]:59132)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1Tk452-0003Am-Dx
	for Autoconf@gnu.org; Sat, 15 Dec 2012 21:35:54 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1Tk451-0002jg-F1
	for Autoconf@gnu.org; Sat, 15 Dec 2012 21:35:52 -0500
Received: from mx.meyering.net ([88.168.87.75]:56403)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1Tk451-0002ja-7J
	for Autoconf@gnu.org; Sat, 15 Dec 2012 21:35:51 -0500
Received: from rho.meyering.net (rho.meyering.net [127.0.0.1])
	by rho.meyering.net (Acme Bit-Twister) with ESMTP id 75947600E3;
	Sun, 16 Dec 2012 03:35:50 +0100 (CET)
From: Jim Meyering <jim@meyering.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: Future autoconf package compression
In-Reply-To: <50CD30F4.5070703@cs.ucla.edu> (Paul Eggert's message of "Sat, 15
	Dec 2012 18:24:52 -0800")
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
	<87txrwqm85.fsf@rho.meyering.net> <87mwxezrpx.fsf@rho.meyering.net>
	<50CD30F4.5070703@cs.ucla.edu>
Date: Sun, 16 Dec 2012 03:35:50 +0100
Message-ID: <87hanmzptl.fsf@rho.meyering.net>
Lines: 11
MIME-Version: 1.0
Content-Type: text/plain
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 88.168.87.75
Cc: Autoconf <Autoconf@gnu.org>, Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 02:35:54 -0000

Paul Eggert wrote:
> On 12/15/2012 05:54 PM, Jim Meyering wrote:
>> FYI, a couple of weeks ago, Aki Helin exposed still more problems in
>> gzip's unpacking code.
>
> Well, to be fair, I also have a similar problem with 'tar'
> in my inbox, from Aki, but I'm not inclined to suggest that
> we stop using 'tar'....

Of course.  Nor am I.
GNU tar's overall code quality is far higher than that of gzip.


From MAILER-DAEMON Sun Dec 16 01:46:53 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tk7zx-0005Jd-Bx
	for mharc-autoconf@gnu.org; Sun, 16 Dec 2012 01:46:53 -0500
Received: from eggs.gnu.org ([208.118.235.92]:54229)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nightstrike@gmail.com>) id 1Tk7zt-0005GB-7G
	for autoconf@gnu.org; Sun, 16 Dec 2012 01:46:51 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nightstrike@gmail.com>) id 1Tk7zp-0006Ja-5l
	for autoconf@gnu.org; Sun, 16 Dec 2012 01:46:49 -0500
Received: from mail-bk0-f41.google.com ([209.85.214.41]:50806)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nightstrike@gmail.com>) id 1Tk7zo-0006JW-V2
	for autoconf@gnu.org; Sun, 16 Dec 2012 01:46:45 -0500
Received: by mail-bk0-f41.google.com with SMTP id jg9so2212586bkc.0
	for <autoconf@gnu.org>; Sat, 15 Dec 2012 22:46:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=q8TIEGsXixSXD+E3e+1liSd5Babfc4pXsi/YT1TQ8Yg=;
	b=cu/1NkLiUMhSe4JCBhDcvD+jLNK+DK7RIaOHHD8eZGt6Og5lWGPGQxDM8iaYAgZXFw
	SlDDP/ae6PDBEwolld09U/QZkKDmTG7USB1jhCFZEKQnribX6o6J+0ntGGEfy3u38ys8
	4/kVgCYzBpZPstZzgER+t5t+RkRT41iqvpdH+aidmrUgUuWxHdK5xCyoGcGrLcR2hs4I
	k3V2GXZWEy7Q1lFhS5IrReNUchR0wZWKhm/TyuX00r0z0NRbVBt5RhZwJXgONVOznsHG
	Q/hCofSBFmxxtAqbKKptqWQjNfbNRAXm7i1lWGbSfI39TA02en8CNab1yRcVOi7L1eSG
	n7dQ==
MIME-Version: 1.0
Received: by 10.204.129.202 with SMTP id p10mr4466653bks.56.1355640400452;
	Sat, 15 Dec 2012 22:46:40 -0800 (PST)
Received: by 10.204.59.14 with HTTP; Sat, 15 Dec 2012 22:46:40 -0800 (PST)
In-Reply-To: <50CD1343.6050601@cs.ucla.edu>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
	<50CD00AB.7060107@cs.ucla.edu>
	<CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
	<50CD1343.6050601@cs.ucla.edu>
Date: Sat, 15 Dec 2012 20:46:40 -1000
Message-ID: <CAF1jjLvCjv8Q8FK1yZU3rR_TweKBkQBeKjqD5CCjp=nORBm5Yw@mail.gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
From: NightStrike <nightstrike@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.214.41
Cc: noloader@gmail.com, "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 06:46:51 -0000

On Sat, Dec 15, 2012 at 2:18 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 12/15/2012 03:08 PM, Jeffrey Walton wrote:
>>
>> Is the program designed to remove old core
>> files as part of the autoconf process?
>
>
> No, new cores.  'configure' regularly generates
> programs that dump core, as part of its ordinary
> working procedure.

Why not just use ulimit to not dump core?  Or is that a bashism and not a shism?


From MAILER-DAEMON Sun Dec 16 10:06:45 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TkFnh-0002yr-2b
	for mharc-autoconf@gnu.org; Sun, 16 Dec 2012 10:06:45 -0500
Received: from eggs.gnu.org ([208.118.235.92]:43437)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TkFnd-0002wI-Pg
	for autoconf@gnu.org; Sun, 16 Dec 2012 10:06:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TkFnc-0007jl-B0
	for autoconf@gnu.org; Sun, 16 Dec 2012 10:06:41 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:36507)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TkFnc-0007it-18
	for autoconf@gnu.org; Sun, 16 Dec 2012 10:06:40 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qBGF6M1C017743; Sun, 16 Dec 2012 09:06:23 -0600 (CST)
Date: Sun, 16 Dec 2012 09:06:22 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: NightStrike <nightstrike@gmail.com>
Subject: Re: RE : RE : rm -f core cause some troubles
In-Reply-To: <CAF1jjLvCjv8Q8FK1yZU3rR_TweKBkQBeKjqD5CCjp=nORBm5Yw@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1212160903050.19664@freddy.simplesystems.org>
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
	<50CD00AB.7060107@cs.ucla.edu>
	<CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
	<50CD1343.6050601@cs.ucla.edu>
	<CAF1jjLvCjv8Q8FK1yZU3rR_TweKBkQBeKjqD5CCjp=nORBm5Yw@mail.gmail.com>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Sun, 16 Dec 2012 09:06:23 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: Paul Eggert <eggert@cs.ucla.edu>, "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 15:06:42 -0000

On Sat, 15 Dec 2012, NightStrike wrote:

> On Sat, Dec 15, 2012 at 2:18 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
>> On 12/15/2012 03:08 PM, Jeffrey Walton wrote:
>>>
>>> Is the program designed to remove old core
>>> files as part of the autoconf process?
>>
>>
>> No, new cores.  'configure' regularly generates
>> programs that dump core, as part of its ordinary
>> working procedure.
>
> Why not just use ulimit to not dump core?  Or is that a bashism and not a shism?

The ulimit approach seems useful.

Blindly trying to remove a file named 'core' seems somewhat silly 
since many OSs do not write a file named 'core'.  Instead they write a 
core file with some other file name or even write all core files to 
some other directory on the system.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Sun Dec 16 12:49:48 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TkILU-0006Kr-N1
	for mharc-autoconf@gnu.org; Sun, 16 Dec 2012 12:49:48 -0500
Received: from eggs.gnu.org ([208.118.235.92]:38270)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TkILS-0006Jd-5N
	for autoconf@gnu.org; Sun, 16 Dec 2012 12:49:46 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TkILR-0004ln-6g
	for autoconf@gnu.org; Sun, 16 Dec 2012 12:49:46 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:42801)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TkILR-0004lf-0f
	for autoconf@gnu.org; Sun, 16 Dec 2012 12:49:45 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 57EF939E810E;
	Sun, 16 Dec 2012 09:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pYyBWwE-J-n8; Sun, 16 Dec 2012 09:49:43 -0800 (PST)
Received: from [192.168.1.6] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id E30B739E8109;
	Sun, 16 Dec 2012 09:49:42 -0800 (PST)
Message-ID: <50CE09B2.9050702@cs.ucla.edu>
Date: Sun, 16 Dec 2012 09:49:38 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Subject: Re: RE : RE : rm -f core cause some troubles
References: <87r4n0q0j1.fsf@synchrotron-soleil.fr>
	<50C37888.2080002@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E76B@SUN-DAG1.synchrotron-soleil.fr>
	<50C39F60.7040702@cs.ucla.edu>
	<A2A20EC3B8560D408356CAC2FC148E5358E1E7A5@SUN-DAG1.synchrotron-soleil.fr>
	<50C3D10A.3000604@cs.ucla.edu>
	<CAF6bG8fMEWd3NDtwR3HDkOaX1pbP8ZLnHzxPf8KVP=3qME6O2Q@mail.gmail.com>
	<CAH8yC8mai3=PjmpCDCRD36+ZEZW7AUygfwUkDy+1edAQe6Njog@mail.gmail.com>
	<50C5E54E.1080103@redhat.com>
	<CAH8yC8kAMdeL=kFMGbnbf0=P5c_Pu9TNUO558qm=NfY9Fagptw@mail.gmail.com>
	<50CD00AB.7060107@cs.ucla.edu>
	<CAH8yC8k_dk2g8r72HVFCQzP2+GBDj2HPFri+016ZTQ=-_npB3g@mail.gmail.com>
	<50CD1343.6050601@cs.ucla.edu>
	<CAF1jjLvCjv8Q8FK1yZU3rR_TweKBkQBeKjqD5CCjp=nORBm5Yw@mail.gmail.com>
	<alpine.GSO.2.01.1212160903050.19664@freddy.simplesystems.org>
In-Reply-To: <alpine.GSO.2.01.1212160903050.19664@freddy.simplesystems.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: "autoconf@gnu.org" <autoconf@gnu.org>, NightStrike <nightstrike@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 17:49:47 -0000

On 12/16/2012 07:06 AM, Bob Friesenhahn wrote:
>> Why not just use ulimit to not dump core?  Or is that a bashism and not a shism?
>
> The ulimit approach seems useful.

Yes, that would be nice to add, if someone writes
a patch.  I doubt whether it'd work everywhere, though.
  
> Instead they write a core file with some other file name

Autoconf-generated 'configure' scripts remove the commonly-used
file names for core files.

> or even write all core files to some other directory on the system.

It doesn't catch those.


From MAILER-DAEMON Sun Dec 16 17:24:17 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TkMd7-0001lo-Ge
	for mharc-autoconf@gnu.org; Sun, 16 Dec 2012 17:24:17 -0500
Received: from eggs.gnu.org ([208.118.235.92]:46200)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkMd5-0001li-N6
	for Autoconf@gnu.org; Sun, 16 Dec 2012 17:24:16 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkMd4-0001Px-NZ
	for Autoconf@gnu.org; Sun, 16 Dec 2012 17:24:15 -0500
Received: from mail-vc0-f169.google.com ([209.85.220.169]:40663)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkMd4-0001Pt-JO
	for Autoconf@gnu.org; Sun, 16 Dec 2012 17:24:14 -0500
Received: by mail-vc0-f169.google.com with SMTP id gb23so6486651vcb.0
	for <Autoconf@gnu.org>; Sun, 16 Dec 2012 14:24:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=RC5Uvhaj/ucYx4v7+dv4cwzJG8ksjK4mCIHw/kXf2kQ=;
	b=mQxJSXIOmIqQ617mAid6a979EU8jS/7qZnj2nQoyKMzQ4EdNDwtnfCIjDk0YFpROUz
	v2Pq+wuyBYygNxIzFkE4mMw56VbT8p/g7QXt5JmmejW52b0AHDRDw6ayVUrd3UCMBp2y
	fS0jBM1JNoQo7usApJaJncW7sdy2/RVikp430yxX469o1dG5fgZ8BLW4tp+HvzPPq/SP
	4JbshcAX10peV1jRrwKuo/7cnBjDTYhVv4bqUy1d4Y/rBCxFgf1vlS+cNlxvdixsVrpI
	YuR8k43jgNBTZ9/ldHVe8/1rk2e3lxKIqlXs3SJAEdd7j23XtIxAYgh3vKBDZxWTC/IK
	6iHg==
MIME-Version: 1.0
Received: by 10.52.36.167 with SMTP id r7mr17422377vdj.108.1355696653960; Sun,
	16 Dec 2012 14:24:13 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Sun, 16 Dec 2012 14:24:13 -0800 (PST)
In-Reply-To: <87hanmzptl.fsf@rho.meyering.net>
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
	<87txrwqm85.fsf@rho.meyering.net> <87mwxezrpx.fsf@rho.meyering.net>
	<50CD30F4.5070703@cs.ucla.edu> <87hanmzptl.fsf@rho.meyering.net>
Date: Sun, 16 Dec 2012 17:24:13 -0500
Message-ID: <CAH8yC8nDCMrp9yaRnmN8izhr3d7iKRVtO3m+4fRNNPmJXODviA@mail.gmail.com>
Subject: Re: Future autoconf package compression
From: Jeffrey Walton <noloader@gmail.com>
To: Jim Meyering <jim@meyering.net>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.220.169
Cc: Autoconf <Autoconf@gnu.org>, Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 22:24:16 -0000

On Sat, Dec 15, 2012 at 9:35 PM, Jim Meyering <jim@meyering.net> wrote:
> Paul Eggert wrote:
>> On 12/15/2012 05:54 PM, Jim Meyering wrote:
>>> FYI, a couple of weeks ago, Aki Helin exposed still more problems in
>>> gzip's unpacking code.
>>
>> Well, to be fair, I also have a similar problem with 'tar'
>> in my inbox, from Aki, but I'm not inclined to suggest that
>> we stop using 'tar'....
>
> Of course.  Nor am I.
> GNU tar's overall code quality is far higher than that of gzip.
-Wall -Wextra -Wconversion -Wstrict-overflow go a long way in
uncovering basic developer problems, like truncations, conversions,
and 2's compliment behavior. Everyone - from GNU to private
development teams - could benefit from the illumination of issues by
the toolchain's warning system.

I understand the warning system produces false positives at times, but
I don't throw the baby out with the bath water. I work around the
warning system's short comings in an effort to keep code quality up.
Its what we have to do to separate the wheat from the chaff.

 Its too bad they are not used more often.

Jeff


From MAILER-DAEMON Sun Dec 16 17:51:54 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TkN3q-0007xU-2M
	for mharc-autoconf@gnu.org; Sun, 16 Dec 2012 17:51:54 -0500
Received: from eggs.gnu.org ([208.118.235.92]:49680)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1TkN3n-0007xK-R7
	for Autoconf@gnu.org; Sun, 16 Dec 2012 17:51:53 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1TkN3m-0008JX-GZ
	for Autoconf@gnu.org; Sun, 16 Dec 2012 17:51:51 -0500
Received: from mx.meyering.net ([88.168.87.75]:57574)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jim@meyering.net>) id 1TkN3m-0008JS-9G
	for Autoconf@gnu.org; Sun, 16 Dec 2012 17:51:50 -0500
Received: from rho.meyering.net (rho.meyering.net [127.0.0.1])
	by rho.meyering.net (Acme Bit-Twister) with ESMTP id 5C85E600DF;
	Sun, 16 Dec 2012 23:51:49 +0100 (CET)
From: Jim Meyering <jim@meyering.net>
To: Jeffrey Walton <noloader@gmail.com>
Subject: Re: Future autoconf package compression
In-Reply-To: <CAH8yC8nDCMrp9yaRnmN8izhr3d7iKRVtO3m+4fRNNPmJXODviA@mail.gmail.com>
	(Jeffrey Walton's message of "Sun, 16 Dec 2012 17:24:13 -0500")
References: <CAF6bG8eZN=TF-BpKhxQ5zCy1zyc4Kd-ri-_=bYGv6iQ4ArjfbA@mail.gmail.com>
	<alpine.GSO.2.01.1211240930580.19664@freddy.simplesystems.org>
	<87txrwqm85.fsf@rho.meyering.net> <87mwxezrpx.fsf@rho.meyering.net>
	<50CD30F4.5070703@cs.ucla.edu> <87hanmzptl.fsf@rho.meyering.net>
	<CAH8yC8nDCMrp9yaRnmN8izhr3d7iKRVtO3m+4fRNNPmJXODviA@mail.gmail.com>
Date: Sun, 16 Dec 2012 23:51:49 +0100
Message-ID: <87licxwqyi.fsf@rho.meyering.net>
Lines: 40
MIME-Version: 1.0
Content-Type: text/plain
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 88.168.87.75
Cc: Autoconf <Autoconf@gnu.org>, Marko Lindqvist <cazfi74@gmail.com>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 22:51:53 -0000

Jeffrey Walton wrote:

> On Sat, Dec 15, 2012 at 9:35 PM, Jim Meyering <jim@meyering.net> wrote:
>> Paul Eggert wrote:
>>> On 12/15/2012 05:54 PM, Jim Meyering wrote:
>>>> FYI, a couple of weeks ago, Aki Helin exposed still more problems in
>>>> gzip's unpacking code.
>>>
>>> Well, to be fair, I also have a similar problem with 'tar'
>>> in my inbox, from Aki, but I'm not inclined to suggest that
>>> we stop using 'tar'....
>>
>> Of course.  Nor am I.
>> GNU tar's overall code quality is far higher than that of gzip.
> -Wall -Wextra -Wconversion -Wstrict-overflow go a long way in
> uncovering basic developer problems, like truncations, conversions,
> and 2's compliment behavior. Everyone - from GNU to private
> development teams - could benefit from the illumination of issues by
> the toolchain's warning system.
>
> I understand the warning system produces false positives at times, but
> I don't throw the baby out with the bath water. I work around the
> warning system's short comings in an effort to keep code quality up.
> Its what we have to do to separate the wheat from the chaff.
>
>  Its too bad they are not used more often.

If you have noticed real problems in tar or gzip (or any other
GNU project) about which gcc can warn, please let us know.

It sounds like you are trying to teach grandma how to suck eggs :-)

Did you realize that several GNU projects now enable virtually
every gcc warning that is available (even including those that
are new in the upcoming gcc-4.8, for folks that use bleeding edge gcc)
via gnulib's manywarnings.m4 configure-time tests?

Of course, there is a list of warnings that we do disable,
due to their typical lack of utility and the invasiveness
of changes required do suppress them.


From MAILER-DAEMON Tue Dec 18 00:28:00 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tkpii-00063P-5F
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 00:28:00 -0500
Received: from eggs.gnu.org ([208.118.235.92]:49367)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1Tkpie-000607-T5
	for autoconf@gnu.org; Tue, 18 Dec 2012 00:27:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1Tkpid-0000pR-Pk
	for autoconf@gnu.org; Tue, 18 Dec 2012 00:27:56 -0500
Received: from aibo.runbox.com ([91.220.196.211]:49309)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1Tkpid-0000pJ-JM
	for autoconf@gnu.org; Tue, 18 Dec 2012 00:27:55 -0500
Received: from [10.9.9.131] (helo=fenris.runbox.com)
	by bars.runbox.com with esmtp (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1Tkpib-0001oS-T9
	for autoconf@gnu.org; Tue, 18 Dec 2012 06:27:53 +0100
Received: from mail by fenris.runbox.com with local  (Exim 4.50)
	id 1Tkpiw-0005D8-5E
	for autoconf@gnu.org; Tue, 18 Dec 2012 06:28:14 +0100
Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received: from [108.45.113.66] by secure.runbox.com with http (uid:258406)
	(RMM 4.0); for <autoconf@gnu.org>; Tue, 18 Dec 2012 05:28:14 GMT
From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: autoconf@gnu.org
Subject: Enabling compiler warning flags
Date: Tue, 18 Dec 2012 00:28:14 -0500 (EST)
X-Mailer: RMM
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
In-Reply-To: <mailman.25.1355763603.26155.autoconf@gnu.org>
Message-Id: <E1Tkpiw-0005D8-5E@fenris.runbox.com>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 91.220.196.211
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: dwheeler@dwheeler.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 05:27:58 -0000

Jim Meyering said:
> Did you realize that several GNU projects now enable virtually
> every gcc warning that is available (even including those that
> are new in the upcoming gcc-4.8, for folks that use bleeding edge gcc)
> via gnulib's manywarnings.m4 configure-time tests?
>=20
> Of course, there is a list of warnings that we do disable,
> due to their typical lack of utility and the invasiveness
> of changes required do suppress them.

Is there any way that the autoconf (or automake) folks could make compiler =
warnings much, much easier to enable?  Preferably enabled by default when y=
ou start packaging something? For example, could gnulib warnings and manywa=
rnings be distributed and enabled as *part* of autoconf? If not, could auto=
conf at least strongly advertize the existence of these, and include specif=
ic instructions to people on how to quickly install it? The autoconf sectio=
n on "gnulib" never even *MENTIONS* the "warnings" and "manywarnings" stuff=
!  And while automake has warnings, they are for the automake configuration=
 file... not for compilation.

Compiler warning flags cost nearly nothing to turn on when you're *starting=
* a project, but they're harder to enable later (a thousand warnings about =
the same thing later is harder than fixing it the first time). And while so=
me warnings are nonsense, their use can make the resulting software much, m=
uch better. If we got people to turn on warning flags all over the place, d=
uring development, a lot of bugs would simply disappear.

--- David A. Wheeler


From MAILER-DAEMON Tue Dec 18 01:10:20 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TkqNg-0001bT-5K
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 01:10:20 -0500
Received: from eggs.gnu.org ([208.118.235.92]:53313)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkqNc-0001a0-EZ
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:10:18 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkqNb-0002SB-0S
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:10:16 -0500
Received: from mail-vc0-f173.google.com ([209.85.220.173]:53865)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkqNa-0002S6-SP
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:10:14 -0500
Received: by mail-vc0-f173.google.com with SMTP id f13so347629vcb.18
	for <autoconf@gnu.org>; Mon, 17 Dec 2012 22:10:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type:content-transfer-encoding;
	bh=93l7CVIhVd9stwAQTMS7eFuayyK+Lk90F8teBu2Iw0w=;
	b=LfPz8hDnl7VYA0wijF90NJRxw+zBK0G8+71JZkP8uGmoHtvZAp3nj2b+/M1W9q79lm
	Am9aZt/J1SzrSEWa9dkATQLtYFOpecHvptU2Tdfo6A6uEkwOdI65W9hLyr2xgKQ8RU4/
	9xfuKJZA1WL1G7keARnSo55ZY7Ncl7obPMLy2CZ/5/4Dgfdc/FhDMRwByY/EZhJeTW+H
	I1lhIhbVOD/LNu+bSyIx7ramjcscs5H2Eb0/mtk+yMptAT7Qf5mBpQdiafefoDZJAK3N
	n1uVPZCVIg7vHNqisKKIs5J1Y8j76r66U+nIg65yD1G4qZR2X0w7akbpYYqod+wojwjz
	JWfA==
MIME-Version: 1.0
Received: by 10.220.225.132 with SMTP id is4mr1235542vcb.47.1355811014123;
	Mon, 17 Dec 2012 22:10:14 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Mon, 17 Dec 2012 22:10:14 -0800 (PST)
In-Reply-To: <E1Tkpiw-0005D8-5E@fenris.runbox.com>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
Date: Tue, 18 Dec 2012 01:10:14 -0500
Message-ID: <CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: dwheeler@dwheeler.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.220.173
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 06:10:18 -0000

On Tue, Dec 18, 2012 at 12:28 AM, David A. Wheeler
<dwheeler@dwheeler.com> wrote:
> Jim Meyering said:
>> Did you realize that several GNU projects now enable virtually
>> every gcc warning that is available (even including those that
>> are new in the upcoming gcc-4.8, for folks that use bleeding edge gcc)
>> via gnulib's manywarnings.m4 configure-time tests?
>>
>> Of course, there is a list of warnings that we do disable,
>> due to their typical lack of utility and the invasiveness
>> of changes required do suppress them.
>
> Is there any way that the autoconf (or automake) folks could make compile=
r warnings much, much easier to enable?  Preferably enabled by default when=
 you start packaging something? For example, could gnulib warnings and many=
warnings be distributed and enabled as *part* of autoconf? If not, could au=
toconf at least strongly advertize the existence of these, and include spec=
ific instructions to people on how to quickly install it? The autoconf sect=
ion on "gnulib" never even *MENTIONS* the "warnings" and "manywarnings" stu=
ff!  And while automake has warnings, they are for the automake configurati=
on file... not for compilation.
>
> Compiler warning flags cost nearly nothing to turn on when you're *starti=
ng* a project, but they're harder to enable later (a thousand warnings abou=
t the same thing later is harder than fixing it the first time). And while =
some warnings are nonsense, their use can make the resulting software much,=
 much better. If we got people to turn on warning flags all over the place,=
 during development, a lot of bugs would simply disappear.
>
If you are going to try the waters with warnings, you should also
consider the flags to integrate with platform security.

Platform security integration includes fortified sources and stack
protectors. Here are the flags of interest:
  * -fstack-protector-all
  * -z,noexecstack
  * -z,noexecheap (or other measure, such as W^X)
  * -z,relro
  * -z,now
  * -fPIE and -pie for executables

FORTIFY_SOURCE=3D2 (FORTIFY_SOURCE=3D1 on Android 4.1+), where available.
I know Drepper objects to the safer string/memory functions, but his
way (the way of 1970's strcpy and strcat) simply does not work. I
don't disagree that the safer functions are not completely safe, but I
refuse to throw the baby out with the bath water.

These measures would have stopped a number of recent high profile
0-days and security vulnerabilities, including those against MySQL
(http://seclists.org/bugtraq/2012/Dec/12 and
http://seclists.org/bugtraq/2012/Dec/11) and Pidigin
(http://seclists.org/fulldisclosure/2012/Jul/183).

For those who think its over the top, then let them shoot themselves
in the foot by backing off security integration. Consider: Drepper is
an expert, and even his loader and runtime library make appearances on
Bugtraq and Full Disclosure. Mere mortals (like me and many other
developers) need the integration to help build a secure system.

A hardened or secure toolchain should be a part of every developer's
warchest. It starts with the tools like Autoconf.

Jeff


From MAILER-DAEMON Tue Dec 18 01:16:51 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TkqTz-0002Uu-Tf
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 01:16:51 -0500
Received: from eggs.gnu.org ([208.118.235.92]:54053)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1TkqTx-0002T5-Fk
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:16:50 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1TkqTw-0004BP-AB
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:16:49 -0500
Received: from smtp1.stanford.edu ([171.67.219.81]:59328
	helo=smtp.stanford.edu) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1TkqTw-0004B7-50
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:16:48 -0500
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with SMTP id A175212D3EE;
	Mon, 17 Dec 2012 22:16:46 -0800 (PST)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.stanford.edu (Postfix) with ESMTPS id 27F9712D3F1;
	Mon, 17 Dec 2012 22:16:46 -0800 (PST)
Received: by windlord.stanford.edu (Postfix, from userid 1000)
	id EA8D72F5F3; Mon, 17 Dec 2012 22:16:42 -0800 (PST)
From: Russ Allbery <rra@stanford.edu>
To: noloader@gmail.com
Subject: Re: Enabling compiler warning flags
In-Reply-To: <CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	(Jeffrey Walton's message of "Tue, 18 Dec 2012 01:10:14 -0500")
Organization: The Eyrie
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Mon, 17 Dec 2012 22:16:42 -0800
Message-ID: <87sj73j35h.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 171.67.219.81
Cc: autoconf@gnu.org, dwheeler@dwheeler.com
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 06:16:50 -0000

Jeffrey Walton <noloader@gmail.com> writes:

> FORTIFY_SOURCE=2 (FORTIFY_SOURCE=1 on Android 4.1+), where available.
> I know Drepper objects to the safer string/memory functions, but his
> way (the way of 1970's strcpy and strcat) simply does not work. I
> don't disagree that the safer functions are not completely safe, but I
> refuse to throw the baby out with the bath water.

Having tried both styles, what works even better than replacing strcpy and
strcat with strlcpy and strlcat, or the new *_s functions, is to replace
them with asprintf.  You have to do a little bit of work to be guaranteed
to have asprintf (or a lot of work if you want to support platforms with a
broken snprintf as well), but gnulib will do it for you, and that coding
style is so much nicer than trying to deal with static buffers and
worrying about truncation, particularly if you design the software with
that in mind from the start.  Yes, it's probably slower, but I'll trade
speed for clarity and safety nearly all of the time.

(Or you could also dodge the memory management problems by using a C
framework that supports garbage collection, like APR, but that's farther
afield of this list.)

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>


From MAILER-DAEMON Tue Dec 18 01:23:38 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TkqaY-0003FF-Op
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 01:23:38 -0500
Received: from eggs.gnu.org ([208.118.235.92]:54847)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkqaV-0003D0-Fd
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:23:36 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkqaU-0005gA-Ed
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:23:35 -0500
Received: from mail-vb0-f46.google.com ([209.85.212.46]:35177)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TkqaU-0005g3-AJ
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:23:34 -0500
Received: by mail-vb0-f46.google.com with SMTP id b13so353568vby.19
	for <autoconf@gnu.org>; Mon, 17 Dec 2012 22:23:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=k98xeFtDb+5KFTAzR2fXuVf0NgeSu2daZfNxRpzmQMg=;
	b=XtDqvVexZmWsMJHe6+guMbkO2awzw2+9XLGT+eQiw5t4DztEOpelwcQDYDCzBz7D7O
	aXtxEzuZsFbj0+M6Wn95zy265bjI/xYAsBDGMCha6/wIyAQUwVMSp4cgk35gPubVl+EH
	S39y7JasW2welc51p1R0NVDfNCAbIsEe3pV2atEaJL22QfkdV6aWIipBSDKxdSIv5A85
	3goTgpERzW6gTG3fII+SMPQF6eXtLyAmGcDrxpot2f8e1lsA2YWB9hyIDBkKsIhEDWdQ
	vg3gPfC2oBG9CXF8u51HGnU6O6SkxEgV0ZSzKgumI4hGEdgcvXsbmy7NhvLK6vZIT8cY
	wmAQ==
MIME-Version: 1.0
Received: by 10.52.36.167 with SMTP id r7mr1070397vdj.108.1355811813876; Mon,
	17 Dec 2012 22:23:33 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Mon, 17 Dec 2012 22:23:33 -0800 (PST)
In-Reply-To: <87sj73j35h.fsf@windlord.stanford.edu>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<87sj73j35h.fsf@windlord.stanford.edu>
Date: Tue, 18 Dec 2012 01:23:33 -0500
Message-ID: <CAH8yC8kitScM35RjEf1be4RBEpunovFhykp+xni1ega98rgW9w@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: Russ Allbery <rra@stanford.edu>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.46
Cc: autoconf@gnu.org, dwheeler@dwheeler.com
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 06:23:37 -0000

On Tue, Dec 18, 2012 at 1:16 AM, Russ Allbery <rra@stanford.edu> wrote:
> Jeffrey Walton <noloader@gmail.com> writes:
>
>> FORTIFY_SOURCE=2 (FORTIFY_SOURCE=1 on Android 4.1+), where available.
>> I know Drepper objects to the safer string/memory functions, but his
>> way (the way of 1970's strcpy and strcat) simply does not work. I
>> don't disagree that the safer functions are not completely safe, but I
>> refuse to throw the baby out with the bath water.
>
> Having tried both styles, what works even better than replacing strcpy and
> strcat with strlcpy and strlcat, or the new *_s functions, is to replace
> them with asprintf.  You have to do a little bit of work to be guaranteed
> to have asprintf (or a lot of work if you want to support platforms with a
> broken snprintf as well), but gnulib will do it for you, and that coding
> style is so much nicer than trying to deal with static buffers and
> worrying about truncation, particularly if you design the software with
> that in mind from the start.  Yes, it's probably slower, but I'll trade
> speed for clarity and safety nearly all of the time.
Yeah, I think you are right about asprintf (though I have never used it).

I can't count how many times I've seen silent truncation due to
sprint. Most recently, I pointed it out on some SE Android patches
(Android port of SE Linux) that passed by the NSA sponsored mailing
list. They went unfixed. Amazing.

Jeff


From MAILER-DAEMON Tue Dec 18 01:30:06 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tkqgo-0004bp-VM
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 01:30:06 -0500
Received: from eggs.gnu.org ([208.118.235.92]:55551)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1Tkqgl-0004Zt-8G
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:30:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1Tkqgi-0007KJ-IS
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:30:02 -0500
Received: from smtp1.stanford.edu ([171.67.219.81]:32939
	helo=smtp.stanford.edu) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1Tkqgi-0007KD-CZ
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:30:00 -0500
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with SMTP id AF30912D476;
	Mon, 17 Dec 2012 22:29:59 -0800 (PST)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.stanford.edu (Postfix) with ESMTPS id 6F34F12D43D;
	Mon, 17 Dec 2012 22:29:59 -0800 (PST)
Received: by windlord.stanford.edu (Postfix, from userid 1000)
	id 4F6A52F5F3; Mon, 17 Dec 2012 22:29:58 -0800 (PST)
From: Russ Allbery <rra@stanford.edu>
To: noloader@gmail.com
Subject: Re: Enabling compiler warning flags
In-Reply-To: <CAH8yC8kitScM35RjEf1be4RBEpunovFhykp+xni1ega98rgW9w@mail.gmail.com>
	(Jeffrey Walton's message of "Tue, 18 Dec 2012 01:23:33 -0500")
Organization: The Eyrie
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<87sj73j35h.fsf@windlord.stanford.edu>
	<CAH8yC8kitScM35RjEf1be4RBEpunovFhykp+xni1ega98rgW9w@mail.gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Mon, 17 Dec 2012 22:29:58 -0800
Message-ID: <87hanjj2jd.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 171.67.219.81
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 06:30:05 -0000

Jeffrey Walton <noloader@gmail.com> writes:

> Yeah, I think you are right about asprintf (though I have never used it).

> I can't count how many times I've seen silent truncation due to sprint.
> Most recently, I pointed it out on some SE Android patches (Android port
> of SE Linux) that passed by the NSA sponsored mailing list. They went
> unfixed. Amazing.

Silent truncation is the primary reason why strlcpy and strlcat aren't in
glibc.  Both functions are designed to silently truncate when the target
buffer isn't large enough, and few callers deal with that.  This
ironically can actually create other types of security vulnerabilities
(although it's probably less likely to do so than a stack overflow).

asprintf guarantees that you don't have silent truncation; either you run
out of memory and the operation fails, or you get the whole string.  The
cost, of course, is that you now have to do explicit memory management,
which is often what people were trying to avoid by using static buffers.
But it *is* C; if you're not going to embrace explicit memory management,
you may have picked the wrong programming language....  :)

strlcpy and strlcat have some benefit in situations where you're trying to
add some robustness (truncation instead of overflow) to code with
existing, broken APIs that you can't change, which I suspect was some of
the original motivation.  But if you can design the APIs from the start,
I'd always use strdup and asprintf (or something more sophisticated like
obstacks or APR pools) instead.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>


From MAILER-DAEMON Tue Dec 18 01:44:55 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tkqv9-0006lq-So
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 01:44:55 -0500
Received: from eggs.gnu.org ([208.118.235.92]:57568)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tkqv7-0006lj-Cx
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:44:55 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tkqv6-0002UR-Bw
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:44:53 -0500
Received: from smtp.gentoo.org ([140.211.166.183]:44921)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tkqv6-0002TN-6S
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:44:52 -0500
Received: from vapier.localnet (localhost [127.0.0.1])
	by smtp.gentoo.org (Postfix) with ESMTP id AFC6333DA5A;
	Tue, 18 Dec 2012 06:44:49 +0000 (UTC)
From: Mike Frysinger <vapier@gentoo.org>
Organization: wh0rd.org
To: autoconf@gnu.org,
 noloader@gmail.com
Subject: Re: Enabling compiler warning flags
Date: Tue, 18 Dec 2012 01:44:48 -0500
User-Agent: KMail/1.13.7 (Linux/3.7.1; KDE/4.6.5; x86_64; ; )
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
In-Reply-To: <CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart3721426.5lJPdSxH3P";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201212180144.49550.vapier@gentoo.org>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 140.211.166.183
Cc: dwheeler@dwheeler.com
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 06:44:55 -0000

--nextPart3721426.5lJPdSxH3P
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Tuesday 18 December 2012 01:10:14 Jeffrey Walton wrote:
> If you are going to try the waters with warnings, you should also
> consider the flags to integrate with platform security.
>=20
> Platform security integration includes fortified sources and stack
> protectors. Here are the flags of interest:
>   * -fstack-protector-all
>   * -z,noexecstack
>   * -z,noexecheap (or other measure, such as W^X)
>   * -z,relro
>   * -z,now
>   * -fPIE and -pie for executables

if you do choose to add these to your configure script, you should provide =
a=20
flag to control the behavior (default enabling is OK).  some of these are n=
ot=20
cheap, especially for some architectures.
=2Dmike

--nextPart3721426.5lJPdSxH3P
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAABAgAGBQJQ0BDhAAoJEEFjO5/oN/WBt4EQAMroQkRgEtoo4S5F5XDHdZOz
XKSAgBDsjIlyvgkLA76+ZMMoLvsY8tq7PN6MYcjBtar4YPBYsORInBb3mHJj9VN7
T7Hnr9G0UmELgiQb9/JrbXQqTM64tioLxjP0/hlze2nTNEPAvbYHVTLA7FdD6RUm
XXXJIziiQtGbwjHzVlniBUioptc6GKl6ulOqleQSUb04WmXC5ViPU5lwFCPevYUu
NPDQSSIwOGWlxpEVbzAxwBGLrBdeprx2gkv2tZyFyTQ41K2w975uS1qdoCvn9fvh
LTO+ls+08rptIGmbTnBEszizO/UuKI/z8S+7zM8XnH2ZSnAyIDFIGbSHB9/ysaEd
f34zqxo9+oTx8A5eoxhc9gOh8rTD/RMM1CTWM98WLUgdhVN8uNMc05GFV+IaD0Rf
KjOoR7oVrNHPFd0JbRVfUj6Q2bIWJCk1L+4QZwx5x2eIj0r1bVVqhcamXS3ugAVG
TACxhHXcO7FUkX58LoPS3G4K/TQK8rbnOIoNKSlzM8AQJf5Qj/P+k2jJCPfBAlmq
U4KxsHunitIQ4sZ9ntPdTgIB/GVqa0MzavVCqUkDar5xt1mS8k+x0R4h4CQ2aZG0
NyMS4JhYGdH1bWabX5y2smnnqaw7KgnnSkpVZZycmYSKEIQQ4fRaeqQ4U2aNdcOs
8ECio/DAlJy/WL2fyDHd
=YMr1
-----END PGP SIGNATURE-----

--nextPart3721426.5lJPdSxH3P--


From MAILER-DAEMON Tue Dec 18 01:46:54 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tkqx4-0007HU-8Y
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 01:46:54 -0500
Received: from eggs.gnu.org ([208.118.235.92]:57835)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tkqx0-0007G3-HP
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:46:52 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tkqwz-00037W-Al
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:46:50 -0500
Received: from smtp.gentoo.org ([140.211.166.183]:45029)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tkqwz-00037R-4R
	for autoconf@gnu.org; Tue, 18 Dec 2012 01:46:49 -0500
Received: from vapier.localnet (localhost [127.0.0.1])
	by smtp.gentoo.org (Postfix) with ESMTP id 8030F33DABB;
	Tue, 18 Dec 2012 06:46:48 +0000 (UTC)
From: Mike Frysinger <vapier@gentoo.org>
Organization: wh0rd.org
To: autoconf@gnu.org,
 dwheeler@dwheeler.com
Subject: Re: Enabling compiler warning flags
Date: Tue, 18 Dec 2012 01:46:47 -0500
User-Agent: KMail/1.13.7 (Linux/3.7.1; KDE/4.6.5; x86_64; ; )
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
In-Reply-To: <E1Tkpiw-0005D8-5E@fenris.runbox.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1620933.8ysN0fbunH";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201212180146.48401.vapier@gentoo.org>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 140.211.166.183
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 06:46:52 -0000

--nextPart1620933.8ysN0fbunH
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Tuesday 18 December 2012 00:28:14 David A. Wheeler wrote:
> Jim Meyering said:
> > Did you realize that several GNU projects now enable virtually
> > every gcc warning that is available (even including those that
> > are new in the upcoming gcc-4.8, for folks that use bleeding edge gcc)
> > via gnulib's manywarnings.m4 configure-time tests?
> >=20
> > Of course, there is a list of warnings that we do disable,
> > due to their typical lack of utility and the invasiveness
> > of changes required do suppress them.
>=20
> Is there any way that the autoconf (or automake) folks could make compiler
> warnings much, much easier to enable?  Preferably enabled by default when
> you start packaging something? For example, could gnulib warnings and
> manywarnings be distributed and enabled as *part* of autoconf? If not,
> could autoconf at least strongly advertize the existence of these, and
> include specific instructions to people on how to quickly install it? The
> autoconf section on "gnulib" never even *MENTIONS* the "warnings" and
> "manywarnings" stuff!  And while automake has warnings, they are for the
> automake configuration file... not for compilation.
>=20
> Compiler warning flags cost nearly nothing to turn on when you're
> *starting* a project, but they're harder to enable later (a thousand
> warnings about the same thing later is harder than fixing it the first
> time). And while some warnings are nonsense, their use can make the
> resulting software much, much better. If we got people to turn on warning
> flags all over the place, during development, a lot of bugs would simply
> disappear.

you might want to look at the autoconf-archive project:
http://www.gnu.org/software/autoconf-archive/

they provide AX_CFLAGS_WARN_ALL for starters, and then for more refined -W=
=20
flags, you can easily use AX_CHECK_COMPILE_FLAG.
=2Dmike

--nextPart1620933.8ysN0fbunH
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAABAgAGBQJQ0BFYAAoJEEFjO5/oN/WBEbwP/1Oi7eUVlMyh1N915O82nzMb
xULgoFK+SKgL31CiEkaxpAW/IliW+ZL8up/BF5d1m3fnWDGu/QtckgByzEtXokv6
FDDDgp0bwdpe1kMjvvzuP4dzibT0ofm1S+BLYZ8lByI3IhS9JtbL6MbQvc991wUu
8Ub7KLDDQuYzwhvof3fIltcOHTN59hi8NTa6wqkPqryXFV1Si/OMbP469HU6R47k
miwFN//0PhCHihsy+gwSpU1vCEGwBYjRgBYxQt3E/R7Q2OIYEFwQa0201upugU0a
dtAfI1xS+nSe72LoBieAplFhHNaXC5irVGRM5Uj+4XP13hbtM8+B4/TZuYvfDcz7
Y/Jk7h9dUCbpcK8LWp3pUYVMmtwiRUASnKCZ3izivPZToZj9+6VO/FqCAvJaWzwg
PIQM1hgxuiiHtMitrY4zx6JtGd3p1HV0yNILoimfDpuEdmRTEkOEiju9jhd/Du7B
WnvN219vZL4GT/sVmj0JUXo1geThhJqGqgmN3wHSWIeLqfv8FJab+cnC0z0tfUWC
3rrBfE+PfbCsCq7uDVH2a3VbPvfprWtTziJWK9zphH5I1TzwwEyOOt82fGFMgKbl
WAuryPQtW3KuNsztRRpwL6LVprktFLnUVeMksYens+MR5LOgpyqBsG+xXUfPSvZF
w+jfc8EfPlrTirhVk1vE
=Ogk5
-----END PGP SIGNATURE-----

--nextPart1620933.8ysN0fbunH--


From MAILER-DAEMON Tue Dec 18 02:55:28 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tks1Q-0005eu-J2
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 02:55:28 -0500
Received: from eggs.gnu.org ([208.118.235.92]:39920)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tks1N-0005eK-LG
	for autoconf@gnu.org; Tue, 18 Dec 2012 02:55:26 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tks1M-00035u-JA
	for autoconf@gnu.org; Tue, 18 Dec 2012 02:55:25 -0500
Received: from mail-vb0-f52.google.com ([209.85.212.52]:61140)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tks1M-00035d-Fj
	for autoconf@gnu.org; Tue, 18 Dec 2012 02:55:24 -0500
Received: by mail-vb0-f52.google.com with SMTP id ez10so428644vbb.25
	for <autoconf@gnu.org>; Mon, 17 Dec 2012 23:55:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=ge2FV4NP+BgGBRT1UT2A6R7Q9qzRZ1VyN92Wb3w/OIk=;
	b=l5hVWQ1inlfJAGy/mg9HXeUkQx6QIVc4IjJe9Eh1KQZzZXjwTbQzmWUfEKE3T9DqNC
	bFcqPlu27kMIngxaJduKz4Mk4bB3iNiKaJJ4YIjLiVodZwiwYO242sc6jo6mKTqGBBLI
	DkVo2i0CuU+Qlcit/1S/m7Rp10/5Gz5V0BiDelLByY9Y0rfd4DiEqtMvWFLExxtITns4
	AGpDv7R5rIjm7mQICDUHPhftkagoJxbVoM2bSmvBkV2RfFLDlUoZYw9HChlkXVpt2xtg
	Ux3R2wC+ztu0UG+prH90FHOcle58LhjdO0+n2RaGK2WkJEOGsP7w4zqA0mO9AIXKYlPZ
	UOPg==
MIME-Version: 1.0
Received: by 10.58.2.226 with SMTP id 2mr1514428vex.53.1355817323967; Mon, 17
	Dec 2012 23:55:23 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Mon, 17 Dec 2012 23:55:23 -0800 (PST)
In-Reply-To: <201212180144.49550.vapier@gentoo.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<201212180144.49550.vapier@gentoo.org>
Date: Tue, 18 Dec 2012 02:55:23 -0500
Message-ID: <CAH8yC8=LjCqXm5R2jcgck=iCu38VSMCyjtAtHxx2ZCKOy=m0Sw@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.52
Cc: autoconf@gnu.org, dwheeler@dwheeler.com
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 07:55:27 -0000

On Tue, Dec 18, 2012 at 1:44 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Tuesday 18 December 2012 01:10:14 Jeffrey Walton wrote:
>> If you are going to try the waters with warnings, you should also
>> consider the flags to integrate with platform security.
>>
>> Platform security integration includes fortified sources and stack
>> protectors. Here are the flags of interest:
>>   * -fstack-protector-all
>>   * -z,noexecstack
>>   * -z,noexecheap (or other measure, such as W^X)
>>   * -z,relro
>>   * -z,now
>>   * -fPIE and -pie for executables
>
> if you do choose to add these to your configure script, you should provide a
> flag to control the behavior (default enabling is OK).  some of these are not
> cheap, especially for some architectures.
Good point. A noexec stack or noexec heap can be costly if using PaX.

What abstractions does Autoconf have to identify platforms and
security measures so a maintainer can supply one configure that works
for all platforms and architectures? For example, noexec stacks should
be enabled by default on x86 and x64. To split hairs even further,
noexec stacks should be on by default for x86 and x64, while noexec
heaps should be in effect on Gentoo systems running on x86 and x64.

Leaving these security related decisions to developers has a history
of failures due to gaps in awareness and knowledge (confer: audit the
software at ftp.gnu.org). In this case, Autoconf can close the gap and
be part of the solution.

Jeff


From MAILER-DAEMON Tue Dec 18 13:43:15 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tl28J-0003zM-TC
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 13:43:15 -0500
Received: from eggs.gnu.org ([208.118.235.92]:43567)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tl28H-0003z7-KN
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:43:14 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tl28G-0003Lf-8u
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:43:13 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:43852)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tl28G-0003KV-16
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:43:12 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qBIIguEi004034; Tue, 18 Dec 2012 12:42:56 -0600 (CST)
Date: Tue, 18 Dec 2012 12:42:56 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: "David A. Wheeler" <dwheeler@dwheeler.com>
Subject: Re: Enabling compiler warning flags
In-Reply-To: <E1Tkpiw-0005D8-5E@fenris.runbox.com>
Message-ID: <alpine.GSO.2.01.1212181239340.28949@freddy.simplesystems.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Tue, 18 Dec 2012 12:42:56 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 18:43:14 -0000

On Tue, 18 Dec 2012, David A. Wheeler wrote:
>
> Compiler warning flags cost nearly nothing to turn on when you're 
> *starting* a project, but they're harder to enable later (a thousand 
> warnings about the same thing later is harder than fixing it the 
> first time). And while some warnings are nonsense, their use can 
> make the resulting software much, much better. If we got people to 
> turn on warning flags all over the place, during development, a lot 
> of bugs would simply disappear.

What might actually happen is that a bunch of casts get added to the 
code in order to quench the warnings.  These casts cause new bugs when 
the code is updated or they hide later attempts to find conversion 
issues.

It is pretty common that the person trying to eliminate a warning does 
not understand the code well enough to understand the consequences of 
their action or is interested in a quick fix.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Tue Dec 18 13:44:14 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tl29G-0004IO-Le
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 13:44:14 -0500
Received: from eggs.gnu.org ([208.118.235.92]:43939)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tl29C-0004Ga-Lc
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:44:12 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tl29B-0003Zz-E5
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:44:10 -0500
Received: from smtp.gentoo.org ([140.211.166.183]:35167)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vapier@gentoo.org>) id 1Tl29B-0003Zn-3f
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:44:09 -0500
Received: from vapier.localnet (localhost [127.0.0.1])
	by smtp.gentoo.org (Postfix) with ESMTP id 155B433DA5D;
	Tue, 18 Dec 2012 18:44:08 +0000 (UTC)
From: Mike Frysinger <vapier@gentoo.org>
Organization: wh0rd.org
To: noloader@gmail.com
Subject: Re: Enabling compiler warning flags
Date: Tue, 18 Dec 2012 13:44:01 -0500
User-Agent: KMail/1.13.7 (Linux/3.7.1; KDE/4.6.5; x86_64; ; )
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<201212180144.49550.vapier@gentoo.org>
	<CAH8yC8=LjCqXm5R2jcgck=iCu38VSMCyjtAtHxx2ZCKOy=m0Sw@mail.gmail.com>
In-Reply-To: <CAH8yC8=LjCqXm5R2jcgck=iCu38VSMCyjtAtHxx2ZCKOy=m0Sw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1894608.TEDFyppSZ4";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201212181344.07524.vapier@gentoo.org>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 140.211.166.183
Cc: autoconf@gnu.org, dwheeler@dwheeler.com
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 18:44:13 -0000

--nextPart1894608.TEDFyppSZ4
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Tuesday 18 December 2012 02:55:23 Jeffrey Walton wrote:
> On Tue, Dec 18, 2012 at 1:44 AM, Mike Frysinger wrote:
> > On Tuesday 18 December 2012 01:10:14 Jeffrey Walton wrote:
> >> If you are going to try the waters with warnings, you should also
> >> consider the flags to integrate with platform security.
> >>=20
> >> Platform security integration includes fortified sources and stack
> >>=20
> >> protectors. Here are the flags of interest:
> >>   * -fstack-protector-all
> >>   * -z,noexecstack
> >>   * -z,noexecheap (or other measure, such as W^X)
> >>   * -z,relro
> >>   * -z,now
> >>   * -fPIE and -pie for executables
> >=20
> > if you do choose to add these to your configure script, you should
> > provide a flag to control the behavior (default enabling is OK).  some
> > of these are not cheap, especially for some architectures.
>=20
> Good point. A noexec stack or noexec heap can be costly if using PaX.

those weren't the ones i was thinking of actually :).  the mainline kernel=
=20
itself handles the GNU_STACK segment, although it relies on hardware suppor=
t=20
for it.  if the hardware doesn't support it, then that's where PaX's softwa=
re=20
implementation might come into play.

> What abstractions does Autoconf have to identify platforms and
> security measures so a maintainer can supply one configure that works
> for all platforms and architectures?

if you use AC_CANONICAL_HOST, you get access to $host_os (e.g. "linux") and=
=20
$host_cpu (e.g. "x86_64").  but that's about it.

> For example, noexec stacks should
> be enabled by default on x86 and x64. To split hairs even further,
> noexec stacks should be on by default for x86 and x64, while noexec
> heaps should be in effect on Gentoo systems running on x86 and x64.

noexec is already enabled by default for all Linux/gcc/glibc targets.  ther=
e=20
should be no need for people to specify it themselves.  the only time it=20
really comes up anymore is if someone is writing pure assembly and didn't p=
ut=20
the prerequisite section in there.
=2Dmike

--nextPart1894608.TEDFyppSZ4
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAABAgAGBQJQ0Ll3AAoJEEFjO5/oN/WBgvwP/jkhaSp6AM3J3EFmztjdVZwC
R50B+H5suCwCk8kE4HKDdcsWZKJv/ye1SgUkZWdr/4Hin56NPApMRd0NqHjPb2E+
mtVWyt622U5rrJy3hzE1WMGT/i7S4l2A1tLiHKWEn/hWqv8moh0M4rDzsAThljsX
qWjCeBZeMK8LRtLNge8zLVOukPck6NiJwmR2N5nbuLrHJ2RRd7kpiUNCwawP7Oai
VeRC40WDFgX9sJfu4RQ60doLP/O728i0k4VVCOb1tfVHj44EHd1P+BwlEgVRlx19
W+XBjlQxUmKsDpdf6Quf4Fw97W5IsEPhUWfi1B+5um6LkQY0TYOYdQb8Kp/q1xM2
2dR75zWwUnJObA2cEETAWad7aIwJxXCSlZwyO4UADLnZJsfk2SOHo30qxukEI+Df
EV/70Sx0Ikz1zqUMyE+f0wRBOsS+mfWkwD8Rndzv2Hbj0mKGjNzrz9nMQ04eRGVq
Xf4684yuubAnxY8KGDycAofkB6kkVLmOY8boafFXgW5O6uxPIrh+lAnIZdLTek7E
qtBYK6iR9fztcKxQvnMIA6qJ/avOmsCfPha2ixk9vrdr5ZaZ0ZFiONBOLUsW57/Z
C6XvexelrIp1RGwhPrWjdyiPwnLbwILBrXVPjJyExHNNJGrhrMzy8Ao4ZyXG1YAe
BglosAqCDNpmx20z5ECH
=tu3J
-----END PGP SIGNATURE-----

--nextPart1894608.TEDFyppSZ4--


From MAILER-DAEMON Tue Dec 18 13:48:19 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tl2DD-0006Ep-7B
	for mharc-autoconf@gnu.org; Tue, 18 Dec 2012 13:48:19 -0500
Received: from eggs.gnu.org ([208.118.235.92]:44885)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tl2D9-0006Ca-V4
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:48:17 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tl2D8-0004yg-AG
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:48:15 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:43863)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tl2D8-0004yT-1r
	for autoconf@gnu.org; Tue, 18 Dec 2012 13:48:14 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qBIImAOQ004053; Tue, 18 Dec 2012 12:48:10 -0600 (CST)
Date: Tue, 18 Dec 2012 12:48:10 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Jeffrey Walton <noloader@gmail.com>
Subject: Re: Enabling compiler warning flags
In-Reply-To: <CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Tue, 18 Dec 2012 12:48:10 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 18:48:17 -0000

On Tue, 18 Dec 2012, Jeffrey Walton wrote:
> If you are going to try the waters with warnings, you should also
> consider the flags to integrate with platform security.
>
> Platform security integration includes fortified sources and stack
> protectors. Here are the flags of interest:
>  * -fstack-protector-all
>  * -z,noexecstack
>  * -z,noexecheap (or other measure, such as W^X)
>  * -z,relro
>  * -z,now
>  * -fPIE and -pie for executables
>
> FORTIFY_SOURCE=2 (FORTIFY_SOURCE=1 on Android 4.1+), where available.

I understand your concern and the reasoning, but these sort of options 
are highly platform/target/distribution specific.  It is easy to 
create packages which fail to build on many systems.  Later, the baked 
in settings of somewhat dated distribution tarballs may not meet 
current standards.

Surely it is better to leave this to OS distribution maintainers who 
establish common rules for OS packages and ensure that options are 
applied in a uniform and consistent manner.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Wed Dec 19 00:56:00 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlCdM-0001Tl-Di
	for mharc-autoconf@gnu.org; Wed, 19 Dec 2012 00:56:00 -0500
Received: from eggs.gnu.org ([208.118.235.92]:56511)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlCdK-0001SW-KG
	for autoconf@gnu.org; Wed, 19 Dec 2012 00:55:59 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlCdH-00012D-JM
	for autoconf@gnu.org; Wed, 19 Dec 2012 00:55:58 -0500
Received: from mail-vb0-f43.google.com ([209.85.212.43]:38944)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlCdH-000123-E2
	for autoconf@gnu.org; Wed, 19 Dec 2012 00:55:55 -0500
Received: by mail-vb0-f43.google.com with SMTP id fs19so1873611vbb.16
	for <autoconf@gnu.org>; Tue, 18 Dec 2012 21:55:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=vPU756t5msmCo3swUlK6MB+L7fe51entiA4OZYe4n5o=;
	b=K9+gG7FszevH3rZhXAhcRMU9p7fuLfnAMCygDv3/46m4ljCGC/XrDFcPH/GFXlZrWb
	AcdWPbH6QSwJHCdzcj4K3XyOwBKy3Gdg8DrVMiWtKVzWu0n7kXuZS0XanEimndVHB+ma
	EbMruRI6aLDI6t9h79RZr8pl2+LlpCwc3HO17yqpSWaEv2BqKwOqkHM9jGSlEkj5ntVc
	VTw5KBKq01p1i9fvdxhqbHd+WAjhdxyK0/1RfixlYhpRadLEDk+r4GIQTd6Sbap7BcIP
	R4DmtyqqnScBK1t3y/uI81F3RrZVtdsrzG6rvXlDGePQv89qBM3P8kDjyeBND+9ogDDH
	2nWQ==
MIME-Version: 1.0
Received: by 10.52.36.167 with SMTP id r7mr6098233vdj.108.1355896554818; Tue,
	18 Dec 2012 21:55:54 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Tue, 18 Dec 2012 21:55:54 -0800 (PST)
In-Reply-To: <alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
Date: Wed, 19 Dec 2012 00:55:54 -0500
Message-ID: <CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.43
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 05:55:59 -0000

On Tue, Dec 18, 2012 at 1:48 PM, Bob Friesenhahn
<bfriesen@simple.dallas.tx.us> wrote:
> On Tue, 18 Dec 2012, Jeffrey Walton wrote:
>>
>> If you are going to try the waters with warnings, you should also
>> consider the flags to integrate with platform security.
>>
>> Platform security integration includes fortified sources and stack
>> protectors. Here are the flags of interest:
>>  * -fstack-protector-all
>>  * -z,noexecstack
>>  * -z,noexecheap (or other measure, such as W^X)
>>  * -z,relro
>>  * -z,now
>>  * -fPIE and -pie for executables
>>
>> FORTIFY_SOURCE=2 (FORTIFY_SOURCE=1 on Android 4.1+), where available.
>
> I understand your concern and the reasoning, but these sort of options are
> highly platform/target/distribution specific.  It is easy to create packages
> which fail to build on many systems.  Later, the baked in settings of
> somewhat dated distribution tarballs may not meet current standards.
>
> Surely it is better to leave this to OS distribution maintainers who
> establish common rules for OS packages and ensure that options are applied
> in a uniform and consistent manner.
I think your arguments make a lot of sense and I would like to agree with you.

Unfortunately, the folks at Red Hat provided a "proof by counter
example" with the recent MySQL 0-days
(http://www.h-online.com/security/news/item/MariaDB-fixes-zero-day-vulnerability-in-MySQL-1761451.html).
I would have expected Red Hat security folks to be on top of it,
especially with a high risk application such as a database that
accepts input from the network (some hand waiving since PHP is likely
in front of it).

In the recent MySQL 0-days, the developers (MariaDB) and the platform
(Red Hat) both failed. Its been repeated time and time again
throughout our brief history.

Jeff


From MAILER-DAEMON Wed Dec 19 10:47:46 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlLs1-0006vw-W5
	for mharc-autoconf@gnu.org; Wed, 19 Dec 2012 10:47:46 -0500
Received: from eggs.gnu.org ([208.118.235.92]:35651)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TlLrz-0006uk-AY
	for autoconf@gnu.org; Wed, 19 Dec 2012 10:47:44 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TlLry-00057M-1o
	for autoconf@gnu.org; Wed, 19 Dec 2012 10:47:43 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:56009)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TlLrx-00057F-RV
	for autoconf@gnu.org; Wed, 19 Dec 2012 10:47:41 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id E495FA60005;
	Wed, 19 Dec 2012 07:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8RKA8k9xDqJ1; Wed, 19 Dec 2012 07:47:40 -0800 (PST)
Received: from [192.168.1.6] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 80B3EA60001;
	Wed, 19 Dec 2012 07:47:40 -0800 (PST)
Message-ID: <50D1E19C.7000004@cs.ucla.edu>
Date: Wed, 19 Dec 2012 07:47:40 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: noloader@gmail.com
Subject: Re: Enabling compiler warning flags
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
	<CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
In-Reply-To: <CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 15:47:44 -0000

On 12/18/2012 09:55 PM, Jeffrey Walton wrote:
> Unfortunately, the folks at Red Hat provided a "proof by counter
> example" with the recent MySQL 0-days

No matter what the security regime is, it will always
break down.  Always.  The question is not whether security
could be improved.  Security could always be improved.
The question is whether it's worth the effort.

Abstractly, I think Autoconf machinery to support security
checking is a good idea, but the devil is in the details.
One good way to help determine whether the proposed change
to Autoconf is worth the effort is to see whether someone
is willing to volunteer the work to make the proposed change happen,
and to donate their change to the FSF.  Are you willing
and able to do that?  If not, can you find someone who is?


From MAILER-DAEMON Wed Dec 19 13:53:25 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlOlh-0008T6-IQ
	for mharc-autoconf@gnu.org; Wed, 19 Dec 2012 13:53:25 -0500
Received: from eggs.gnu.org ([208.118.235.92]:50981)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1TlOld-0008S4-LP
	for autoconf@gnu.org; Wed, 19 Dec 2012 13:53:23 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1TlOlV-0002ge-QO
	for autoconf@gnu.org; Wed, 19 Dec 2012 13:53:21 -0500
Received: from aibo.runbox.com ([91.220.196.211]:60704)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1TlOlV-0002fB-Kk
	for autoconf@gnu.org; Wed, 19 Dec 2012 13:53:13 -0500
Received: from [10.9.9.131] (helo=fenris.runbox.com)
	by bars.runbox.com with esmtp (Exim 4.71)
	(envelope-from <dwheeler@dwheeler.com>) id 1TlOlT-0000ts-1H
	for autoconf@gnu.org; Wed, 19 Dec 2012 19:53:11 +0100
Received: from mail by fenris.runbox.com with local  (Exim 4.50)
	id 1TlOlr-0001kw-Ht
	for autoconf@gnu.org; Wed, 19 Dec 2012 19:53:35 +0100
Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received: from [129.246.254.94] by secure.runbox.com with http
	(uid:258406) (RMM 4.0); for <autoconf@gnu.org>;
	Wed, 19 Dec 2012 18:53:35 GMT
From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: autoconf@gnu.org
Subject: Re: Autoconf Digest, Vol 104, Issue 14
Date: Wed, 19 Dec 2012 13:53:35 -0500 (EST)
X-Mailer: RMM
References: <mailman.17.1355936404.9757.autoconf@gnu.org>
In-Reply-To: <mailman.17.1355936404.9757.autoconf@gnu.org>
Message-Id: <E1TlOlr-0001kw-Ht@fenris.runbox.com>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 91.220.196.211
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: dwheeler@dwheeler.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 18:53:23 -0000

Bob Friesenhahn <bfriesen@simple.dallas.tx.us>:
> It is pretty common that the person trying to eliminate a warning does=20
> not understand the code well enough to understand the consequences of=20
> their action or is interested in a quick fix.

But one reason this happens is that the original developer never saw the wa=
rning.  If warnings are *on* by default, the original developer is far more=
 likely to see and respond to them.  Nowadays, developers pull from some re=
po and use autoconf to set up a working version.  If the defaults don't tur=
n on warnings, nothing else will either.

Bob Friesenhahn <bfriesen@simple.dallas.tx.us>:
> I understand your concern and the reasoning, but these sort of options=20
> are highly platform/target/distribution specific.  It is easy to=20
> create packages which fail to build on many systems.  Later, the baked=20
> in settings of somewhat dated distribution tarballs may not meet=20
> current standards.
>=20
> Surely it is better to leave this to OS distribution maintainers who=20
> establish common rules for OS packages and ensure that options are=20
> applied in a uniform and consistent manner.

The whole *point* of autoconf is to make it easy to distribute packages tha=
t work on various systems.  We have many, many examples where the "OS distr=
ibution maintainers" don't use what's available.  Perhaps even more importa=
ntly, "Joe User" who installs software from source code will *NOT* know how=
 to enable them, unless they happen to be in the site or system-wide config=
 files.  But since these capabilities aren't baked into autoconf, they are =
unlikely to be in the system-wide config files either.


Paul Eggert:
> Abstractly, I think Autoconf machinery to support security
> checking is a good idea, but the devil is in the details.

Amen to that, of course :-).

--- David A. Wheeler


From MAILER-DAEMON Wed Dec 19 19:24:26 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlTw2-0007NQ-AA
	for mharc-autoconf@gnu.org; Wed, 19 Dec 2012 19:24:26 -0500
Received: from eggs.gnu.org ([208.118.235.92]:33596)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlTvz-0007Jx-IZ
	for autoconf@gnu.org; Wed, 19 Dec 2012 19:24:24 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlTvx-0005jP-Gr
	for autoconf@gnu.org; Wed, 19 Dec 2012 19:24:23 -0500
Received: from mail-vb0-f45.google.com ([209.85.212.45]:42333)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlTvx-0005hB-CF
	for autoconf@gnu.org; Wed, 19 Dec 2012 19:24:21 -0500
Received: by mail-vb0-f45.google.com with SMTP id p1so3061158vbi.18
	for <autoconf@gnu.org>; Wed, 19 Dec 2012 16:24:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=IvxHspqXob0ZdWsQU+hRRherftZmbxhdC6o0VpwNno8=;
	b=euhaivDdV+6zf/j9WbQc6kj3D1DzH0JUuvK0ndttyTy7nQI9DdgNyOn6bKPCxz4NDy
	Z0PRyw4cY/N4Mjr2j/kVjJwBBTgKxaw7v3rcyyiFi3YD2+odzK0iiTcVT0yjUqIFU7/w
	pXd8c+ZC6A7BBCQtp3ykPeHp+aVvMK+2d77QcR1MPDy4YGpFb6taLF63pMXJo7PidgqK
	oWxwWtgJ8CVkLnxrGqT/fKmBaamkhtkhS2pwdZ5v/JtaUWtyMJLaWIwOdHphWLeB2q8F
	GOLPAVm3/DNQ12Afry0zJXmJQ9WKiFzxtaDbgGS6+3rEbTg+pjcsnKQm/vUV5NhnoJc7
	9kSw==
MIME-Version: 1.0
Received: by 10.52.36.167 with SMTP id r7mr9999086vdj.108.1355963060480; Wed,
	19 Dec 2012 16:24:20 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Wed, 19 Dec 2012 16:24:20 -0800 (PST)
In-Reply-To: <50D1E19C.7000004@cs.ucla.edu>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
	<CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
	<50D1E19C.7000004@cs.ucla.edu>
Date: Wed, 19 Dec 2012 19:24:20 -0500
Message-ID: <CAH8yC8=ewKcWcybFb1v7x3+C66dJx=xurEDaeWaTnbGwk6xA6A@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.45
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 00:24:24 -0000

Hi Paul,

On Wed, Dec 19, 2012 at 10:47 AM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 12/18/2012 09:55 PM, Jeffrey Walton wrote:
>>
>> Unfortunately, the folks at Red Hat provided a "proof by counter
>> example" with the recent MySQL 0-days
>
>
> No matter what the security regime is, it will always
> break down.  Always.  The question is not whether security
> could be improved.  Security could always be improved.
> The question is whether it's worth the effort.
Agreed.

> Abstractly, I think Autoconf machinery to support security
> checking is a good idea, but the devil is in the details.
Agreed.

> One good way to help determine whether the proposed change
> to Autoconf is worth the effort is to see whether someone
> is willing to volunteer the work to make the proposed change happen,
> and to donate their change to the FSF.  Are you willing
> and able to do that?  If not, can you find someone who is?
Well, I work in the "secure software" field (whatever that's worth
given the collective failures of the security folks). I am willing to
try and help. I've been lurking on the list trying to learn (I don't
even use Autoconf - I still write my makefiles by hand).

I'm not sure how much help the FSF will be. Forgive my ignorance, but
are FSF and GNU equivalent? A couple of years ago when Savannah got
hacked (January, 2011), I sent an email asking for guidance for
projects on security related matters (broadly, secure coding guides,
data security and best practices, selection of cryptographic
algorithms, and the like). The email was sent to gnu@gnu.org (the
listed point of contact), and it opened with: "There's two points
below that GNU could address. The first is storing plain text
passwords. Second is the lack of security topics in 'GNU Coding
Standards'." I did not even get a reply.

For completeness, I don't think this is an Autoconf problem. But I was
hoping Autoconf (or other friends, such as Automake) could be part of
the solution. I am wit's end trying to figure out how to put a sizable
dent in the problem. I've been putting fires out with garden hoses,
and its not working.

Jeff


From MAILER-DAEMON Wed Dec 19 22:14:19 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlWaR-000215-TX
	for mharc-autoconf@gnu.org; Wed, 19 Dec 2012 22:14:19 -0500
Received: from eggs.gnu.org ([208.118.235.92]:55878)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TlWaQ-000207-AA
	for autoconf@gnu.org; Wed, 19 Dec 2012 22:14:19 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TlWaP-0006Ue-90
	for autoconf@gnu.org; Wed, 19 Dec 2012 22:14:18 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:60049)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1TlWaP-0006U9-3X
	for autoconf@gnu.org; Wed, 19 Dec 2012 22:14:17 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 5254AA60001;
	Wed, 19 Dec 2012 19:14:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KnrqHEloIVr6; Wed, 19 Dec 2012 19:14:08 -0800 (PST)
Received: from [192.168.1.6] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 90C1439E8118;
	Wed, 19 Dec 2012 19:14:08 -0800 (PST)
Message-ID: <50D28280.9030504@cs.ucla.edu>
Date: Wed, 19 Dec 2012 19:14:08 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: noloader@gmail.com
Subject: Re: Enabling compiler warning flags
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
	<CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
	<50D1E19C.7000004@cs.ucla.edu>
	<CAH8yC8=ewKcWcybFb1v7x3+C66dJx=xurEDaeWaTnbGwk6xA6A@mail.gmail.com>
In-Reply-To: <CAH8yC8=ewKcWcybFb1v7x3+C66dJx=xurEDaeWaTnbGwk6xA6A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 03:14:19 -0000

On 12/19/2012 04:24 PM, Jeffrey Walton wrote:
> I'm not sure how much help the FSF will be.

The GNU project can be of some help, sure.

> Forgive my ignorance, but
> are FSF and GNU equivalent?

Not exactly.  The FSF sponsors the GNU project, but it also
does other things.  The GNU project is its biggest project,
though.  See <http://www.fsf.org/about/>.

> The email was sent tognu@gnu.org

Sorry, I'm not on that mailing list and didn't see it.
Please see <http://www.gnu.org/software/security/>
for how to report security issues that need to be escalated.

> I was hoping Autoconf (or other friends, such as Automake) could be part of
> the solution.

Yes, I think this is a reasonable idea for improving the
robustness of GNU and GNU-using software.



From MAILER-DAEMON Wed Dec 19 22:26:58 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlWmg-0003cg-UR
	for mharc-autoconf@gnu.org; Wed, 19 Dec 2012 22:26:58 -0500
Received: from eggs.gnu.org ([208.118.235.92]:57048)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TlWmd-0003bC-36
	for autoconf@gnu.org; Wed, 19 Dec 2012 22:26:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TlWmb-0001NY-Kc
	for autoconf@gnu.org; Wed, 19 Dec 2012 22:26:55 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:49170)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TlWmb-0001M9-9s
	for autoconf@gnu.org; Wed, 19 Dec 2012 22:26:53 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qBK3QggA017678; Wed, 19 Dec 2012 21:26:42 -0600 (CST)
Date: Wed, 19 Dec 2012 21:26:42 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Jeffrey Walton <noloader@gmail.com>
Subject: Re: Enabling compiler warning flags
In-Reply-To: <CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1212192118190.19664@freddy.simplesystems.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
	<CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Wed, 19 Dec 2012 21:26:43 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 03:26:57 -0000

On Wed, 19 Dec 2012, Jeffrey Walton wrote:
>>
>> Surely it is better to leave this to OS distribution maintainers who
>> establish common rules for OS packages and ensure that options are applied
>> in a uniform and consistent manner.
> I think your arguments make a lot of sense and I would like to agree with you.
>
> Unfortunately, the folks at Red Hat provided a "proof by counter
> example" with the recent MySQL 0-days
> (http://www.h-online.com/security/news/item/MariaDB-fixes-zero-day-vulnerability-in-MySQL-1761451.html).
> I would have expected Red Hat security folks to be on top of it,
> especially with a high risk application such as a database that
> accepts input from the network (some hand waiving since PHP is likely
> in front of it).

I don't know anything about this vulnerability but your conclusion 
does not quite make sense.  Software is evaluated for vulnerability at 
the source code level without consideration for the fortifications 
which were suggested.

I am suggesting that OS distributions know how to best fortify their 
systems and that fortification methods may vary with each OS release. 
This does not mean that application bugs should not be corrected.

Most of the the -z,blahblah options could be eliminated if the OS and 
toolchain were to arrange to do useful security things by default. 
They could do useful security things by default and flags could 
disable safeguards for rare code which needs to intentionally do the 
things guarded against.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Wed Dec 19 23:15:21 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlXXV-0003PF-0r
	for mharc-autoconf@gnu.org; Wed, 19 Dec 2012 23:15:21 -0500
Received: from eggs.gnu.org ([208.118.235.92]:34065)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1TlXXS-0003P9-OF
	for autoconf@gnu.org; Wed, 19 Dec 2012 23:15:19 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1TlXXR-0005b5-Da
	for autoconf@gnu.org; Wed, 19 Dec 2012 23:15:18 -0500
Received: from smtp1.stanford.edu ([171.67.219.81]:39276
	helo=smtp.stanford.edu) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1TlXXR-0005ab-8A
	for autoconf@gnu.org; Wed, 19 Dec 2012 23:15:17 -0500
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with SMTP id B3B0414080F
	for <autoconf@gnu.org>; Wed, 19 Dec 2012 20:15:15 -0800 (PST)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.stanford.edu (Postfix) with ESMTPS id 74E6B1407F9
	for <autoconf@gnu.org>; Wed, 19 Dec 2012 20:15:15 -0800 (PST)
Received: by windlord.stanford.edu (Postfix, from userid 1000)
	id 5AF782F5F3; Wed, 19 Dec 2012 20:15:14 -0800 (PST)
From: Russ Allbery <rra@stanford.edu>
To: autoconf@gnu.org
Subject: Re: Enabling compiler warning flags
In-Reply-To: <alpine.GSO.2.01.1212192118190.19664@freddy.simplesystems.org>
	(Bob Friesenhahn's message of "Wed, 19 Dec 2012 21:26:42 -0600 (CST)")
Organization: The Eyrie
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8n6_WF-PgKg_=_gYuQq_agoK3TDruHH=8huh+UJVk9vnA@mail.gmail.com>
	<alpine.GSO.2.01.1212181244030.28949@freddy.simplesystems.org>
	<CAH8yC8=b07rdvxp+oK5mXO2kZocjpTcc-OyYG9wZNttK7rTLxA@mail.gmail.com>
	<alpine.GSO.2.01.1212192118190.19664@freddy.simplesystems.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Wed, 19 Dec 2012 20:15:14 -0800
Message-ID: <87hanhz7e5.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 171.67.219.81
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 04:15:20 -0000

Bob Friesenhahn <bfriesen@simple.dallas.tx.us> writes:

> Most of the the -z,blahblah options could be eliminated if the OS and
> toolchain were to arrange to do useful security things by default. They
> could do useful security things by default and flags could disable
> safeguards for rare code which needs to intentionally do the things
> guarded against.

Ubuntu patches gcc to enable a bunch of these options.  Debian discussed
doing the same and decided not to, since Debian really dislikes diverging
from upstream on things that have that much public-facing visibility, and
instead built it into our packaging system.

I think having the toolchain do some of this automatically has been a hard
sell for understandable backwards-compatibility concerns, but that would
certainly be something that could be explored across multiple GNU
projects.  Although one of the problems with making toolchain changes is
that the needs of embedded systems, who are heavy toolchain users, are
often quite different.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>


From MAILER-DAEMON Thu Dec 20 14:46:19 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tlm4R-0006ye-4z
	for mharc-autoconf@gnu.org; Thu, 20 Dec 2012 14:46:19 -0500
Received: from eggs.gnu.org ([208.118.235.92]:47423)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tlm4J-0006ww-8T
	for autoconf@gnu.org; Thu, 20 Dec 2012 14:46:17 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tlm4G-00028P-Qg
	for autoconf@gnu.org; Thu, 20 Dec 2012 14:46:11 -0500
Received: from mail-vb0-f49.google.com ([209.85.212.49]:32869)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1Tlm4G-00028K-Lh
	for autoconf@gnu.org; Thu, 20 Dec 2012 14:46:08 -0500
Received: by mail-vb0-f49.google.com with SMTP id r6so4188848vbi.22
	for <autoconf@gnu.org>; Thu, 20 Dec 2012 11:46:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type:content-transfer-encoding;
	bh=SWcfW2noWhzSjomzDY6zligyFqXoY5ETBZ9SFhq2TPo=;
	b=VP0+onoO6qDFUjvJfpH3N+eaVe0fCFXvv8haV3dNfkq4WeKVadfYQ8RdIuGQsUe95u
	kG1E8d/8FHqj8BGthpZHOhw6m2uslY6Rjuy5md3ggcTJ9dQ2SqmENPs9OLVzCtBVX89J
	xs0JdqK1IBcl+SC8qI81yLgkCo2Q5MThvpKoPosIQesKZAagbucuR/SxWk52X9kW3jac
	YqJXzWJm8FXJ92MC6tGB4wMNJNdceNkKBWWf5WIIydxGy9sdxq1bHayvwHkeGa9zcRHa
	7g7ycNTFT/8jWNgiCHSHQKQKh1kAwnpG4HSkG4+b7Oz4r7mb6Acli61hwdR/INJwdEZv
	qNHg==
MIME-Version: 1.0
Received: by 10.52.36.167 with SMTP id r7mr13968308vdj.108.1356032768015; Thu,
	20 Dec 2012 11:46:08 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Thu, 20 Dec 2012 11:46:07 -0800 (PST)
In-Reply-To: <E1Tkpiw-0005D8-5E@fenris.runbox.com>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
Date: Thu, 20 Dec 2012 14:46:07 -0500
Message-ID: <CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: dwheeler@dwheeler.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.212.49
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 19:46:18 -0000

On Tue, Dec 18, 2012 at 12:28 AM, David A. Wheeler
<dwheeler@dwheeler.com> wrote:
> Jim Meyering said:
>> Did you realize that several GNU projects now enable virtually
>> every gcc warning that is available (even including those that
>> are new in the upcoming gcc-4.8, for folks that use bleeding edge gcc)
>> via gnulib's manywarnings.m4 configure-time tests?
>>
>> Of course, there is a list of warnings that we do disable,
>> due to their typical lack of utility and the invasiveness
>> of changes required do suppress them.
>
> Is there any way that the autoconf (or automake) folks could make compile=
r warnings much, much easier to enable?  Preferably enabled by default when=
 you start packaging something? For example, could gnulib warnings and many=
warnings be distributed and enabled as *part* of autoconf? If not, could au=
toconf at least strongly advertize the existence of these, and include spec=
ific instructions to people on how to quickly install it? The autoconf sect=
ion on "gnulib" never even *MENTIONS* the "warnings" and "manywarnings" stu=
ff!  And while automake has warnings, they are for the automake configurati=
on file... not for compilation.
>
> Compiler warning flags cost nearly nothing to turn on when you're *starti=
ng* a project, but they're harder to enable later (a thousand warnings abou=
t the same thing later is harder than fixing it the first time). And while =
some warnings are nonsense, their use can make the resulting software much,=
 much better. If we got people to turn on warning flags all over the place,=
 during development, a lot of bugs would simply disappear.
>
To further muddy the water, there are also preprocessor macros that
affect security!

Debug configurations can/should have _DEBUG and DEBUG preprocessor
macros; while Release configurations should/must have _NDEBUG and
NDEBUG preprocessor macros. Posix only observes NDEBUG
(http://pubs.opengroup.org/onlinepubs/009604499/basedefs/assert.h.html).
The additional Debug and Release preprocessor macros help ensure the
'proper' or 'more complete' uptake of third party libraries (such as
SQLite and SQLCipher).

Other libraries also add additional macro dependencies. For example
Objective C Release configurations also need NS_BLOCK_ASSERTIONS=3D1
defined.

If a project does not observe proper preprocessor macros for a
configuration, a project could fall victim to runtime assertions and
actually DoS itself after the assert calls abort(). The ISC's DNS
server comes to mind (confer: there are CVE's assigned for the errant
behavior, and its happened more than once!
http://www.google.com/#q=3Disc+dns+assert+dos).

So there you have it: all the elements of a secure toolchain. It
includes the preprocessor (macros), the compiler (warnings), and
linker (platform security integration). Many people don't realize all
the details that go into getting a project set up correctly, long
before the first line of code is ever written. And it applies to
Makefiles, Eclipse, Net Beans, Xcode, Visual Studio, et al. Its not
just limited to one tool or one platform.

Jeff


From MAILER-DAEMON Thu Dec 20 15:24:20 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlmfE-0001dW-Oh
	for mharc-autoconf@gnu.org; Thu, 20 Dec 2012 15:24:20 -0500
Received: from eggs.gnu.org ([208.118.235.92]:54585)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TlmfA-0001cT-33
	for autoconf@gnu.org; Thu, 20 Dec 2012 15:24:19 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tlmf4-00049w-5g
	for autoconf@gnu.org; Thu, 20 Dec 2012 15:24:15 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:51602)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1Tlmf3-00049a-Up
	for autoconf@gnu.org; Thu, 20 Dec 2012 15:24:10 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qBKKO6CX025797; Thu, 20 Dec 2012 14:24:06 -0600 (CST)
Date: Thu, 20 Dec 2012 14:24:05 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Jeffrey Walton <noloader@gmail.com>
Subject: Re: Enabling compiler warning flags
In-Reply-To: <CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1212201419450.2948@freddy.simplesystems.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Thu, 20 Dec 2012 14:24:07 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 20:24:19 -0000

On Thu, 20 Dec 2012, Jeffrey Walton wrote:
>
> If a project does not observe proper preprocessor macros for a
> configuration, a project could fall victim to runtime assertions and
> actually DoS itself after the assert calls abort(). The ISC's DNS

The "falling victim to runtime assertions" is the same as falling 
victim to a bug.  It is not necessarily true that removing the 
assertion is better than suffering from the unhandled bug.  Once again 
this is a program/situation-specific issue.

You keep repeating standard recipies which are not proper/best for all 
software.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Thu Dec 20 15:49:18 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tln3O-0007C7-90
	for mharc-autoconf@gnu.org; Thu, 20 Dec 2012 15:49:18 -0500
Received: from eggs.gnu.org ([208.118.235.92]:58026)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1Tln3E-00079F-Hy
	for autoconf@gnu.org; Thu, 20 Dec 2012 15:49:16 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1Tln39-0002NA-N9
	for autoconf@gnu.org; Thu, 20 Dec 2012 15:49:08 -0500
Received: from smtp1.stanford.edu ([171.67.219.81]:43348
	helo=smtp.stanford.edu) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rra@stanford.edu>) id 1Tln39-0002N0-HV
	for autoconf@gnu.org; Thu, 20 Dec 2012 15:49:03 -0500
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with SMTP id A01F2140F55
	for <autoconf@gnu.org>; Thu, 20 Dec 2012 12:49:02 -0800 (PST)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.stanford.edu (Postfix) with ESMTPS id 5F5B7140F54
	for <autoconf@gnu.org>; Thu, 20 Dec 2012 12:49:02 -0800 (PST)
Received: by windlord.stanford.edu (Postfix, from userid 1000)
	id 4BCE92F5C6; Thu, 20 Dec 2012 12:49:01 -0800 (PST)
From: Russ Allbery <rra@stanford.edu>
To: autoconf@gnu.org
Subject: Re: Enabling compiler warning flags
In-Reply-To: <CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
	(Jeffrey Walton's message of "Thu, 20 Dec 2012 14:46:07 -0500")
Organization: The Eyrie
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Thu, 20 Dec 2012 12:49:01 -0800
Message-ID: <87ip7we9fm.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 171.67.219.81
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 20:49:16 -0000

Jeffrey Walton <noloader@gmail.com> writes:

> If a project does not observe proper preprocessor macros for a
> configuration, a project could fall victim to runtime assertions and
> actually DoS itself after the assert calls abort(). The ISC's DNS server
> comes to mind (confer: there are CVE's assigned for the errant behavior,
> and its happened more than once!
> http://www.google.com/#q=isc+dns+assert+dos).

It's very rare for it to be sane to continue after an assert().  That
would normally mean a serious coding error on the part of the person who
wrote the assert().  The whole point of assert() is to establish
invariants which, if violated, would result in undefined behavior.
Continuing after an assert() could well lead to an even worse security
problem, such as a remote system compromise.

The purpose of the -DNDEBUG compile-time option is not to achieve
additional security by preventing a DoS, but rather to gain additional
*performance* by removing all the checks done via assert().  If your goal
is to favor security over performance, you never want to use -DNDEBUG.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>


From MAILER-DAEMON Thu Dec 20 16:32:38 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlnjK-0007Fj-0q
	for mharc-autoconf@gnu.org; Thu, 20 Dec 2012 16:32:38 -0500
Received: from eggs.gnu.org ([208.118.235.92]:37450)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlnjF-0007DT-5Z
	for autoconf@gnu.org; Thu, 20 Dec 2012 16:32:36 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlnjD-0006Q9-C3
	for autoconf@gnu.org; Thu, 20 Dec 2012 16:32:33 -0500
Received: from mail-vc0-f174.google.com ([209.85.220.174]:57761)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlnjD-0006Q0-3n
	for autoconf@gnu.org; Thu, 20 Dec 2012 16:32:31 -0500
Received: by mail-vc0-f174.google.com with SMTP id d16so4278570vcd.19
	for <autoconf@gnu.org>; Thu, 20 Dec 2012 13:32:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=bl/H+3J1QQbJFeRtVHB1QtucRMC4CKveY0ttskTEWFs=;
	b=pzj0m96THYZVQK3d/NfIzBpm/v4/uSvt1+w9IhB9fNB178sn7ydB5WTKcO2fEsFTC9
	WJMfLJKfsVyvuDd/0I7CCsA9DEeA+llrtCTxnpWJyLVLWA7r+Obj9l0fFeTX/RKGA5eG
	s2pGj2ifpt4SRPHek30/PK5xoRHmjzwC8Fq8LGs9/82m2BcAss6Oi3Y8c+ChYurtTzJo
	dUTrA3iBjv1SFRVsg3hlwp29D3v1nLdDeP/6pudwcCx8gs+Ftl1brNAfGNZJi2wSMv1w
	WJ1CvangChUGK4W0cSELw7QE5Ou3QzL3jT8+5wCmXd8FZpREFv0v9JP3r7ohMxKfdEEk
	HfjA==
MIME-Version: 1.0
Received: by 10.220.238.139 with SMTP id ks11mr16293642vcb.49.1356039150513;
	Thu, 20 Dec 2012 13:32:30 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Thu, 20 Dec 2012 13:32:30 -0800 (PST)
In-Reply-To: <alpine.GSO.2.01.1212201419450.2948@freddy.simplesystems.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
	<alpine.GSO.2.01.1212201419450.2948@freddy.simplesystems.org>
Date: Thu, 20 Dec 2012 16:32:30 -0500
Message-ID: <CAH8yC8nsEu7m9gQ8FHg6bbENwoGV0D8HU-_KbRaDRj+87hJU=Q@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.220.174
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 21:32:36 -0000

Hi Bob,

On Thu, Dec 20, 2012 at 3:24 PM, Bob Friesenhahn
<bfriesen@simple.dallas.tx.us> wrote:
> On Thu, 20 Dec 2012, Jeffrey Walton wrote:
>>
>> If a project does not observe proper preprocessor macros for a
>> configuration, a project could fall victim to runtime assertions and
>> actually DoS itself after the assert calls abort(). The ISC's DNS
>
> The "falling victim to runtime assertions" is the same as falling victim to
> a bug.  It is not necessarily true that removing the assertion is better
> than suffering from the unhandled bug.  Once again this is a
> program/situation-specific issue.
Well, I can't think of a situation where an abort or crash is
preferred over gracefully handling a failure that could be handled
with an exit. In this case, the program is already in a code path -
why not just fail the function rather than abort? But then again, I
don't think like many others (as you can probably tell). So I could be
missing something.

In the case of a bug with known security implications (a detectable
stack smash, for example), include a "last line" defense that ensures
the program does not proceed (such as an OS initiated termination).
There is a subtle difference: in one case the program is calling
abort(); while in the other the OS is calling abort().

> You keep repeating standard recipies which are not proper/best for all
> software.
I understand its not "one size fits all," but I'm not proposing
anything evolutionary either.

All I ask is that a program properly handle its use cases (including
negative cases). The program should exhibit well defined behavior (its
an attribute or emergent property of being correct). Part of
exhibiting well defined behavior is having an understanding of your
tools due to things like Debug/Release and NDEBUG.

Folks *have* to be responsible for their programs. They can't keep
passing the buck and hope someone else will take care of it. The
operating system or Distribution Maintainers should not have to do
these things for developers.

Jeff


From MAILER-DAEMON Thu Dec 20 16:32:43 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlnjP-0007Or-5F
	for mharc-autoconf@gnu.org; Thu, 20 Dec 2012 16:32:43 -0500
Received: from eggs.gnu.org ([208.118.235.92]:37480)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlnjK-0007GA-AE
	for autoconf@gnu.org; Thu, 20 Dec 2012 16:32:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlnjG-0006Qr-SB
	for autoconf@gnu.org; Thu, 20 Dec 2012 16:32:37 -0500
Received: from mail-vc0-f182.google.com ([209.85.220.182]:64172)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <noloader@gmail.com>) id 1TlnjG-0006Qn-NA
	for autoconf@gnu.org; Thu, 20 Dec 2012 16:32:34 -0500
Received: by mail-vc0-f182.google.com with SMTP id fy27so4348549vcb.41
	for <autoconf@gnu.org>; Thu, 20 Dec 2012 13:32:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	bh=l5nsUoh557ZkkvwB7QnIM2of5vA/UyNO+OKbS9PSh/I=;
	b=FAZ+Wl6fBhTchpGCqA+sVN7lW8Vo+KtKdBTcxqeOzFsMfpZW0YpqjIRJBfCfBTeXiK
	Ax2rEksNpHaGgQE93E4VIiYfO9pyiMGWO85rPbgXvu9XiYEJlf6Y18HI8PyaI3MjLcbu
	k47PNHmjjb0gdKWEmqYlF1R+G5mtTXk+Bxt6oaGlU7JxCDORAr1Q+nRy31G1cj3F4YnQ
	o+fmpICZp6oAwGeTwNTYUtaJtbfuhzPKbcZavXohAMqWuRTUYQi8gUDIexIARYSRItol
	2XeMQYdcIDkchdLBOSMewlm1soWhyHBMrPNi3ysKr66tuID47U8J53EUHmlSRBE8Kvjp
	UKXA==
MIME-Version: 1.0
Received: by 10.58.107.235 with SMTP id hf11mr17323464veb.16.1356039154230;
	Thu, 20 Dec 2012 13:32:34 -0800 (PST)
Received: by 10.220.230.71 with HTTP; Thu, 20 Dec 2012 13:32:34 -0800 (PST)
In-Reply-To: <87ip7we9fm.fsf@windlord.stanford.edu>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
	<87ip7we9fm.fsf@windlord.stanford.edu>
Date: Thu, 20 Dec 2012 16:32:34 -0500
Message-ID: <CAH8yC8nN6JeJzzeZWHhwRSb1D6VtV4TjtunZgt3yqcfJtzpwsw@mail.gmail.com>
Subject: Re: Enabling compiler warning flags
From: Jeffrey Walton <noloader@gmail.com>
To: Russ Allbery <rra@stanford.edu>
Content-Type: text/plain; charset=UTF-8
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy]
X-Received-From: 209.85.220.182
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 21:32:42 -0000

Hi Russ,

On Thu, Dec 20, 2012 at 3:49 PM, Russ Allbery <rra@stanford.edu> wrote:
> Jeffrey Walton <noloader@gmail.com> writes:
>
>> If a project does not observe proper preprocessor macros for a
>> configuration, a project could fall victim to runtime assertions and
>> actually DoS itself after the assert calls abort(). The ISC's DNS server
>> comes to mind (confer: there are CVE's assigned for the errant behavior,
>> and its happened more than once!
>> http://www.google.com/#q=isc+dns+assert+dos).
>
> It's very rare for it to be sane to continue after an assert().  That
> would normally mean a serious coding error on the part of the person who
> wrote the assert().  The whole point of assert() is to establish
> invariants which, if violated, would result in undefined behavior.
> Continuing after an assert() could well lead to an even worse security
> problem, such as a remote system compromise.
So, I somewhat disagree with you here. I think the differences are
philosophical because I could never find guidance from standard bodies
(such as Posix or IEEE) on rationales or goals behind NDEBUG and the
intention of the abort() behind an assert().

First, an observation: if all the use cases are accounted (positive
and negative), code *lacking* NDEBUG will never fire an asserts. The
default case of 'fail' is enough to ensure this. You would be
surprised (or maybe not) how many functions don't have the default
'fail' case. Any code that lacks NDEBUG because it depends upon
assert() the abort() is defective by design. That includes the ISC's
DNS server and their assertion/abort scheme (critical infrastructure,
no less).

Under no circumstance is a program allowed to abort(). It processes as
expected or it fails gracefully. If it fails gracefully, it can exit()
if it likes. But it does not crash, and it does not abort().

Here's the philosophical difference (that will surely draw criticism):
asserts are a debug/diagnostic tool to aide in development. They have
no place in release code. I'll take it a step further: Posix asserts
are useless during development under a debugger because the eventually
lead to SIGTERM. A much better approach in practice is to SIGTRAP.

Code under my purview must (1) validate all parameters and (2) check
all return values. Not only must there be logic to fail the function
if anything goes wrong, *everything* must be asserted to alert of the
point of first failure. In this respect, asserts create self-debugging
code.

I found developers did not like assert in debug configurations. They
did not like asserts because of SIGTERM, which meant the developers
did not fully assert. That caused the code to be non-compliant. The
root cause was they did not like eating the dogfood of their own bugs.
So I had to rewrite the asserts to use SIGTRAP, which made them very
happy (they could make a mental note and continue on debugging). Code
improved dramatically after that - we were always aware of the first
point of failure, with out the need for breakpoints and detailed
inspection unless needed.

> The purpose of the -DNDEBUG compile-time option is not to achieve
> additional security by preventing a DoS, but rather to gain additional
> *performance* by removing all the checks done via assert().  If your goal
> is to favor security over performance, you never want to use -DNDEBUG.
Probably another philosophical difference: (1) code must be correct.
(2) code should be secure. (3) code can be efficient. NDEBUG just
removes the debugging/diagnostic aides, so it does help with (3). (1)
is achieved because there is a separate if/then/else that handles the
proper failure of a function in a release configuration.

I know many will disagree, but I will put my money where my mouth is:
I have code in the field (secure containers and secure channels) that
has never taken a bug report or taken less than a handful (fewer than
3). They were developed with the discipline described above, and they
include a complete suite of negative, multi-threaded self tests that
ensure graceful failures. I don't care too much about the positive
test cases since I can hire a kid from a third world country for $10
or $15 US a day to copy/paste code that works under the 'good' cases.

Can anyone else say claim have a non-trivial code base that does not
suffer defects (with a reasonable but broad definition of defect)?

Anyway, sorry about the philosophicals. I know it does not lend much
to the thread.

Jeff


From MAILER-DAEMON Thu Dec 20 18:13:26 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TlpIs-0003s0-1g
	for mharc-autoconf@gnu.org; Thu, 20 Dec 2012 18:13:26 -0500
Received: from eggs.gnu.org ([208.118.235.92]:50706)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TlpIp-0003r7-6Y
	for autoconf@gnu.org; Thu, 20 Dec 2012 18:13:24 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TlpIn-0006Zo-3v
	for autoconf@gnu.org; Thu, 20 Dec 2012 18:13:23 -0500
Received: from blade.simplesystems.org ([65.66.246.74]:51926)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bfriesen@simple.dallas.tx.us>) id 1TlpIm-0006Zh-RJ
	for autoconf@gnu.org; Thu, 20 Dec 2012 18:13:21 -0500
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	qBKNDGlQ026377; Thu, 20 Dec 2012 17:13:16 -0600 (CST)
Date: Thu, 20 Dec 2012 17:13:16 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Jeffrey Walton <noloader@gmail.com>
Subject: Re: Enabling compiler warning flags
In-Reply-To: <CAH8yC8nsEu7m9gQ8FHg6bbENwoGV0D8HU-_KbRaDRj+87hJU=Q@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1212201707030.2948@freddy.simplesystems.org>
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
	<alpine.GSO.2.01.1212201419450.2948@freddy.simplesystems.org>
	<CAH8yC8nsEu7m9gQ8FHg6bbENwoGV0D8HU-_KbRaDRj+87hJU=Q@mail.gmail.com>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Thu, 20 Dec 2012 17:13:16 -0600 (CST)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
X-Received-From: 65.66.246.74
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 23:13:24 -0000

On Thu, 20 Dec 2012, Jeffrey Walton wrote:
>>
>> The "falling victim to runtime assertions" is the same as falling victim to
>> a bug.  It is not necessarily true that removing the assertion is better
>> than suffering from the unhandled bug.  Once again this is a
>> program/situation-specific issue.
> Well, I can't think of a situation where an abort or crash is
> preferred over gracefully handling a failure that could be handled
> with an exit. In this case, the program is already in a code path -
> why not just fail the function rather than abort? But then again, I
> don't think like many others (as you can probably tell). So I could be
> missing something.

Assertions are intended for detecting unexpected conditions. 
External inputs to the program do not count as 'unexpected condition' 
and so one should never write an assertion for external inputs.  When 
an unexpected condition occurs, the best thing to do is to dump core 
so that it is possible to figure out how the impossible happend.

I agree with Russ Allbery that the primary reason to disable 
assertions is to avoid the performance penalty.  In properly-written 
code (such as your own) these assertions should not be firing anyway.

In my own performance-tuned software which uses many assert 
statements, I find the performance benefit from removing assertions to 
be virtually unmeasurable.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From MAILER-DAEMON Thu Dec 20 18:49:43 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tlprz-0004Md-2D
	for mharc-autoconf@gnu.org; Thu, 20 Dec 2012 18:49:43 -0500
Received: from eggs.gnu.org ([208.118.235.92]:58415)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tlpru-0004MR-Ov
	for autoconf@gnu.org; Thu, 20 Dec 2012 18:49:41 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tlprl-0007qs-Fa
	for autoconf@gnu.org; Thu, 20 Dec 2012 18:49:38 -0500
Received: from smtp.cs.ucla.edu ([131.179.128.62]:52644)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eggert@cs.ucla.edu>) id 1Tlprl-0007qY-AX
	for autoconf@gnu.org; Thu, 20 Dec 2012 18:49:29 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp.cs.ucla.edu (Postfix) with ESMTP id 9357839E810A;
	Thu, 20 Dec 2012 15:49:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1])
	by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j01o10jfJSeZ; Thu, 20 Dec 2012 15:49:27 -0800 (PST)
Received: from [192.168.1.6] (pool-71-189-154-249.lsanca.fios.verizon.net
	[71.189.154.249])
	by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 2750F39E8108;
	Thu, 20 Dec 2012 15:49:27 -0800 (PST)
Message-ID: <50D3A407.4080609@cs.ucla.edu>
Date: Thu, 20 Dec 2012 15:49:27 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
Organization: UCLA Computer Science Department
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: noloader@gmail.com
Subject: Re: Enabling compiler warning flags
References: <mailman.25.1355763603.26155.autoconf@gnu.org>
	<E1Tkpiw-0005D8-5E@fenris.runbox.com>
	<CAH8yC8nTvpSSY3n37HR7R4frpUq65s15sE6fJXc2Y1LZxvqxjw@mail.gmail.com>
	<87ip7we9fm.fsf@windlord.stanford.edu>
	<CAH8yC8nN6JeJzzeZWHhwRSb1D6VtV4TjtunZgt3yqcfJtzpwsw@mail.gmail.com>
In-Reply-To: <CAH8yC8nN6JeJzzeZWHhwRSb1D6VtV4TjtunZgt3yqcfJtzpwsw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 131.179.128.62
Cc: autoconf@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 23:49:41 -0000

On 12/20/2012 01:32 PM, Jeffrey Walton wrote:
> Posix asserts
> are useless during development under a debugger because the eventually
> lead to SIGTERM. A much better approach in practice is to SIGTRAP.

I didn't follow all that message, but this part doesn't appear
to be correct.  In POSIX, when assert() fails it leads to SIGABRT.

More generally, I'd rather focus this mailing list's energy into
improving Autoconf rather than worrying too much about
philosophical considerations.


From MAILER-DAEMON Sat Dec 22 10:19:06 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TmQqw-0000R1-Rk
	for mharc-autoconf@gnu.org; Sat, 22 Dec 2012 10:19:06 -0500
Received: from eggs.gnu.org ([208.118.235.92]:38861)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TmQqn-0000QG-Pv
	for autoconf@gnu.org; Sat, 22 Dec 2012 10:19:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TmQqh-0003WE-UK
	for autoconf@gnu.org; Sat, 22 Dec 2012 10:18:57 -0500
Received: from mx1.redhat.com ([209.132.183.28]:35428)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>)
	id 1TmQqT-0003Ta-Hd; Sat, 22 Dec 2012 10:18:37 -0500
Received: from int-mx10.intmail.prod.int.phx2.redhat.com
	(int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qBMFIaJS010029
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Sat, 22 Dec 2012 10:18:36 -0500
Received: from [10.3.234.210] (vpn-234-210.phx2.redhat.com [10.3.234.210])
	by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP
	id qBMFIaSf015531; Sat, 22 Dec 2012 10:18:36 -0500
Message-ID: <50D5CF4B.1080807@redhat.com>
Date: Sat, 22 Dec 2012 08:18:35 -0700
From: Eric Blake <eblake@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Jef Driesen <jefdriesen@hotmail.com>
Subject: Re: Conditional AC_DEFINE with m4_define variable?
References: <kb4hfk$3j3$1@ger.gmane.org>
In-Reply-To: <kb4hfk$3j3$1@ger.gmane.org>
X-Enigmail-Version: 1.4.6
OpenPGP: url=http://people.redhat.com/eblake/eblake.gpg
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature";
	boundary="------------enig4DF1351CE4ED8C9A252907E8"
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 209.132.183.28
Cc: "autoconf@gnu.org" <autoconf@gnu.org>, automake@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Dec 2012 15:19:05 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4DF1351CE4ED8C9A252907E8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

[adding autoconf, as this question technically is independent of automake=
]

On 12/22/2012 07:52 AM, Jef Driesen wrote:
> Hi,
>=20
> When I set a variable with:
>=20
> m4_define([dc_version_suffix],[devel])
>=20
> or leave it empty:
>=20
> m4_define([dc_version_suffix],[])
>=20
> And then try to conditionally call AC_DEFINE based on whether the
> dc_version_suffix is set or not, this doesn't work:
>=20
> AS_IF([test "x$dc_version_suffix" =3D "xdevel"], [
>    AC_DEFINE(ENABLE_PTY, [1], [Enable pseudo terminal support.])
> ])

This will expand to either:

test "x$" =3D "xdevel"

or

test "x$devel" =3D "xdevel"

based on the macro value.  Probably not what you wanted.

>=20
> However if I use m4_isset, then it does kind of work, except that the
> USE_REVISION macro in the config.h is either defined, or not present at=

> all.
>=20
> m4_ifset([dc_version_suffix],[
>    AC_DEFINE(USE_REVISION, [1], [Use the revision number.])
> ])

Indeed, this actually does what _I_ would want - since dc_version_suffix
is known at m4 time, we might as well use that information to generate
the smallest possible configure.

But if you _insist_ on delaying the decision until shell time, even
though the condition being tested is known at m4 time, then you probably
want to use something like this:

AS_IF([test "x]dc_version_suffix[" =3D "xdevel"], [
  AC_DEFINE([USE_REVISION], [1], [Use the revision number.])
])

which expands the literal contents of the macro in place, so that your
configure will then either contain:

test "x" =3D "xdevel"

or

test "xdevel" =3D "xdevel"

Or, if you _want_ a shell variable rather than an m4 variable as the
source of your decision, then be sure you set up that shell variable:

[dc_version_suffix]=3Ddc_version_suffix
AS_IF([[test "x$dc_version_suffix" =3D "xdevel"]], [
  AC_DEFINE([USE_REVISION], [1], [Use the revision number.])
])

where the extra quoting is necessary to ensure that your configure file
will look like either:

dc_version_suffix=3D
test "x$dc_version_suffix" =3D "xdevel"

or

dc_version_suffix=3Ddevel
test "x$dc_version_suffix" =3D "xdevel"

Using a different shell variable name than the m4 macro name will make
it easier to type, without quite so much quoting:

version_suffix=3Ddc_version_suffix
AS_IF([test "x$version_suffix" =3D "xdevel"], [
  AC_DEFINE([USE_REVISION], [1], [Use the revision number.])
])

>=20
> Does anyone know how to implement this correctly?

It really depends on what you are trying to accomplish by deciding
something at m4 time, but deferring the action on that decision until
configure time.

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--------------enig4DF1351CE4ED8C9A252907E8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBCAAGBQJQ1c9LAAoJEKeha0olJ0Nqa+oIAKI3Jdrsbk3uDRyNAFvh6KHA
tg6lT0tR0vjsNVwjSoYxfLRlHP35vfB+fgROccINWg6Vef3dXZ/Pu/aOMpf3+fql
JEGtCP/mh3/PFAvoOM0nFB0oS+Lgnc50yoavS9CON0PJHzTKgvKfoR0etqr0arEl
PrsxX26KPJ8ZH1kl1IXSG7t9kExekyss730Bfh8ie2bzXluThoV3ftEjRaetrcOy
5NiaiV6/6baUgPDOqaQ4myymwAovi5cd18mGkXzr9klFLk8rjprtGqr0AnVXHiPG
1GLpcQ+9NwXGNQWUmokNSWpnvGDYk8nKMacSu/LnAr9rm2BLG0+wdY3CP0q05fw=
=Ub7V
-----END PGP SIGNATURE-----

--------------enig4DF1351CE4ED8C9A252907E8--


From MAILER-DAEMON Sat Dec 22 11:45:08 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1TmSCC-00086q-QL
	for mharc-autoconf@gnu.org; Sat, 22 Dec 2012 11:45:08 -0500
Received: from eggs.gnu.org ([208.118.235.92]:49944)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gnu-autoconf@m.gmane.org>) id 1TmSC8-00082u-8M
	for autoconf@gnu.org; Sat, 22 Dec 2012 11:45:07 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gnu-autoconf@m.gmane.org>) id 1TmSBz-0007m1-GA
	for autoconf@gnu.org; Sat, 22 Dec 2012 11:45:04 -0500
Received: from plane.gmane.org ([80.91.229.3]:45800)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gnu-autoconf@m.gmane.org>) id 1TmSBz-0007lo-6B
	for autoconf@gnu.org; Sat, 22 Dec 2012 11:44:55 -0500
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <gnu-autoconf@m.gmane.org>) id 1TmSC7-0007rq-H1
	for autoconf@gnu.org; Sat, 22 Dec 2012 17:45:03 +0100
Received: from d51a5099b.access.telenet.be ([81.165.9.155])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <autoconf@gnu.org>; Sat, 22 Dec 2012 17:45:03 +0100
Received: from jefdriesen by d51a5099b.access.telenet.be with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <autoconf@gnu.org>; Sat, 22 Dec 2012 17:45:03 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: autoconf@gnu.org
From: Jef Driesen <jefdriesen@hotmail.com>
Subject: Re: Conditional AC_DEFINE with m4_define variable?
Date: Sat, 22 Dec 2012 17:29:55 +0100
Lines: 103
Message-ID: <kb4n61$ei9$1@ger.gmane.org>
References: <kb4hfk$3j3$1@ger.gmane.org> <50D5CF4B.1080807@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: d51a5099b.access.telenet.be
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
In-Reply-To: <50D5CF4B.1080807@redhat.com>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 80.91.229.3
Cc: automake@gnu.org
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Dec 2012 16:45:07 -0000

On 22-12-12 16:18, Eric Blake wrote:
 > [adding autoconf, as this question technically is independent of automake]
 >
 > On 12/22/2012 07:52 AM, Jef Driesen wrote:
 >> Hi,
 >>
 >> When I set a variable with:
 >>
 >> m4_define([dc_version_suffix],[devel])
 >>
 >> or leave it empty:
 >>
 >> m4_define([dc_version_suffix],[])
 >>
 >> And then try to conditionally call AC_DEFINE based on whether the
 >> dc_version_suffix is set or not, this doesn't work:
 >>
 >> AS_IF([test "x$dc_version_suffix" = "xdevel"], [
 >>     AC_DEFINE(ENABLE_PTY, [1], [Enable pseudo terminal support.])
 >> ])
 >
 > This will expand to either:
 >
 > test "x$" = "xdevel"
 >
 > or
 >
 > test "x$devel" = "xdevel"
 >
 > based on the macro value.  Probably not what you wanted.

That explains very well, why it doesn't work. I wasn't really aware of the
difference between m4 and shell variables.

 >> However if I use m4_isset, then it does kind of work, except that the
 >> USE_REVISION macro in the config.h is either defined, or not present at
 >> all.
 >>
 >> m4_ifset([dc_version_suffix],[
 >>     AC_DEFINE(USE_REVISION, [1], [Use the revision number.])
 >> ])
 >
 > Indeed, this actually does what _I_ would want - since dc_version_suffix
 > is known at m4 time, we might as well use that information to generate
 > the smallest possible configure.
 >
 > But if you _insist_ on delaying the decision until shell time, even
 > though the condition being tested is known at m4 time, then you probably
 > want to use something like this:

I do not insist on doing things in a particular way. I just want something that
works and preferably done the right way  See below for an explanation of what
I'm trying to achieve.

 >> Does anyone know how to implement this correctly?
 >
 > It really depends on what you are trying to accomplish by deciding
 > something at m4 time, but deferring the action on that decision until
 > configure time.

What I want to accomplish is as follows. I have a dc_version() function in my
library which returns the version number. The main part of the version number is
generated directly from configure.ac (with AC_SUBST and a version.h.in file).
But I also generate a revision.h file at build time containing the git SHA1. So
far no problem. But now I'm trying to append this git revision info for
non-release builds (e.g. dc_version_suffix not empty). So my version.c file
contains roughly this:

#ifdef HAVE_CONFIG_H
#include "config.h"
#endif

#include <libdivecomputer/version.h> /* Defines the DC_VERSION macro. */

#ifdef USE_REVISION
#include "revision.h"/* Defines the DC_VERSION_REVISION macro. */
#endif

const char *
dc_version (dc_version_t *version)
{
#ifdef USE_REVISION
	return DC_VERSION " (" DC_VERSION_REVISION ")";
#else
	return DC_VERSION;
#endif
}

So I wanted to have this USE_REVISION macro somehow end up in the config.h
header, such that the above code would work.

The m4_ifset based test does that, but if the dc_version_suffix is empty, the
USE_REVISION macro is not present in the config.h file at all. Usually when you
define any sort of tests (e.g. AC_CHECK_*), then the corresponding macros always
ends up in the config.h file, but uncommented when not available. Like this:

/* Use the revision number. */
/* #undef USE_REVISION */

When using an AS_IF based test, that's the case too. So that's why I thought the
m4_ifset test was not the right tool.

Jef



From MAILER-DAEMON Mon Dec 31 16:21:35 2012
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Tpmnf-0004wH-0p
	for mharc-autoconf@gnu.org; Mon, 31 Dec 2012 16:21:35 -0500
Received: from eggs.gnu.org ([208.118.235.92]:38923)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1Tpmnd-0004w5-69
	for autoconf@gnu.org; Mon, 31 Dec 2012 16:21:34 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TpmnV-0005Ak-Ei
	for autoconf@gnu.org; Mon, 31 Dec 2012 16:21:33 -0500
Received: from mx1.redhat.com ([209.132.183.28]:2806)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eblake@redhat.com>) id 1TpmnV-0005Ae-7V
	for autoconf@gnu.org; Mon, 31 Dec 2012 16:21:25 -0500
Received: from int-mx12.intmail.prod.int.phx2.redhat.com
	(int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qBVLLO8o017081
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 31 Dec 2012 16:21:24 -0500
Received: from [10.3.113.75] (ovpn-113-75.phx2.redhat.com [10.3.113.75])
	by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP
	id qBVLLL3o020163; Mon, 31 Dec 2012 16:21:23 -0500
Message-ID: <50E201D1.5080900@redhat.com>
Date: Mon, 31 Dec 2012 14:21:21 -0700
From: Eric Blake <eblake@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Jef Driesen <jefdriesen@hotmail.com>
Subject: Re: Conditional AC_DEFINE with m4_define variable?
References: <kb4hfk$3j3$1@ger.gmane.org> <50D5CF4B.1080807@redhat.com>
	<BLU0-SMTP188FDF2C4FBD8E53311CC7BC4350@phx.gbl>
In-Reply-To: <BLU0-SMTP188FDF2C4FBD8E53311CC7BC4350@phx.gbl>
X-Enigmail-Version: 1.4.6
OpenPGP: url=http://people.redhat.com/eblake/eblake.gpg
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature";
	boundary="------------enig94836BCEAB72975A0BD87CBD"
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.25
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x
X-Received-From: 209.132.183.28
Cc: "autoconf@gnu.org" <autoconf@gnu.org>
X-BeenThere: autoconf@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion list for the autoconf build system <autoconf.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/autoconf>
List-Post: <mailto:autoconf@gnu.org>
List-Help: <mailto:autoconf-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/autoconf>,
	<mailto:autoconf-request@gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 21:21:34 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig94836BCEAB72975A0BD87CBD
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/22/2012 09:07 AM, Jef Driesen wrote:
> On 22-12-12 16:18, Eric Blake wrote:
>> [adding autoconf, as this question technically is independent of
>> automake]
>>
> What I want to accomplish is as follows. I have a dc_version() function=

> in my library which returns the version number. The main part of the
> version number is generated directly from configure.ac (with AC_SUBST
> and a version.h.in file). But I also generate a revision.h file at buil=
d
> time containing the git SHA1. So far no problem. But now I'm trying to
> append this git revision info for non-release builds (e.g.
> dc_version_suffix not empty).

You may be interested in seeing how GNU Coreutils approaches this.  It
uses a tool git-version-gen from gnulib, as well as some hooks into
configure.ac and Makefile.am, so that if you are building from
coreutils.git, then the git version is injected as a suffix into the
generated version string via a file version.[ch], and if you are
building from a tarball, then the information is hard-coded and there is
no suffix.  By sticking the version information in a separate .c file,
it becomes merely a matter of linking to the new .o file (rather than
recompiling the world) when the version number changes.

> So my version.c file contains roughly this:
>=20
> #ifdef HAVE_CONFIG_H
> #include "config.h"
> #endif

Within a single project, you should know whether you are using config.h;
being conditional only matters for libraries like libtool that are
designed to work even without autoconf.  That is, these days, most
people _don't_ need #ifdef HAVE_CONFIG_H, but can blindly assume that it
is in use.

>=20
> #include <libdivecomputer/version.h> /* Defines the DC_VERSION macro. *=
/
>=20
> #ifdef USE_REVISION
> #include "revision.h"/* Defines the DC_VERSION_REVISION macro. */
> #endif

Makes sense.

> So I wanted to have this USE_REVISION macro somehow end up in the
> config.h header, such that the above code would work.
>=20
> The m4_ifset based test does that, but if the dc_version_suffix is
> empty, the USE_REVISION macro is not present in the config.h file at
> all. Usually when you define any sort of tests (e.g. AC_CHECK_*), then
> the corresponding macros always ends up in the config.h file, but
> uncommented when not available. Like this:
>=20
> /* Use the revision number. */
> /* #undef USE_REVISION */

Ah, so you want the template to be visible to autoheader, even when the
template is not in use from a tarball.

>=20
> When using an AS_IF based test, that's the case too. So that's why I
> thought the m4_ifset test was not the right tool.

Yeah, m4_ifset hides the entire AC_DEFINE from view of any other tool,
like autoheader, that scans for m4 calls.  If you want the template to
appear unconditionally, but only be defined when needed, you might try:

if m4_ifset([dc_version_suffix], [:], [false]); then
  AC_DEFINE([USE_REVISION], [1], [Use the revision number.])
fi

which then makes the AC_DEFINE() unconditionally expanded at m4 time (so
autoheader will list the template), but the shell decision on whether to
do anything is now minimized.

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--------------enig94836BCEAB72975A0BD87CBD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBCAAGBQJQ4gHRAAoJEKeha0olJ0NqsNUH+gI9dBnedP+nBA4qTQIVfwZI
bMMJkBb1cD1zfGWHpeUOMqs2aGAXGKAION0A/yOIr1C0OKBeMLH5wj7nqYZVh8eR
a4tQ4Vh3Q+VO4fXBvTHpxQcutg6i0fU14g5rTpmLlXAnyHh9f3tCuBdoaChwmSSh
GcspzcZV4zmmAlVLZiR0floa7izVGZCBnciskNbnGDYuMixZzZ6i+V7iaJgRzk05
DGk+u3a7+Kjz1OHBPZ9/kqdLMQQeTxrFphGzQcrDJzxHBkSgUANLomvzc7LJcCM5
RphGc4VELYwwZ20RMDN6cnRU4tnT5u7cd3AH8PfsDKsAM0PIfBypKBrB2Mjbq7E=
=vMpH
-----END PGP SIGNATURE-----

--------------enig94836BCEAB72975A0BD87CBD--


