Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

> On Nov 10, 2016, at 15:16, Eric Wing wrote: > > On 11/10/16, Jordan Rose > wrote: >> >>> On Nov 10, 2016, at 13:34, Eric Wing wrote: >>> >>> On 11/9/16, Eric Wing wrote: On 11/9/16, Eric Wing wrote: > On 11/9/16, Jordan Rose wrote: >> Ah, that

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

On 11/10/16, Jordan Rose wrote: > >> On Nov 10, 2016, at 13:34, Eric Wing wrote: >> >> On 11/9/16, Eric Wing wrote: >>> On 11/9/16, Eric Wing wrote: On 11/9/16, Jordan Rose wrote: > Ah, that does help. The logic to build the Glibc module map comes from > stdlib/public/Platform/CMa

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

> On Nov 10, 2016, at 13:34, Eric Wing wrote: > > On 11/9/16, Eric Wing wrote: >> On 11/9/16, Eric Wing wrote: >>> On 11/9/16, Jordan Rose wrote: Ah, that does help. The logic to build the Glibc module map comes from stdlib/public/Platform/CMakeLists.txt, and explicitly checks for >

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

Thanks so much for getting to the bottom of this! I was getting by with hacks to get around this for a while.  I'm very glad we have a reproducible change that triggers. - Will On November 10, 2016 at 1:34:27 PM, Eric Wing via swift-dev (swift-dev@swift.org) wrote: On 11/9/16, Eric Wing wrot

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

On 11/9/16, Eric Wing wrote: > On 11/9/16, Eric Wing wrote: >> On 11/9/16, Jordan Rose wrote: >>> Ah, that does help. The logic to build the Glibc module map comes from >>> stdlib/public/Platform/CMakeLists.txt, and explicitly checks for >>> “LINUX”, >>> “FREEBSD”, “ANDROID”, and “CYGWIN”. Does

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

On 11/9/16, Eric Wing wrote: > On 11/9/16, Jordan Rose wrote: >> Ah, that does help. The logic to build the Glibc module map comes from >> stdlib/public/Platform/CMakeLists.txt, and explicitly checks for “LINUX”, >> “FREEBSD”, “ANDROID”, and “CYGWIN”. Does the Steam-Runtime build use a >> differe

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

On 11/9/16, Jordan Rose wrote: > Ah, that does help. The logic to build the Glibc module map comes from > stdlib/public/Platform/CMakeLists.txt, and explicitly checks for “LINUX”, > “FREEBSD”, “ANDROID”, and “CYGWIN”. Does the Steam-Runtime build use a > different SDK name? > > Jordan > How would

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

Ah, that does help. The logic to build the Glibc module map comes from stdlib/public/Platform/CMakeLists.txt, and explicitly checks for “LINUX”, “FREEBSD”, “ANDROID”, and “CYGWIN”. Does the Steam-Runtime build use a different SDK name? Jordan > On Nov 8, 2016, at 23:40, Eric Wing via swift-de

Re: [swift-dev] Glibc.swift: error: no such module 'SwiftGlibc'

I'm comparing the build log differences between the successful build on Ubuntu 16.10 and the failed build in Steam-Runtime. It looks like while building Swift (past llvm & clang), at step [651/720], the build logs diverge. In the successful case on Ubuntu, the command is building glibc.modulemap.