Skip to content

Fix multi-arch cross-compiling #15085

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

Closed
wants to merge 3 commits into from
Closed

Fix multi-arch cross-compiling #15085

wants to merge 3 commits into from

Conversation

lanza
Copy link
Contributor

@lanza lanza commented Mar 8, 2018

This is a rebased version of #13108

Pushing here to get the logs.

zbowling and others added 3 commits March 8, 2018 00:49
On platforms without fat binaries (anything but Darwin), we now build
and install stdlibs for each arch in it's own folder. Namely
lib/swift/<platform>/<arch> instead of lib/swift/<platform>.
This is a hacky fix for an issue where build-script-impl gets the ninja
command invocations from `ninja -n -v` incorrectly. Ninja gets a few
commands, including `clang++ ... -o somelib`, which assumes incorrectly
that we're in `swift-linux-x86_64` and thus errors out on the build
process.

This change just lets ninja do the work at the cost of potentially
scrambling the lit progress bar.
@lanza lanza closed this Mar 10, 2018
@lanza lanza deleted the multi_arch branch March 10, 2018 00:42
@lanza lanza restored the multi_arch branch March 10, 2018 00:42
@lanza lanza deleted the multi_arch branch March 10, 2018 00:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants