Re: Autoconf regex test

2000-03-31 Thread Assar Westerlund
Geoff Hutchison <[EMAIL PROTECTED]> writes: > I think that's probably sufficient. Is there any place in the > autoconf manual that talks about how to access the programs you've > already found? For example, what variable contains the path to the > compiler? Is it ac_cxx_prog or something like t

Re: Autoconf regex test

2000-03-31 Thread Geoff Hutchison
At 2:36 AM +0200 4/1/00, Assar Westerlund wrote: >[ I've redirected this to the autoconf mailing list ] I didn't know it existed, I only saw comments about the automake one. Sorry! >The simple and dirty approach is to #include . Doh! As I said, I was drawing a blank. Of course this will work fi

Re: Autoconf regex test

2000-03-31 Thread Assar Westerlund
[ I've redirected this to the autoconf mailing list ] Geoff Hutchison <[EMAIL PROTECTED]> writes: > Basically, I want an AC_TRY_RUN test that includes the regex.c file in > compilation. Is this possible, or can you only compile/link the test > program file? The simple and dirty approach is to #

Re: catching build problems

2000-03-31 Thread Tom Tromey
>> How do I override the rule for entering one of them? Alexandre> I don't think you can override it :-( You can rewrite the entire rule, but of course that will break in a future version. Tom

Automake feature request (Was: catching build problems)

2000-03-31 Thread Lars J. Aas
On Fri, Mar 31, 2000 at 01:33:12PM -0300, Alexandre Oliva wrote: : On Mar 31, 2000, "Lars J. Aas" <[EMAIL PROTECTED]> wrote: : > How do I override the rule for entering one of them? : : I don't think you can override it :-( Looks like I have to push for such a feature to be integrated/implemente

Re: catching build problems

2000-03-31 Thread Alexandre Oliva
On Mar 31, 2000, "Lars J. Aas" <[EMAIL PROTECTED]> wrote: > How do I override the rule for entering one of them? I don't think you can override it :-( -- Alexandre OlivaEnjoy GuaranĂ¡, see http://www.ic.unicamp.br/~oliva/ Cygnus Solutions, a Red Hat companyaoliva@{redhat, cygnus}.co

Re: catching build problems

2000-03-31 Thread Alexandre Oliva
On Mar 31, 2000, "Lars J. Aas" <[EMAIL PROTECTED]> wrote: > : The trap is fine, but the `:=' syntax is far from portable. > Without it, wouldn't the variable become recursive? Yep. That's why you can't do it like that :-( It might work to set MAKE_TRAP as you suggested, and then use $(MAKE_TR

Re: catching build problems

2000-03-31 Thread Lars J. Aas
On Fri, Mar 31, 2000 at 01:19:54PM -0300, Alexandre Oliva wrote: : On Mar 31, 2000, "Lars J. Aas" <[EMAIL PROTECTED]> wrote: : : > : The trap is fine, but the `:=' syntax is far from portable. : : > Without it, wouldn't the variable become recursive? : : Yep. That's why you can't do it like th

Re: config.status usage

2000-03-31 Thread Akim Demaille
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes: Lars> it will fail for read-only source hierarchies. I'll try to remove the limitation of a relative path. In fact, it should be a nice thing to do, since it would help us to fix the last DOS issues. But gotta go. Have nice weekend ye all

Re: config.status usage

2000-03-31 Thread Lars J. Aas
On Fri, Mar 31, 2000 at 05:44:26PM +0200, Akim Demaille wrote: : > "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes: : Lars> This will produce out.tmp in $(builddir), but expect out.tmp to : Lars> be in $(srcdir) for the second pass, wouldn't it? Any hints on : Lars> what the best workaround t

Re: config.status usage

2000-03-31 Thread Akim Demaille
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes: Lars> This will produce out.tmp in $(builddir), but expect out.tmp to Lars> be in $(srcdir) for the second pass, wouldn't it? Any hints on Lars> what the best workaround to that small obstacle is? You're right, grmph. I don't how to handle

Re: catching build problems

2000-03-31 Thread Lars J. Aas
On Fri, Mar 31, 2000 at 12:24:10PM -0300, Alexandre Oliva wrote: : On Mar 31, 2000, "Lars J. Aas" <[EMAIL PROTECTED]> wrote: : : > On Fri, Mar 17, 2000 at 01:30:49PM +0100, Lars J. Aas wrote: : : > : MAKE := trap "cat $(top_srcdir)/troubleshooting" 1 2 15; $(MAKE) MAKE="$(MAKE)" : : > Does anyo

Re: config.status usage

2000-03-31 Thread Lars J. Aas
On Fri, Mar 31, 2000 at 05:13:30PM +0200, Akim Demaille wrote: : > "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes: : : Lars> I'd like to make config.status process a file that is both a : Lars> config header and a config file (do substitutions on both : Lars> @keyword@ and #undef KEYWORD).

Re: catching build problems

2000-03-31 Thread Alexandre Oliva
On Mar 31, 2000, "Lars J. Aas" <[EMAIL PROTECTED]> wrote: > On Fri, Mar 17, 2000 at 01:30:49PM +0100, Lars J. Aas wrote: > : MAKE := trap "cat $(top_srcdir)/troubleshooting" 1 2 15; $(MAKE) MAKE="$(MAKE)" > Does anyone know if setting up a trap on make like described below > will fail on some p

Re: config.status usage

2000-03-31 Thread Akim Demaille
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes: Lars> I'd like to make config.status process a file that is both a Lars> config header and a config file (do substitutions on both Lars> @keyword@ and #undef KEYWORD). Is there a one-step way of doing Lars> that with config.status, or do I h

config.status usage

2000-03-31 Thread Lars J. Aas
I'd like to make config.status process a file that is both a config header and a config file (do substitutions on both @keyword@ and #undef KEYWORD). Is there a one-step way of doing that with config.status, or do I have to make a temporary file? Lars J

Re: catching build problems

2000-03-31 Thread Lars J. Aas
I never got any response on this one, so I'm trying [EMAIL PROTECTED] too this time. Does anyone know if setting up a trap on make like described below will fail on some platform? Lars J On Fri, Mar 17, 2000 at 01:30:49PM +0100, Lars J. Aas wrote: : I just set up the following line in the bas