On Thu, Mar 15, 2018 at 05:29:39AM -0600, Jan Beulich wrote:
> >>> On 15.03.18 at 12:22, wrote:
> > On Thu, Mar 15, 2018 at 02:45:15AM -0600, Jan Beulich wrote:
> >> >>> On 14.03.18 at 18:11, wrote:
> >> > The implementation of cc-option (grepping the
>>> On 15.03.18 at 12:22, wrote:
> On Thu, Mar 15, 2018 at 02:45:15AM -0600, Jan Beulich wrote:
>> >>> On 14.03.18 at 18:11, wrote:
>> > The implementation of cc-option (grepping the option being tested in
>> > output) in Config.mk now makes it not
On Thu, Mar 15, 2018 at 02:45:15AM -0600, Jan Beulich wrote:
> >>> On 14.03.18 at 18:11, wrote:
> > The implementation of cc-option (grepping the option being tested in
> > output) in Config.mk now makes it not possible to detect if -Og is
> > supported because "-Og" doesn't
>>> On 14.03.18 at 18:11, wrote:
> The implementation of cc-option (grepping the option being tested in
> output) in Config.mk now makes it not possible to detect if -Og is
> supported because "-Og" doesn't appear in the output if it is not
> supported. I suspect there will
Hi all
The implementation of cc-option (grepping the option being tested in
output) in Config.mk now makes it not possible to detect if -Og is
supported because "-Og" doesn't appear in the output if it is not
supported. I suspect there will be other options that cc-option can't work
with.
It is