Re: Problem with AC_LINK_IFELSE and library order

2005-10-24 Thread Francesco Montorsi
Hi, Ralf Wildenhues wrote: It's usually more appropriate to prepend to LIBS (but to append to LDFLAGS!), in order to facilitate static linking. Thus, you should be using LIBS="-ltotest $LIBS" ok thanks; I'll do Francesco

Re: using VPATH in depend2.am?

2005-10-24 Thread Harald Dunkel
Hi, Stepan Kasal wrote: > Hello, > > > Suggested code for today: ;-) > > `IFS=:; v=$(VPATH); \ > for d in '' $$v; do \ > test -n "$$d" && d=$$d/; \ > test -f $${d}%SOURCE% && echo $$d && break; \ > done`%SOURCE% > Works for me, as it seems. Reg

Re: compile with VC++

2005-10-24 Thread Harald Dunkel
Hi Stepan, Stepan Kasal wrote: > > I looked at /usr/share/automake-1.9/compile and I cannot understand > how this could happen. > I think that the parametr to compile should look like > some/path/main.c > which becomes cfile, and then cofile is assigned as > > cofile=`echo "$cfile" | sed -

Re: compile with VC++ (was: AC_PROG_CC_C_O doesn't work with VC++)

2005-10-24 Thread Keith MARSHALL
Stepan Kasal wrote: > I think that the parametr to compile should look like >some/path/main.c > which becomes cfile, and then cofile is assigned as... Just guessing, but with cl.exe being Bill's C compiler, it probably doesn't understand `some/path/main.c' as a path name; (it will

Re: strange warnings from aclocal...

2005-10-24 Thread Ralf Wildenhues
Hi Ed, * Ed Hartnett wrote on Mon, Oct 24, 2005 at 04:34:27PM CEST: > > I am getting warnings from aclocal about a bunch of macros being > underquoted. But these are not my macros! They seem to be part of > aclocal. > /usr/share/aclocal/g-wrap.m4:7: warning: underquoted definition of > AC_GWRAP

compile with VC++ (was: AC_PROG_CC_C_O doesn't work with VC++)

2005-10-24 Thread Stepan Kasal
Hello, [ let's move to automake@gnu.org ] On Mon, Oct 24, 2005 at 04:20:44PM +0200, Harald Dunkel wrote: > I think I found the problem. The compile script says at the > end > : > if test -f "$cofile"; then > mv "$cofile" "$ofile" > elif test -f "${cofile}bj"; then >

strange warnings from aclocal...

2005-10-24 Thread Ed Hartnett
Howdy all! I am getting warnings from aclocal about a bunch of macros being underquoted. But these are not my macros! They seem to be part of aclocal. Is there a way to get rid of this so that I can see any "real" warnings? (That is, warnings related to the mistakes I'm making in my configuration

Re: using VPATH in depend2.am?

2005-10-24 Thread Stepan Kasal
Hello, On Fri, Oct 21, 2005 at 10:58:44PM +0200, Harald Dunkel wrote: > Stepan Kasal wrote: > > `IFS=:; x=':$(VPATH)'; \ > > for d in $$x; do \ > > test -n $$d && d=$$d/; \ > > test -f $${d}%SOURCE% && echo $$d && break; > > done`%SOURCE% > > I like this versio

Re: Doing something just a bit more complex than `make check'

2005-10-24 Thread Ralf Wildenhues
Hello there, * Roberto Bagnara wrote on Wed, Oct 19, 2005 at 09:13:16PM CEST: > > Instead, what I would like to have is to only say > > test1_SOURCES = test1.cc > test2_SOURCES = test2.cc > ... > > and then achieve the effect of (sorry for the pseudo-code) > >for flags in $FLAGS_CHOICES >

Re: Problem with AC_LINK_IFELSE and library order

2005-10-24 Thread Ralf Wildenhues
Hi Francesco, * Francesco Montorsi wrote on Sat, Oct 22, 2005 at 04:14:11PM CEST: > > I finally found that I was using > > LDFLAGS="$LDFLAGS -ltotest" *snip* > instead of > > LIBS="$LIBS -ltotest" > AC_LINK_IFELSE([ > AC_LANG_PROGRAM([#include ], >