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
python3 fails to build if directory or sysroot contains "*icc*" string #77522
Comments
Hello, as said, in yocto we pass in $CC environment, also the --sysroot keyword. If --sysroot contains the "*icc*" or "*gcc*" in path, the build fails because of wrong autoconf checks. checking in a case switch for *icc* seems bad to me, I propose to change it with something like I know this isn't a strong patch, but maybe we can apply it while writing some better detect code. The build fails as descripted in the yocto bug |
I signed the contributor agreement, even if such patches shouldn't need any kind of license |
Thank you. Yes, we require a signed CA for something this non-trivial. Victor, I don't know who maintains configure. If you don't, maybe you know who does. |
Maybe this is the same as bpo-28584, about the ${CC} variable rather than “sysroot”. In any case, the patch looks unrelated. |
This was the patch I wanted to add, but I picked up a wrong one (a vbox one) In any case, duplicate of bpo-28584 |
icc-find.patch (and a 2nd version) has been uploaded to bpo-28584 also. I unlinked the erroneous upload 'patch'. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: