-
Notifications
You must be signed in to change notification settings - Fork 40
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
scons python modules malforms additional compiler flags in some cases #18
Comments
Fixed |
Thanks. Please note you have one more reference like this in CAMotics sources, I assume it could give the same issue: https://github.com/CauldronDevelopmentLLC/CAMotics/blob/83e0d40acef7f241919153b3746b49b0d8e0e8bc/src/cairo/SConscript#L7 |
Hmm, I think I've tried similar fix but then it was throwing different kind of error. Something like flags = re.sub(r'-Werro([^\s]+|r)', '', flags) |
I'm wary of replacing all specific |
But newest code with Fedora flags fails to build. I have to tamper with logic again.
|
You could install |
Also, adding |
This happens with |
C! is supposed to use the system bzip2 if it's available. Can you post the errors you find in
Perhaps the first line is a
Then delete the scons cache and rebuild:
Then search for bz2 in |
I am using mock to build the package, mock recreates build tree every time it is started. It seems that system library is found:
But still:
|
Ahh... I didn't notice that the problem here is not with |
Here is the full build log: build.log.txt |
I was wrong. C! now always uses its built-in boost. From your build log I see that you (or the package builder) are adding |
Adding |
But it's the Fedora flags that are in error. According to the compiler error, you cannot have
|
But Fedora flags are turning this on with |
Ok, I see. So if we are stripping out |
Because of following code
flags = flags.replace('-Wall', '').replace('-Werror', '')
, something like-Werror=format-security
becomes=format-security
.https://github.com/CauldronDevelopmentLLC/cbang/search?utf8=✓&q=-Werror&type=Code
The text was updated successfully, but these errors were encountered: