-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add required flags for using the new SwiftOnoneSupport library #266
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
Add required flags for using the new SwiftOnoneSupport library #266
Conversation
03b405a
to
5be5be5
Compare
foundation.LDFLAGS += ' -lswiftSwiftOnoneSupport ' | ||
# In the future, remove the LDFLAGS line above and enable | ||
# the optimizations. But currently, it results in a segmentation | ||
# fault on one of the tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if this causes a segfault in one of the tests and it is currently working that probably means there is an expectation failure that is not met in your library:
it is worth noting the lines below are incorrect and should not be modified at that point:
from lib/script.py:111
if Configuration.current.build_mode == Configuration.Debug:
swift_flags += "-g -Onone "
elif Configuration.current.build_mode == Configuration.Release:
swift_flags += "-O "
that modification runs just fine without your changes; can you get me the crash point by attaching lldb?
cd swift-corelibs-foundation
ninja test
LD_LIBRARY_PATH=../build/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation/:/home/phausler/Public/build/Ninja-ReleaseAssert/xctest-linux-x86_64 ../build/Ninja-ReleaseAssert/lldb-linux-x86_64/bin/lldb ../build/Ninja-ReleaseAssert/foundation-linux-x86_64/TestFoundation/TestFoundation
presuming you built as release mode in the standard layouts
@phausler Actually, I was wrong. There is no crash anymore. Looks like I fixed it on the Swift side after I tested yesterday. Which means, that we can enable |
Let me know if you want me to submit the corresponding PR or if you want to commit this one-liner yourself. |
I will change the |
OK. Should I then just remove the Release related part altogether and have only the change for LDFLAGS in Debug mode? |
Or should I remove the comment about |
as soon as the corresponding swift commit is merged I will merge this and push corrections for the release builds |
OK. Understood. I'm about to merge the Swift commit now. |
Done. |
Add required flags for using the new SwiftOnoneSupport library
With your But let's first see that everything builds fine. Once everything is fine, we can remove this if-statement. |
@phausler Thanks for your support! |
[5.3] [build-script] Remove hard-coded install prefix of /usr and pass it in instead
This is a PR related to the following PR: swiftlang/swift#1429
They should be merged in sync, otherwise foundation builds will fail after the mentioned PR is merged.