-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
tools/build.py does not adhere to $CXX env variable settings #24289
Comments
This is of course related with my BSD porting efforts: #10260 |
I was provided by a nice temporary workaround from http://bsdguru.in/29/shadow-the-base-from-external-apps-they-use-egcc-unkowningly - I still think this is a build issue that should eventually get fixed. For anyone wondering the workaround is:
|
Found another place that ignores the environment. This one is even worse than the previous one since base gcc & g++ are not on PATH so it must hard code the path somewhere?
|
Checked with build.py -v, seems that this spot of the build uses 'cc' which I didn't shadow from the system. Still another place that should be fixed up imho.
|
The GYP build was replaced with a GN build. |
While building on OpenBSD the base system ships with g++ 4.2.1
There is a newer gcc/g++ installed via ports as egcc/eg++
Doing
export CXX=eg++
allowed me to move forward with the port but after a significant amount of code got build the setting seems to no longer being adhered to. Leading to a build failure due to a flag that is not recognised in g++ but would normally be recognized by eg++.The text was updated successfully, but these errors were encountered: