<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=""><div><blockquote type="cite" class=""><div class="">On Aug 28, 2017, at 9:08 AM, Meghali Dhoble via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><div class=""><div class=""><p class=""><font size="2" class="">Hi, </font><br class=""><font size="2" class="">I have been working towards getting the swift source code built on my power (ppc64le) platform on Ubuntu16.04 OS. </font><br class=""><font size="2" class="">I am observing build issues and looking for some help here. Please redirect me if this is not the right place for these questions.</font><br class=""><br class=""><font size="2" class="">I would like to understand the pre-requisites and the hardware configurations required to build this language. </font><br class=""><font size="2" class="">The error I am getting look like memory issues as the process is being killed abruptly. I am attaching the log herewith for reference. </font><br class=""></p></div></div></blockquote><div>I don't see anything like that in the log. It looks like an ordinary compiler error relating to our custom calling convention.</div><div><br class=""></div><div>You need to either</div><div>1. implement swiftcc in LLVM's ppc64 backend and then teach Clang that it's legal there or</div><div>2. configure Swift to not try to use it.</div><div><br class=""></div><div>In the short term, I suspect that (2) is the right approach. Graydon was at least thinking about doing some work recently that would be aimed at making it easier to do this kind of configuration; CC'ing him explicitly to see if there's been progress there.</div><div><br class=""></div><div>John.</div></div></body></html>