Re: make check failures

2002-07-25 Thread Alexandre Duret-Lutz
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: >> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes: adl> The gnits2 and gnits3 failures show a difference between GNU adl> make and BSD make when run with the `-k' option: GNU make will adl> reflect whether it encountered an err

(no subject)

2002-07-25 Thread Free Concert Tickets!
  TI wants to send you to your favourite concerts for free! Simply tell us what kind of music you like and we will notify you when your favourite shows are in your area. TI does not need your name or any other p

Re: turn off putting flex/bison output in distfile?

2002-07-25 Thread Alexandre Duret-Lutz
>>> "mcmahill" == mcmahill <[EMAIL PROTECTED]> writes: mcmahill> Is there a way to turn off the inclusion of lex and mcmahill> yacc generated output in the distfile? I've seen mcmahill> some problems where yacc on one box generates code mcmahill> which doesn't compile on a different box (as

Re: How to get .o not .lo files in foo_LINK command?

2002-07-25 Thread Grzegorz Jakacki
On Fri, 19 Jul 2002, Tom Tromey wrote: [...] > Grzegorz> Question: how can I get *.o files in the external linker > Grzegorz> command line? > > You can't. The .lo files are the ones you want, as they are compiled > -fPIC. Linking the .o files would be incorrect on some platforms. > > It is arg

Re: turn off putting flex/bison output in distfile?

2002-07-25 Thread Thomas E. Dickey
On Thu, 25 Jul 2002, Alexandre Duret-Lutz wrote: > >>> "mcmahill" == mcmahill <[EMAIL PROTECTED]> writes: > > mcmahill> Is there a way to turn off the inclusion of lex and > mcmahill> yacc generated output in the distfile? I've seen > mcmahill> some problems where yacc on one box generates c

Re: turn off putting flex/bison output in distfile?

2002-07-25 Thread Akim Demaille
> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes: Thomas> byacc is portable, and has the advantage (in contrast to Thomas> bison) of being written in ANSI C. ... which is written in?

Re: turn off putting flex/bison output in distfile?

2002-07-25 Thread Thomas E. Dickey
On 25 Jul 2002, Akim Demaille wrote: > > "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes: > > Thomas> byacc is portable, and has the advantage (in contrast to > Thomas> bison) of being written in ANSI C. > > ... which is written in? bison relies on alloca, which is not standard. There

Re: turn off putting flex/bison output in distfile?

2002-07-25 Thread Akim Demaille
> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes: Thomas> bison relies on alloca, which is not standard. There are two meaning of `relies alloca': - bison.exe uses alloca but has the machinery to emulate it when missing. No problem was ever reported. - the parsers it outputs u

RE: linking with libtool

2002-07-25 Thread Boehne, Robert
Title: RE: linking with libtool FYI,  Libtool mailing lists seem to be working again.   - Robert -Original Message-From: Boehne, Robert Sent: Friday, July 19, 2002 8:24 AMTo: 'Alexandre Duret-Lutz'; Enrico NgCc: [EMAIL PROTECTED]Subject: RE: linking with libtool Unfortuna

Re: Adding site specific rules to Automake

2002-07-25 Thread mlist . gnu . automake
==> "tom" == Tom Tromey <[EMAIL PROTECTED]> writes: tom> Probably not. That would basically be a fork; nobody else tom> would be able to recreate your Makefiles. Matthew> Is there some documentation about this? I have read the Matthew> Automake documentation and haven't seen any

Re: make check failures

2002-07-25 Thread Alexandre Duret-Lutz
patrick> - comment6 needs gnu make >> >> Which make are you using? I'd rather teach Automake to warn >> about this construct if it's not portable. It turns out it was easier to fix the user input rather than to warn about it. I'm installing the following patch on HEAD and branch-1-6. I th

Re: make check failures

2002-07-25 Thread Patrick Welche
On Thu, Jul 25, 2002 at 11:21:31PM +0200, Alexandre Duret-Lutz wrote: > patrick> - comment6 needs gnu make > >> > >> Which make are you using? I'd rather teach Automake to warn > >> about this construct if it's not portable. > > It turns out it was easier to fix the user input rather than t