diff options
author | Alan Modra <amodra@gmail.com> | 2023-04-26 09:59:40 +0930 |
---|---|---|
committer | Alan Modra <amodra@gmail.com> | 2023-04-26 10:32:07 +0930 |
commit | 4a8635cbecbd4eefa6dafdc4510014ad1755ddc3 (patch) | |
tree | d8c98a8c902c8bd843b7cf8cf289a07918cf5505 /opcodes | |
parent | 5b429b870767e2107bcc7d5d849e04d6901b5912 (diff) | |
download | binutils-4a8635cbecbd4eefa6dafdc4510014ad1755ddc3.zip binutils-4a8635cbecbd4eefa6dafdc4510014ad1755ddc3.tar.gz binutils-4a8635cbecbd4eefa6dafdc4510014ad1755ddc3.tar.bz2 |
binutils runtest $CC
I noticed in the binutile Makefile that runtest is being invoked with
CC, CC_FOR_BUILD and other compiler related flags in the environment.
That doesn't work. Those variables ought to be passed on the runtest
command line.
After fixing that I had some fails due to binutils testprog.c now
being compiled with the default "-g -O2" picked up in
CFLAGS_FOR_TARGET. Hack around that by passing -O0.
Also, with the binutils testsuite now taking notice of CC_FOR_TARGET,
I found a couple of debuginfod.exp fails with one of my compilers that
happened to be built without --debug-id being enabled by default.
* Makefile.am (check-DEJAGNU): Pass $CC and other variable on
the runtest command line rather than futilely in the
environment. Add -O0 to CFLAGS_FOR_TARGET.
* Makefile.in: Regenerate.
* testsuite/binutils-all/debuginfod.exp: Compile testprog.c
with -Wl,--build-id.
Diffstat (limited to 'opcodes')
0 files changed, 0 insertions, 0 deletions