Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Akim Demaille
> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes: Russ> Respectively, I think you're significantly over-solving this Russ> problem. Just document somewhere what files can possibly be Russ> created and let the package author do what they wish with them, Russ> write a make distclean rule or

Re: Debian Autoconf bug report: Bug#138666: autoconf: AC_EXEEXT fails when CFLAGS="-fprofile-arcs -ftest-coverage"

2002-04-03 Thread Akim Demaille
|Hi. I'm the maintainer of the Debian package for Autoconf. I |received the following bug report against Autoconf 2.52. It |looks like it still applies to Autoconf 2.53, so I'm passing it |along upstream with this message. | |Thanks, | |Ben. | |From: & Youngman <[EMAIL PROTECTED]> |Subject: Bu

net-snmp and uClibc

2002-04-03 Thread Arne Jonsson
Hi! I'm trying to crossmake a "small" snmp agent using the net-snmp package (cross to ARM that is). In order to make it "small" I'm using the uClibc C-library. This works OK, i.e it compiles and links (I haven't tested it yet). But, when configuring the net-snmp package the autoconf tools checks

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Akim Demaille
> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes: Peter> Akim Demaille writes: >> In fact, I think all the tools should provide some --clean. For >> instance, the hair we have to clean the Texinfo related files have >> nothing to do in Automake. It should be provided by texi2dvi and

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Akim Demaille
> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes: Peter> Akim Demaille writes: >> And, as far as Automake goes, I don't think I'm making things worse >> to its non-users. Nothing changes for them. Peter> Possibly true, but try to keep a clean separation between Peter> Autoconf and A

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Earnie Boyd
Paul Eggert wrote: > > > Date: Tue, 02 Apr 2002 22:41:50 -0800 > > From: Dan Kegel <[EMAIL PROTECTED]> > > > > Clearly, one would also want cp --clean. > > "rm --clean" would be far more useful. I've often wanted that, > usually right after I've removed the wrong thing. > > (Sorry, Akim, could

RE: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Robert Collins
I think there are valid points to both the 'tools don't clean up after themselves' and the 'autoconf and automake shouldn't be in lockstep' arguments. IMO autoconf will make life easier for both automake and non-automake users by providing a clean capability of it's own. That in itself should mak

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Akim Demaille
| Akim Demaille writes: | > What I'm doing now is buying my freedom. The freedom to extend | > Autoconf without 1. requiring from the rest of the world that they | > adjust their distclean rules, 2. requiring that Automake folks release | > a newer Automake etc., not to mention that it needs 1.

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Thomas Dickey
On Wed, Apr 03, 2002 at 11:12:26PM +1000, Robert Collins wrote: > As a secondary point, as a user, I'd love to see one of two things: > * looser coupling between automake and autoconf, or good > * a single product. bad (there's been no good come out of mashing automake into autoconf). -- Tho

Re: 2.53 doesn't work on MacOS X

2002-04-03 Thread David Thompson
Output from make check (I tried to send the whole thing but the list rejected it. If there is someplace to send the whole check, let me know): [localhost:~/src/autoconf-2.53] dthompsn% make check Making check in bin make[1]: Nothing to be done for `check'. Making check in tests make autoconf a

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Peter Eisentraut
Akim Demaille writes: > What I'm doing now is buying my freedom. The freedom to extend > Autoconf without 1. requiring from the rest of the world that they > adjust their distclean rules, 2. requiring that Automake folks release > a newer Automake etc., not to mention that it needs 1. writing >

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Russ Allbery
Akim Demaille <[EMAIL PROTECTED]> writes: > You miss one point: killing this impedance problem. When Autoconf adds > new files, e.g., autom4te.cache, Automake is immediately obsoleted, > because it does not remove this file. That's not exactly a horrible failure mode. People can just add it to

Re: RFC: ./configure or ./config.status --clean

2002-04-03 Thread Roger Leigh
On Wed, Apr 03, 2002 at 07:04:07PM +0200, Akim Demaille wrote: > > | Akim Demaille writes: > | > What I'm doing now is buying my freedom. The freedom to extend > | > Autoconf without 1. requiring from the rest of the world that they > | > adjust their distclean rules, 2. requiring that Automake

an AC_PATH_PROG curiousity

2002-04-03 Thread Steve M. Robbins
Hi, It appears that AC_PATH_PROG has changed behaviour between 2.13 and 2.5x. If the following configure.in file is processed with autoconf 2.13, all three calls correctly find "ls" AC_INIT AC_PATH_PROG(LS1,ls,no) echo "LS=$LS1" AC_PATH_PROG(LS2,ls,no,$PATH) echo "LS=$LS2