<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Thanks so much for getting to the bottom of this!</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I was getting by with hacks to get around this for a while. I'm very glad we have a reproducible change that triggers.</div> <br> <div class="bloop_sign" id="bloop_sign_1478816321762038016"><div style="font-family:helvetica,arial;font-size:13px">- Will</div></div> <br><p class="airmail_on">On November 10, 2016 at 1:34:27 PM, Eric Wing via swift-dev (<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>On 11/9/16, Eric Wing <ewmailing@gmail.com> wrote:<br>> On 11/9/16, Eric Wing <ewmailing@gmail.com> wrote:<br>>> On 11/9/16, Jordan Rose <jordan_rose@apple.com> wrote:<br>>>> Ah, that does help. The logic to build the Glibc module map comes from<br>>>> stdlib/public/Platform/CMakeLists.txt, and explicitly checks for<br>>>> “LINUX”,<br>>>> “FREEBSD”, “ANDROID”, and “CYGWIN”. Does the Steam-Runtime build use a<br>>>> different SDK name?<br>>>><br>>>> Jordan<br>>>><br>>><br>>> How would I verify/debug this for sure? I haven't been setting<br>>> anything differently when I build under Steam-Runtime vs. Ubuntu. (And<br>>> I have gotten through a pure Linux (no Android) build under<br>>> Steam-Runtime successfully.) Steam-Runtime is just a Linux. (It is<br>>> originally derived from Ubuntu 12.04LTS, though it probably has all<br>>> its Ubuntu identifiers stripped/replaced.)<br>>><br>>><br>>> I checked the CMakeCache.txt in<br>>> build/Ninja-ReleaseAssert/swift-linux-x86_64<br>>><br>>> Both files are identical between the Steam-Runtime and Ubuntu versions<br>>> when building for Android. The variable SWIFT_SDKS is:<br>>> SWIFT_SDKS:STRING=ANDROID;LINUX<br>>><br>>><br>>> Obviously something is different somewhere since it seems to be<br>>> skipping the glibc.modulemap in the Steam-Runtime case.<br>>><br>>><br>>> Thanks,<br>>> Eric<br>>><br>><br>> Oops. Correction to my last post. The CMakeCache.txt are not<br>> identical. I compared the wrong files.<br>><br>> However, the SWIFT_SDKS variable are the same in each.<br>><br>> Here are some differences I did spot:<br>><br>> In Ubuntu, LIBXML2_XMLLINT_EXECUABLE is not found, but defined in my<br>> SteamRT cache.<br>><br>> Ubuntu:<br>> SWIFT_HAVE_WORKING_STD_REGEX_TEST:INTERNAL=1<br>> Steam<br>> SWIFT_HAVE_WORKING_STD_REGEX_TEST:INTERNAL=<br>><br>> Ubuntu:<br>> SWIFT_HAVE_WORKING_STD_REGEX_TEST_EXITCODE:INTERNAL=0<br>> Steam:<br>> SWIFT_HAVE_WORKING_STD_REGEX_TEST_EXITCODE:INTERNAL=FAILED_TO_RUN<br>><br>><br>> The remaining of the differences are tool version differences and<br>> stuff with libICU (because Steam-Runtime doesn't supply it so I must<br>> build/supply it myself). But most of these differences are expected.<br>><br>> Thanks,<br>> Eric<br>><br><br><br>It looks like the problem is related to which version of CMake you use.<br><br>Ubuntu 16.10 supplies CMake 3.5.2.<br>Steam-Runtime ships a version that is way too old, so I built and used<br>the latest stable CMake version, 3.6.3.<br><br>Using 3.6.3 seems to always trigger this problem with the Swift build.<br><br>I tested it both ways:<br><br>1. I changed Ubuntu 16.10 to use CMake 3.6.3 and the build broke in<br>exactly the same way I described.<br><br>2. In Steam-Runtime, I built/used CMake 3.5.2 instead, and the build completed.<br><br><br>I still don’t know specifically what the build script bug is. This is<br>going to need to be fixed eventually if all newer versions of CMake<br>lead to a broken build process.<br><br>Thanks,<br>Eric<br>_______________________________________________<br>swift-dev mailing list<br>swift-dev@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-dev<br></div></div></span></blockquote></body></html>