diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2023-04-14 21:26:32 +0200 |
|---|---|---|
| committer | Thomas Schwinge <thomas_schwinge@mentor.com> | 2023-06-22 21:41:30 +0200 |
| commit | 4c7d0dfec5793cbf5cf3930b91f930479126d8ce (patch) | |
| tree | f04b80e3a3e916089a858cdada5d3820e4c2360d /winsup | |
| parent | 6b2ae32ecdfdb8ca1337e19fac3b6e0a4079e769 (diff) | |
| download | newlib-4c7d0dfec5793cbf5cf3930b91f930479126d8ce.zip newlib-4c7d0dfec5793cbf5cf3930b91f930479126d8ce.tar.gz newlib-4c7d0dfec5793cbf5cf3930b91f930479126d8ce.tar.bz2 | |
For GCC, newlib combined tree, newlib build-tree testing, use standard search paths
For example, for GCC/GCN target (AMD GPUs), target libraries are built
individually per supported hardware ISA ('-march=[...]'). Testing such a
toolchain via, for example:
$ make RUNTESTFLAGS='--target_board=[...]/-march=gfx90a' check[...]
... does work fine for all 'check-gcc-[...]' as well as GCC-provided target
libraries, 'check-target-[...]'. Just for 'check-target-newlib', for the
example above, not the '-march=gfx90a' newlib libraries are linked in, but
instead always the default ones, which results in link FAILure. This is cured
simply by skipping use of 'newlib/testsuite/lib/flags.exp', so that the
standard search paths as determined by GCC, DejaGnu are used for newlib, too.
Diffstat (limited to 'winsup')
0 files changed, 0 insertions, 0 deletions