Hi

On Thu, Mar 21, 2024 at 08:48:01PM +0100, Helmut Grohne wrote:

I was recently working on gcc builds and this disagreement currently
makes stuff unbuildable. Hence I looked into solutions and/or
workarounds.

Care to just share what you actually found? Where is it broken and how
to see this?

Because this whole thing started with "it is broken, but I won't tell
you where or what or how".

On Tue, Mar 05, 2024 at 09:50:27AM +0100, Helmut Grohne wrote:

You just said that the search path used during the build of the
toolchain and the one for everything else are unrelated. So you are
free to create $BUILD/tmp-include with symlinks for asm, asm-generic, linux.

The toolchain as installed already finds all headers. So I still don't see why we need this in the final system.

I find this argument fairly convincing and hope Matthias also does.

As a result, I implemented the proposed change and am attaching it for discussion here. I've implemented it in a way that if there is a sysroot linux header installation, it'll be preferred. Do you see any downsides
of this approach?

I wonder now. How would that ever work for the native build? Or does
the native build already do those symlinks? Or are native and cross
configured differently? Or is that a weird difference in gcc itself?

Bastian

--
Oblivion together does not frighten me, beloved.
-- Thalassa (in Anne Mulhall's body), "Return to Tomorrow",
stardate 4770.3.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)