Open thesamesam opened 2 months ago
The same is true for objdump
and all such toolchain tools.
+1
Totally agreed. This was a short-term kludge of mine in 2011 -- it's long past time for it to get fixed properly. A nice boring job given how pervasive this is :)
I don't mind taking it. I already have a stack of other test fixes it might conflict with, even.
Do we have a patch for this?
No, I'm happy to do it, but I was hoping to have my test fixes in first (already sent). I can prepare the patches now but I was worried about conflicts.
I am looking at the patches already submitted to pull them in.
I'm afraid that's almost certain to clash like mad with https://github.com/oracle/dtrace-utils/commit/c80d7ebb0b1b413115d94f5004caa1f62c9c76f7 which I'm getting reviewed now :(
Many tests have lines like
test/unittest/usdt/tst.guess32.sh:14:CC=/usr/bin/gcc
. They should respect CC from the environment to allow testing with different GCC versions.e.g. On my system,
/usr/bin/gcc
is usually GCC trunk, but I might want to compare GCC 14 with that to check for regressions.