-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: stop hardcoding /usr/bin/gcc #75
Comments
The same is true for |
+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. |
Bug: oracle#75 Signed-off-by: Sam James <[email protected]>
Bug: oracle#75 Signed-off-by: Sam James <[email protected]>
I'm afraid that's almost certain to clash like mad with c80d7eb which I'm getting reviewed now :( |
That's in, so the clash has happened and things have settled down again. |
Thanks Nick. I'll rebase and test it, then send it soon. |
Sam, did you get a chance to do the rebase? |
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.The text was updated successfully, but these errors were encountered: