>>> The *BSD makes don't
>>> suffer from it either. As for AIX, IRIX and OSF1/Tru64, I don't have
>>> access to those systems, so I can't test how their make implementations
>>> behave.
>>
>> I have aix 5.3 and aix 6.1 here. So if you tell me how it's best to
>> check…
>>
> You can use this Makefi
On Mon, Jul 23, 2012 at 4:42 PM, Stefano Lattarini
wrote:
> [Re-adding the list, as this discussion is worth being registered in
> the archives IMHO]
>
Ok.
The situation is that both of the approaches (.pc.c rule and .pc.lo
rule) have problems entailed.
>>>
* .pc.lo rule doesn't c
Ah, sorry. That's so easy, and now i recollect you must have said this
before, but i've lost it...
2011/1/13 ralf.wildenhues :
> * Юрий Пухальский wrote on Wed, Jan 12, 2011 at 03:21:11PM CET:
>> -
>> SUFFIXES = .pc
>>
>> .pc.lo:
&
2011/1/13 Stefano Lattarini :
> On Thursday 13 January 2011, Юрий Пухальский wrote:
>> Good day.
>>
>> I'll throw my humble userish $0.02 in here.
>>
>> First of all, i like the idea of autotools working in any POSIX
>> enviroment, requiring a s
Good day.
I'll throw my humble userish $0.02 in here.
First of all, i like the idea of autotools working in any POSIX
enviroment, requiring a set of tools that is everywhere by definition.
Because when for example i try to compile my project in hostile
environment with suspicious admins that watc
Andre, i think it can be done, as from what i've picked ylwrap
operates in temporary directory anyway, so that should be no problem
picking whatever lex has dropped, be it .c or .cc.
As for recognizing the suffix - it might be troublesome for a file
with .l extension having option c++ inside. The r
Good evening!
Thank You for the reply, Andre!
I'm sure that it will work, but to me it looks as hacky as the %option
approach. Shouldn't automake hide these nasty details from me?
Another problem i've stumbled upon:
The same thing with files and renaming occurs when compiling bison file:
it's be
Good day!
I've a lex file with %option c++.
Being processed by lex it produces by default a file named lex.yy.cc,
while automake expects it to be lex.yy.c when constructing a line with
ylwrap:
/bin/sh ./ylwrap engine_tcp_lex.ll lex.yy.c engine_tcp_lex.cc -- flex -d
Setting LEX_OUTPUT_ROOT doesn't
