Hi James
> On 23 Jun 2025, at 17:08, Richard Biener via Gcc wrote:
>> Am 23.06.2025 um 17:56 schrieb James K. Lowden :
>> On Sat, 21 Jun 2025 11:03:19 +0200
>> Richard Biener wrote:
>>
A comparison of the mentions of "fixinclude" in config.{status,log}
of two directories, bootstrap a
> Am 23.06.2025 um 17:56 schrieb James K. Lowden :
>
> On Sat, 21 Jun 2025 11:03:19 +0200
> Richard Biener wrote:
>
>>> A comparison of the mentions of "fixinclude" in config.{status,log}
>>> of two directories, bootstrap and non-bootstrap, shows no
>>> difference.
>>>
>>> What should I b
On Sat, 21 Jun 2025 11:03:19 +0200
Richard Biener wrote:
> > A comparison of the mentions of "fixinclude" in config.{status,log}
> > of two directories, bootstrap and non-bootstrap, shows no
> > difference.
> >
> > What should I be looking for?
>
> For why fixinclude isn?t built - the config.
> On 21 Jun 2025, at 12:03, Richard Biener via Gcc wrote:
>
>
>
>> Am 21.06.2025 um 08:45 schrieb James K. Lowden :
>>
>> I guess I'm doing something wrong, or not enough. "make install" is
>> failing after a bootstrap build because the build/fixincludes directory
>> is empty. Edited for
> Am 21.06.2025 um 08:45 schrieb James K. Lowden :
>
> I guess I'm doing something wrong, or not enough. "make install" is
> failing after a bootstrap build because the build/fixincludes directory
> is empty. Edited for brevity:
>
> $ make -C build-boot/ V=1 install
> make: Entering directo
