On Dienstag, 3. Oktober 2017 18:31:45 CEST Avinash Sonawane wrote: > On Mon, Oct 2, 2017 at 8:56 PM, Tim Rühsen <tim.rueh...@gmx.de> wrote: > > On 10/02/2017 10:00 AM, l...@langs.se wrote: > >> Hi! > >> > >> I get the following error when compiling wget 1.19.1 on AIX 7.1: > >> > >> make all-am > >> CC connect.o > >> CC convert.o > >> CC cookies.o > >> CC ftp.o > >> lex -ocss.c > >> 0: Warning: 1285-300 The o flag is not valid. > >> 0: Warning: 1285-300 The s flag is not valid. > >> 0: Warning: 1285-300 The s flag is not valid. > >> 0: Warning: 1285-300 The . flag is not valid. > >> > >> Seems the LEX arguments are not valid? > >> > >> Any suggestions? > > > > Hi, > > > > some 'lex' versions *must have* a space after -o, some others *must not > > have* a space there. We decided not to use a space since this covers > > most build environments. > > I am concerned about the `-o` option itself. As per the POSIX.1-2008 > [0], lex only supports -t, -n and -v. Though agreed flex is the de > facto implementation of lex which supports `-o`, I think we should > stick to the POSIX standard and shouldn't use `-o`. > > I see 2 possible approaches: > 1. use lex.yy.c, default file generated or > 2. use `-t >` to have the desired custom filename.
We had that several times in the past - and no solution fits in all situations. I don't remember the details right now just the "don't touch it conclusion". Search the mailing list archives... but don't waste your time. Regards, Tim
signature.asc
Description: This is a digitally signed message part.
