<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 28, 2015, at 7:20 PM, Joe Groff <<a href="mailto:jgroff@apple.com" class="">jgroff@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: HelveticaNeue; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I can believe LLVM and Clang only build against glibc, but that's not necessarily a problem for compiled executables.</span></div></blockquote></div><br class=""><div class="">I was attempting to build Swift on a system (specifically, Alpine) which does not have a glibc package.</div><div class=""><br class=""></div><div class="">It may very well be possible to design a cross-compile toolchain to build glibc-free Swift executables from a glibc system. That kind of question is well outside my knowledge.</div><div class=""><br class=""></div><div class="">But that particular rabbithole does not lead to a swift package for Alpine, so unfortunately, it is of small help for my motivation.</div></body></html>