From: Simon Marchi <simon.marchi@polymtl.ca>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: jreiser@bitwagon.com, gdb-patches@sourceware.org
Subject: Re: Build failure with flex 2.5.4 (Re: [PATCH] fix race when building ada-lex.c)
Date: Thu, 03 May 2018 14:48:00 -0000 [thread overview]
Message-ID: <3a09991ea56b6936f3f90f3d11f2af93@polymtl.ca> (raw)
In-Reply-To: <20180503143759.39EC0D8050A@oc3748833570.ibm.com>
On 2018-05-03 10:37, Ulrich Weigand wrote:
> John Reiser wrote:
>
>> gdb/ChangeLog:
>> * gdb/Makefile.in: (.c:.l, .c:.y): Write the target only in
>> the
>> last step, and do it atomically.
>
>> + $(FLEX) --stdout $< \
>
> This causes a build failure on my RHEL 5 based Cell/B.E. dailybuild,
> since flex 2.5.4 does not yet support the long option --stdout.
>
> Is there any reason not to use the equivalent short option -t instead?
>
> Bye,
> Ulrich
Huh, I also wondered whether --stdout was a widely available option. I
found it was added by this commit in flex:
https://github.com/westes/flex/commit/16fe6f3
and since it is 16-17 years old, I didn't raise a flag. But we can
certainly use -t. Can you confirm it works as intended on that system?
Simon
next prev parent reply other threads:[~2018-05-03 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 21:13 [PATCH] fix race when building ada-lex.c John Reiser
2018-04-29 15:58 ` Simon Marchi
2018-05-03 14:40 ` Build failure with flex 2.5.4 (Re: [PATCH] fix race when building ada-lex.c) Ulrich Weigand
2018-05-03 14:48 ` Simon Marchi [this message]
2018-05-03 15:08 ` Ulrich Weigand
2018-05-03 21:35 ` Simon Marchi
2018-05-04 9:07 ` Ulrich Weigand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a09991ea56b6936f3f90f3d11f2af93@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=jreiser@bitwagon.com \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox