Re: traces output order

2008-03-21 Thread Ralf Wildenhues
* Eric Blake wrote on Fri, Mar 21, 2008 at 03:23:07AM CET: > > Primarily? Always! M4 traces are output in the order encountered (but > note that nested macros are traced during argument collection, prior to > the trace of the macro they are feeding). Hmm. That means my current AM_COND_IF patch

Re: traces output order

2008-03-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Ralf, According to Ralf Wildenhues on 3/21/2008 1:18 AM: | Hmm. That means my current AM_COND_IF patch will treat | | AM_COND_IF([OUTER], | [$outer_action | AM_COND_IF([INNER], | [$inner_acti

AC_PROG_LEX behavior

2008-03-21 Thread Stefan Seefeld
I'm trying to use AC_PROG_LEX to discover whether flex (or lex) is available. During testing I found out that, even when neither is available, the LEX variable is set to ':' instead of being empty. And sure enough, I subsequently found this in the programs.m4 code: AC_DEFUN_ONCE([AC_PROG_LEX],

Re: traces output order

2008-03-21 Thread Ralf Wildenhues
On Fri, March 21, 2008 13:20, Eric Blake wrote: > I think I see a way around the problem. Use the nesting level, which is > also part of the trace. For example, autoconf --trace=_AM_COND_IF:'$n-$d' > can tell you that _AM_COND_IF-2 was probably invoked unquoted within > _AM_COND_IF-1. For more a

Re: Implementation of `AC_COMPUTE_INT'

2008-03-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ineiev on 3/21/2008 12:21 AM: | --- Ralf Wildenhues <[EMAIL PROTECTED]> wrote: |> For example: |> |> # We temporarily set cross-compile mode to force AC_COMPUTE_INT |> # to use the slow link-only method |> save_cross_compiling=$cross_com

Negation semantics for LD_FLAGS?

2008-03-21 Thread Bill McGonigle
Hi, I'm looking for a way to tell configure _not_ to look in a directory for libraries, in this case /usr/local/lib. This would be the inverse of LDFLAGS='-L/usr/local/lib'. Here's the scenario: I'm working with a package management system (fink) which maintains its own software tree, b

Re: Negation semantics for LD_FLAGS?

2008-03-21 Thread Bob Friesenhahn
On Fri, 21 Mar 2008, Bill McGonigle wrote: I'm looking for a way to tell configure _not_ to look in a directory for libraries, in this case /usr/local/lib. This would be the inverse of LDFLAGS='-L/usr/local/lib'. How would you like to handle the case where the compiler looks in /usr/local/

Re: Negation semantics for LD_FLAGS?

2008-03-21 Thread Brian Dessent
Bill McGonigle wrote: > I'm looking for a way to tell configure _not_ to look in a directory > for libraries, in this case /usr/local/lib. This would be the I think you're attributing a behavior to autoconf that doesn't exist. Nowhere does autoconf add -L/usr/local/lib unless you explicitly cod

Re: Negation semantics for LD_FLAGS?

2008-03-21 Thread Bill McGonigle
On Mar 21, 2008, at 21:56, Brian Dessent wrote: I think you're attributing a behavior to autoconf that doesn't exist. Nowhere does autoconf add -L/usr/local/lib unless you explicitly code it as such in a test. That the linker searches /usr/local/lib by default is an aspect of how it was bui

header check, cross compiling and compiler version?

2008-03-21 Thread aaragon
Hi everyone, I used to write c++ code in Ubuntu Linux, and then I started working on Mac OS so I had to transfer all my c++ code to the new system. My first task was to get a newer compiler than the one that is shipped by default with Leopard so using macports I compiled GCC v4.3. Now, for my sur

Re: header check, cross compiling and compiler version?

2008-03-21 Thread Peter O'Gorman
aaragon wrote: > Hi everyone, > > I used to write c++ code in Ubuntu Linux, and then I started working on Mac > OS so I had to transfer all my c++ code to the new system. My first task was > to get a newer compiler than the one that is shipped by default with Leopard > so using macports I compiled

Re: header check, cross compiling and compiler version?

2008-03-21 Thread Brian Dessent
aaragon wrote: > I used to write c++ code in Ubuntu Linux, and then I started working on Mac > OS so I had to transfer all my c++ code to the new system. My first task was > to get a newer compiler than the one that is shipped by default with Leopard > so using macports I compiled GCC v4.3. Now, f