For GCC, newlib combined tree, newlib build-tree testing, use standard search paths

[Thomas Schwinge]

Hi!

OK to push to newlib main branch the attached
"For GCC, newlib combined tree, newlib build-tree testing, use standard search paths"
-- or is something else wrong here, or should this be done differently?
(I mean, I'm confused why this doesn't just work; I'm certainly not the
first person to be testing such a setup?)

I'm not doing anything special here: just symlink 'newlib' into the GCC
source directory, build the combined tree, and then run 'make check', as
mentioned in the attached Git commit log.


Grüße
 Thomas


-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-For-GCC-newlib-combined-tree-newlib-build-tree-testi.patch
Type: text/x-diff
Size: 1750 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/newlib/attachments/20230414/2dc1d93e/attachment.bin>