<div dir="ltr"><div>I’d imagine you would have to look into <a href="https://github.com/apple/swift/pull/282">Pull Request #282</a> and <span class="" title="stdlib/public/Glibc/module.map → stdlib/public/Glibc/module.map.in">stdlib/public/Glibc/<a href="http://module.map.in">module.map.in</a>. <br></span></div><span class="" title="stdlib/public/Glibc/module.map → stdlib/public/Glibc/module.map.in">Right now they’re making it look in </span>/usr/include/sys/ rather than /usr/include/x86_64-linux-gnu/sys/. </div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 9, 2015 at 12:04 AM, Lane Schwartz via swift-users <span dir="ltr">&lt;<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I&#39;m attempting to build on Scientific Linux 7.1. I&#39;ve made good progress, but I just hit another error. The build can&#39;t find ioctl.h; it exists, just not in the location the build system is looking for it:</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">$ ls /usr/include/linux/ioctl.h<br>/usr/include/linux/ioctl.h</blockquote><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">[473/490] Compiling /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/stdlib/public/Glibc/linux/x86_64/Glibc.o<br>FAILED: cd /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/stdlib/public/Glibc &amp;&amp; /home/lanes/cmake-3.4.1-Linux-x86_64.binary_distribution/bin/cmake -E make_directory /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/stdlib/public/Glibc/linux/x86_64 &amp;&amp; /home/lanes/cmake-3.4.1-Linux-x86_64.binary_distribution/bin/cmake -E make_directory /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/./lib/swift/linux/x86_64 &amp;&amp; /home/lanes/swift/swift/utils/line-directive /home/lanes/swift/swift/stdlib/public/Glibc/Glibc.swift -- /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/./bin/swiftc -c -sdk / -target x86_64-unknown-linux-gnu -Onone -g -D INTERNAL_CHECKS_ENABLED -I /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/./lib/swift/linux/x86_64 -module-cache-path /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/./clang-module-cache -no-link-objc-runtime -autolink-force-load -module-link-name swiftGlibc -force-single-frontend-invocation -parse-as-library -emit-module -emit-module-path /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/./lib/swift/linux/x86_64/Glibc.swiftmodule -o /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/stdlib/public/Glibc/linux/x86_64/Glibc.o /home/lanes/swift/swift/stdlib/public/Glibc/Glibc.swift<br>/home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/lib/swift/glibc/module.map:187:14: error: header &#39;/usr/include/x86_64-linux-gnu/sys/ioctl.h&#39; not found<br>      header &quot;/usr/include/x86_64-linux-gnu/sys/ioctl.h&quot;<br>             ^<br>/home/lanes/swift/swift/stdlib/public/Glibc/Glibc.swift:13:19: error: could not build Objective-C module &#39;SwiftGlibc&#39;<br>@_exported import SwiftGlibc // Clang module<br>                  ^<br>[473/490] Compiling /home/lanes/swift/build/Ninja-DebugAssert/swift-linux-x86_64/stdlib/private/SwiftPrivate/linux/x86_64/SwiftPrivate.o<br>ninja: build stopped: subcommand failed.<br>./swift/utils/build-script: command terminated with a non-zero exit status 1, aborting</blockquote><div><br></div><div><br></div><div>I&#39;m assuming there should be a pretty trivial fix for this. Any suggestions would be greatly appreciated.</div><div><br></div><div>Thanks,</div><div>Lane</div><div> </div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=KlmFWKNIEcyPEGx2Wqruu-2FaM6I0anrxIOlKS1pgqec7Uy8aBo-2F19J2hYzvnZXt-2BAAlnYODbEksIeYm4i-2BEgmLtmWDbIX-2BOPRZ3muSod0KHCVRwPbcvfc0vSbCPtZUdrq98pgb2PStSeLtae7l28YsqYqSnRHeS0nQSycs4mqn1Y6iD8BP72OoosFDVq33XuDmo-2FqyTmSZ7Svc9lk4O8KIzS5UXU7eyLwyHsyAPmV2N8-3D" alt="" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important" height="1" border="0" width="1">
<br>_______________________________________________<br>
swift-users mailing list<br>
<a href="mailto:swift-users@swift.org">swift-users@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-users" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-users</a><br>
<br></blockquote></div><br></div>