-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Bug in _use_lto_suffix logic #74
Comments
I set such a value:
It correctly added the suffix -lto
It also set the config correctly:
With another value, like:
Suffix lto is not added.
The compilation also fails:
|
Can you try an empty |
Here's the problem. Yes, you're right - I'll get right on it. |
Signed-off-by: Piotr Gorski <[email protected]>
Could you try now? |
And results:
Full lto is setting properly:
|
Works for me! |
In this case, if you find the solution working, the thread can be closed. Now admittedly, when selecting another value that we did not anticipate will add suffix -lto (but with the earlier solution it was exactly the same):
However, the compilation will not succeed anyway:
@xuanruiqi So I guess it can be considered that everything works as it should? |
Signed-off-by: Piotr Gorski <[email protected]>
@xuanruiqi I tried to do it another way.
and here we go:
and
Could you confirm? |
Looks good & works for me |
Great. Thanks again for your report. |
There is this logic in the PKGBUILD:
This is apparently not correct. There should be parens around the or expression, otherwise the expression will always evaluate as true as long as
$_use_llvm_lto
is "thin".The text was updated successfully, but these errors were encountered: