On 09/03/2021 21:32, Gedare Bloom wrote:
My opinion is that the rolling development head is allowed to break on
tool updates, and that anyone doing a bisect needs to know that they
might need to rebuild/change tool versions.
For a git bisect it is important that you can check out the RSB of the
On Tue, Mar 9, 2021 at 1:46 PM Joel Sherrill wrote:
>
>
>
> On Tue, Mar 9, 2021 at 2:32 PM Gedare Bloom wrote:
>>
>> My opinion is that the rolling development head is allowed to break on
>> tool updates, and that anyone doing a bisect needs to know that they
>> might need to rebuild/change tool
On Tue, Mar 9, 2021 at 2:32 PM Gedare Bloom wrote:
> My opinion is that the rolling development head is allowed to break on
> tool updates, and that anyone doing a bisect needs to know that they
> might need to rebuild/change tool versions. How we actually codify
> that is something else. It woul
My opinion is that the rolling development head is allowed to break on
tool updates, and that anyone doing a bisect needs to know that they
might need to rebuild/change tool versions. How we actually codify
that is something else. It would be nice if there was a way to
automatically indicate the ne
Hi
With the recent newlib and tool updates, it should now be possible to merge
Eshan's ftw() test patches but this will result in the tests not building
with older tools which do not have ftw().
Does waf need to probe for ftw() presence on this test and only enable the
test when present? Or can t
