Re: may Automake rely on _AC_SUBST_VARS?

2009-04-08 Thread Ralf Wildenhues
Hi Eric, * Eric Blake wrote on Wed, Apr 08, 2009 at 05:53:00AM CEST: According to Ralf Wildenhues on 4/7/2009 12:41 PM: m4_define([_AC_COMPILER_EXEEXT], m4_defn([_AC_COMPILER_EXEEXT])[m4_provide([_AM_COMPILER_EXEEXT])]) m4_provide_if([_AM_COMPILER_EXEEXT],

Re: autoconf ^M vs echo+tr

2009-04-08 Thread Ralf Wildenhues
Hello Török, * Török Edwin wrote on Tue, Apr 07, 2009 at 10:02:00PM CEST: Regenerating configure with version 2.63 gives me: -ac_cr=`echo X | tr X '\015'` +ac_cr='^M' I thought the echo + tr was more portable, and it also works better with various tools that adjust newlines (like SVN with

Re: autoconf ^M vs echo+tr

2009-04-08 Thread Török Edwin
On 2009-04-08 09:09, Ralf Wildenhues wrote: Hello Török, * Török Edwin wrote on Tue, Apr 07, 2009 at 10:02:00PM CEST: Regenerating configure with version 2.63 gives me: -ac_cr=`echo X | tr X '\015'` +ac_cr='^M' I thought the echo + tr was more portable, and it also works better with

Re: Bison and flex target

2009-04-08 Thread Philip Herron
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey This works for me. But i have a problem it works only if i use 1 yacc/lex. But when i move to add in multiple lexer's etc not too sure how to make this work.. I see stuff on the gdb hack to redefine all the variables but not too sure how this is

Re: Bison and flex target

2009-04-08 Thread Ralf Wildenhues
Hello Philip, please don't top-post, thank you. Also, what do you think about moving to the automake list, where this topic fits better? Followup set. * Philip Herron wrote on Wed, Apr 08, 2009 at 03:20:00PM CEST: Ralf Wildenhues wrote: * Philip Herron wrote on Fri, Apr 03, 2009 at

Re: Autoconf. Generated configure file may use grep but does not unset the GREP_OPTIONS.

2009-04-08 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ilay Bobir on 4/4/2009 5:57 PM: Hi, Starting with version 2.4 GNU grep supports specification of default option values via GREP_OPTIONS environment variable. Many if not all of the configure files generated by the autoconf use

Re: Autoconf. Generated configure file may use grep but does not unset the GREP_OPTIONS.

2009-04-08 Thread Ralf Wildenhues
Hello Eiric, Ilay, * Eric Blake wrote on Wed, Apr 08, 2009 at 02:56:38PM CEST: According to Ilay Bobir on 4/4/2009 5:57 PM: Starting with version 2.4 GNU grep supports specification of default option values via GREP_OPTIONS environment variable. Many if not all of the configure files

Re: Autoconf. Generated configure file may use grep but does not unset the GREP_OPTIONS.

2009-04-08 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 4/8/2009 3:52 PM: Thanks for the report. I agree that unsetting GREP_OPTIONS as part of AC_PROG_GREP (and friends) sounds reasonable, Why not just unset it as part of AS_SHELL_SANITIZE? There are lots of plain