-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Un-revert][Glibc] Configure modulemap for target, not host #1704
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
[Un-revert][Glibc] Configure modulemap for target, not host #1704
Conversation
foreach(SDK ${SWIFT_SDKS}) | ||
foreach(arch ${SWIFT_SDK_${SDK}_ARCHITECTURES}) | ||
# Don't generate Glibc module maps for Darwin targets. | ||
if("${SDK}" STREQUAL "LINUX" OR "${SDK}" STREQUAL "FREEBSD") |
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.
This if()
statement is the only difference between this and #1679. ☝️
@swift-ci Please test |
@gribozavr Looks like the tests passed! Is this good to merge? |
Yes, LGTM, thanks @modocache! |
[Un-revert][Glibc] Configure modulemap for target, not host
Thanks! 👋 |
This change looks like it might be causing the package job to fail: /tmp/swift-package-tests/test-multi-compile-glibc/Output/swift-multi-compile-glibc.py.tmp.dir/hello.swift:1:8: error: missing required module 'SwiftGlibc' Could you please take a look: https://ci.swift.org/view/Packages/job/oss-swift-package-linux-ubuntu-14_04/800/console |
Thanks for the heads up, @najacque. The failing jobs are using the I'm looking into why the tests are failing now. The changes in #1757 seem relevant to this discussion as well... |
@najacque I just finished a clean build of the
I wonder if maybe this problem is now fixed, perhaps thanks to #1757. I'll do a bit of bisecting. In the meantime, could you confirm:
|
DESTINATION "lib/swift/glibc") | ||
swift_install_in_component(stdlib | ||
FILES "${output_dir}/glibc.modulemap" | ||
DESTINATION "${output_dir}") |
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.
I think, this line was the problem.
${SWIFTLIB_DIR}/${SWIFT_SDK_${SDK}_LIB_SUBDIR}/${arch}
is not relevant for install destination.
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.
I just tried checking out the merge commit for this pull request, 38ceced, and running the package tests. Unfortunately, that worked as well--no test failures like the ones that appear in the CI build logs... there must be something else I've overlooking (perhaps some build artifacts from the passing build?). I'll continue looking into this, sorry for the trouble. Ideas on what might be failing would be appreciated! 🙇 |
@shahmishal can you comment on the current state of the tests? |
@najacque @modocache Build passed :) Thanks! |
Ok, thanks for looking into it! |
What's in this pull request?
This reverts commit f2154ee, which reverted 04e1cd5. The original commit needed to be reverted because of an issue in which install targets were added to OS X builds that did not target Linux. This addresses that issue by guarding all the Linux-only CMake logic with a check for the SDK being built.
/cc @gribozavr @jrose-apple
Resolved bug number: None
Before merging this pull request to apple/swift repository:
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
Validation Testing
Note: Only members of the Apple organization can trigger swift-ci.