<div dir="ltr">Hi Eric,<div><br></div><div><a href="https://bugs.swift.org/browse/SR-3219" rel="noreferrer" style="font-size:14px" target="_blank">https://bugs.swift.org/browse/<wbr>SR-3219</a><span style="font-size:14px"> has been resolved.</span></div><div><span style="font-size:14px">The current master branch still reproduce the problem? If so, </span><span style="font-size:14px">could you</span></div><div><span style="font-size:14px">open a new </span><span style="font-size:14px">SR </span><span style="font-size:14px">and share the generated </span><span style="font-size:14px">build.ninja file in the build directory?</span></div><div><span style="font-size:14px"><br></span></div><div class="gmail_extra"><br><div class="gmail_quote">2016-11-19 13:57 GMT+09:00 Eric Wing via swift-dev <span dir="ltr"><<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 11/15/16, Will Stanton <<a href="mailto:willstanton1@yahoo.com">willstanton1@yahoo.com</a>> wrote:<br>
> Hello Eric,<br>
><br>
> Wanted to share I ran into a similar/the same error message this week<br>
> rebuilding from scratch (clean build/ on AWS Linux like CentOS): the build<br>
> stops (almost certainly) because the native SwiftGlibc module isn’t<br>
> generated. It happens near the end of the Swift build, around step<br>
> 600/640ish.<br>
> I’m not sure if there is one cause, since others posting online have run<br>
> into this message over the last year seemingly for different reasons<br>
> (missing libraries?).<br>
><br>
><br>
> Anyway I was able to get past it by executing:<br>
> ninja make lib-swift-linux-x86_64-glibc.<wbr>modulemap<br>
><br>
> Re-invoking the build script gave me this:<br>
> [1/1] Generating glibc.modulemap from glibc.modulemap.gyb<br>
><br>
> And the rest of the build went on its way. Maybe it’ll work for you if<br>
> you're still seeing the problem?<br>
><br>
> I’ve filed SR-3219 <a href="https://bugs.swift.org/browse/SR-3219" rel="noreferrer" target="_blank">https://bugs.swift.org/browse/<wbr>SR-3219</a> with my build.ninja<br>
> in case it’s related to build order (alas I’m not too familiar with<br>
> everything so I don’t know when SwiftGlibc is expected).<br>
><br>
> The error I came across:<br>
> [1/51] Compiling<br>
> /home/ec2-user/swift/...b/<wbr>public/Platform/linux/x86_64/<wbr>Glibc.o<br>
> FAILED: stdlib/public/Platform/linux/<wbr>x86_64/Glibc.o<br>
> cd<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/stdlib/public/<wbr>Platform<br>
> && /home/ec2-user/swift/swift/<wbr>utils/line-directive<br>
> /home/ec2-user/swift/swift/<wbr>stdlib/public/Platform/Glibc.<wbr>swift<br>
> /home/ec2-user/swift/swift/<wbr>stdlib/public/Platform/<wbr>Platform.swift<br>
> /home/ec2-user/swift/swift/<wbr>stdlib/public/Platform/<wbr>TiocConstants.swift<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/stdlib/public/<wbr>Platform/8/tgmath.swift<br>
> --<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/./bin/swiftc<br>
> -c -sdk / -target x86_64-unknown-linux-gnu -resource-dir<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/./lib/swift<br>
> -O -D INTERNAL_CHECKS_ENABLED -I<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/./lib/swift/<wbr>linux/x86_64<br>
> -module-cache-path<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/./module-cache<br>
> -no-link-objc-runtime -autolink-force-load -module-link-name swiftGlibc<br>
> -force-single-frontend-<wbr>invocation -parse-as-library -o<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/stdlib/public/<wbr>Platform/linux/x86_64/Glibc.o<br>
> /home/ec2-user/swift/swift/<wbr>stdlib/public/Platform/Glibc.<wbr>swift<br>
> /home/ec2-user/swift/swift/<wbr>stdlib/public/Platform/<wbr>Platform.swift<br>
> /home/ec2-user/swift/swift/<wbr>stdlib/public/Platform/<wbr>TiocConstants.swift<br>
> /home/ec2-user/swift/build/<wbr>Ninja-ReleaseAssert/swift-<wbr>linux-x86_64/stdlib/public/<wbr>Platform/8/tgmath.swift<br>
> /home/ec2-user/swift/swift/<wbr>stdlib/public/Platform/Glibc.<wbr>swift:13:19: error:<br>
> no such module 'SwiftGlibc'<br>
> @_exported import SwiftGlibc // Clang module<br>
> ^<br>
><br>
><br>
><br>
> Regards,<br>
> Will Stanton<br>
><br>
>> On Nov 10, 2016, at 4:34 PM, Eric Wing via swift-dev <<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>><br>
>> wrote:<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<br>
>> completed.<br>
><br>
><br>
<br>
</div></div>Interesting...following your suggestion, also doing:<br>
<br>
ninja make lib-swift-android-armv7-glibc.<wbr>modulemap<br>
<br>
and then resuming the normal build got me through the rest of the<br>
build with CMake 3.6.3.<br>
<br>
<br>
(To your other email,<br>
Android is technically Bionic instead of Glibc, but the Swift build<br>
system is pretending they are the same. This may need to be addressed<br>
in the future...)<br>
<br>
Thanks,<br>
Eric<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
swift-dev mailing list<br>
<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-dev" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-dev</a><br>
</div></div></blockquote></div><br></div></div>