mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
04915c4f5a
test/Driver/environment.swift is trying to test that the driver can set environment variables that the frontend will use, but the only environment variables we set are ones that are blocked by OS X's "System Integrity Protection" feature when invoking a restricted binary---such as /bin/sh. We could compile a tiny app that calls getenv, but that's a bit heavy for this test. Instead, just limit it to non-OS-X hosts. test/Driver/options-interpreter.swift is testing the effect of the /user/ setting the same sensitive environment variables. In this case, we want to make sure we're calling the Swift driver directly so that we don't run afoul of the same limitations environment.swift was seeing. Fixes rdar://problem/23771412 (which is just about re-enabling these tests).
6 lines
291 B
Swift
6 lines
291 B
Swift
// UNSUPPORTED: objc_interop
|
|
// Apple's "System Integrity Protection" makes this test fail on OS X.
|
|
|
|
// RUN: %swift_driver -target x86_64-unknown-gnu-linux -L/foo/ -driver-use-frontend-path %S/Inputs/print-var.sh %s LD_LIBRARY_PATH | FileCheck %s
|
|
// CHECK: {{^/foo/:[^:]+/lib/swift/linux$}}
|