Re: verbosity

Ralf Wildenhues wrote: > * Christopher Sean Morrison wrote on Mon, Jan 15, 2007 at 07:55:27PM CET: >> Counterproductive presumptuous flamings aside, there are compelling >> arguments on both sides of the issue for having or quelling verbose >> compilation output. > > Yes, the flaming all helps

enable dependency tracking whenever available

Is there a way to enable dependency tracking by default even if only slow mechanisms are available (as if --enable-dependency-tracking were always specified?). thanks, - jason

Re: enable dependency tracking whenever available

Hello Jason, * Jason Kraftcheck wrote on Thu, Jan 18, 2007 at 07:39:30PM CET: > Is there a way to enable dependency tracking by default even if only slow > mechanisms are available (as if --enable-dependency-tracking were always > specified?). You mean as the package developer? Put : ${enable_

Re: verbosity

* Jason Kraftcheck wrote on Thu, Jan 18, 2007 at 07:10:19PM CET: > Ralf Wildenhues wrote: > > > > > > I don't understand why this is such a controversial issue. Then - you must not have had to deal with Makefile.in files s

Re: enable dependency tracking whenever available

Ralf Wildenhues wrote: > Hello Jason, > > * Jason Kraftcheck wrote on Thu, Jan 18, 2007 at 07:39:30PM CET: >> Is there a way to enable dependency tracking by default even if only slow >> mechanisms are available (as if --enable-dependency-tracking were always >> specified?). > > You mean as the p

Re: verbosity

Ralf Wildenhues wrote: > * Jason Kraftcheck wrote on Thu, Jan 18, 2007 at 07:10:19PM CET: >> Ralf Wildenhues wrote: >>> >> I don't understand why this is such a controversial issue. > > Then > - you must not have had to dea

Re: enable dependency tracking whenever available

* Jason Kraftcheck wrote on Thu, Jan 18, 2007 at 08:58:13PM CET: > Ralf Wildenhues wrote: > > : ${enable_dependency_tracking=yes} > Why not just > if test "x$enable_dependency_tracking" = "x"; then > enable_dependency_tracking=yes > fi > > Is it problematic or non-portable for some rea

Re: problem with a test that is expected to fail, on cygwin only...

* Ed Hartnett wrote on Tue, Jan 16, 2007 at 03:17:00AM CET: > > I am having a problem on cygwin only. > > I have a test which is expected to fail. In the Makefile.am I have > this: > > TESTFILES = nctst tst_failure > check_PROGRAMS = $(TESTFILES) > nctst_SOURCES = nctst.cpp > tst_failure_SOURCE

Re: verbosity

* Jason Kraftcheck wrote on Thu, Jan 18, 2007 at 09:50:31PM CET: > Ralf Wildenhues wrote: > > - you must not have had to deal with Makefile.in files several megabytes > > in size, > > No, I haven't. The largest I've had was about half a megabyte. I still > don't think prefixing a few commands

"make dist" problem...

Hi all! I have a little problem with my small project...every time I use the "make dist" command I obtain the following output: [EMAIL PROTECTED]:~/Desktop/DAMA$ make dist { test ! -d pegsolitaire-0.1 || { find pegsolitaire-0.1 -type d ! -perm -200 -exec chmod u+w {} ';' && rm -fr pegsolita

Re: "make dist" problem...

Ralf Wildenhues ha scritto: Which Automake version was used to bootstrap this package? Please also print the first 20 or so lines of output from make -n dist Thanks, Ralf Hi! I'm using automake (GNU automake) 1.9.6 and this is the requested output: { test ! -d pegsolitaire-0.1 || {

Re: "make dist" problem...

Hello Enrico, * Enrico wrote on Thu, Jan 18, 2007 at 10:12:39PM CET: > > I have a little problem with my small project...every time I use the > "make dist" command I obtain the following output: > > [EMAIL PROTECTED]:~/Desktop/DAMA$ make dist > { test ! -d pegsolitaire-0.1 || { find pegsolitai

Re: "make dist" problem...

* Enrico wrote on Thu, Jan 18, 2007 at 10:32:56PM CET: > > I'm using automake (GNU automake) 1.9.6 and this is the requested output: [...] > if test -f $file || test -d $file; then d=.; else d=.; fi; \ > dir=`echo "$file" | sed -e 's,/[^/]*$,,'`; \ > if test "$dir" != "$fil

Re: "make dist" problem...

Ralf Wildenhues ha scritto: M4 strips leading white space in macro arguments, but not trailing white space. Cheers, Ralf I've tried it and now all works well! Thanks for the help! Enrico

Re: M4 syntax $11 vs. ${11}

[ Can we limit this to, say, the m4-discuss and autoconf lists? ] Hi Eric, * Eric Blake wrote on Thu, Jan 18, 2007 at 03:50:09PM CET: > [...] > So would it be worth trying to change the m4sugar definition of m4_define > to something like the following: > > define([m4_define], [regexp([$2], [\$]

RE: warnings with automake 1.10 on cygwin / pstoedit.m4, libsmi.m4, etc.

On Wednesday, January 17th, 2007 @ 10:37a, Brian Dessent wrote: > David Byron wrote: > > > /usr/share/aclocal/libsmi.m4:8: warning: underquoted > > definition of AM_PATH_LIBSMI > > > > /usr/share/aclocal/libmcrypt.m4:17: warning: underquoted > > definition of AM_PATH_LIBMCRYPT > > > > /usr/share/