Hi John,
No, I haven't made any changes for Clang. What specific changes you think I
need to have for Clang?
One observation I have for LLVM and Clang that even though I have
installed them directly using "apt-get install" ; the build-script looks
for the SRC_ROOT/llvm and llvm/tools/clang folders. Also the build-script
runs the build on top of these folders.
I understand if we have system installed dependencies then those should be
used instead of the building it from source; please correct me if I am
wrong here.
PS: As of now I am building using -m option, the build command
is: ./utils/build-script -m -R
Thanks,
Meghali
From: John McCall
To: Meghali Dhoble
Cc: Graydon Hoare , swift-dev
Date: 09/07/2017 12:29 AM
Subject:Re: [swift-dev] Swift build on ppc64le platform
Sent by:rjmcc...@apple.com
On Sep 6, 2017, at 3:28 AM, Meghali Dhoble
wrote:
Thanks John, for the response.
We have a patch added already for ppc64 support at llvm, however
still the failures seen,
Did you change Clang?
John.
I will try to opt for 2nd option and see if that helps.
Thanks,
Meghali
John McCall ---08/28/2017 09:59:28 PM---> On Aug 28,
2017, at 9:08 AM, Meghali Dhoble via swift-dev
wrote: > Hi,
From: John McCall
To: Meghali Dhoble
Cc: swift-dev , Graydon Hoare
Date: 08/28/2017 09:59 PM
Subject: Re: [swift-dev] Swift build on ppc64le platform
Sent by: rjmcc...@apple.com
On Aug 28, 2017, at 9:08 AM, Meghali Dhoble via swift-dev
wrote:
Hi,
I have been working towards getting the swift source code
built on my power (ppc64le) platform on Ubuntu16.04 OS.
I am observing build issues and looking for some help
here. Please redirect me if this is not the right place
for these questions.
I would like to understand the pre-requisites and the
hardware configurations required to build this language.
The error I am getting look like memory issues as the
process is being killed abruptly. I am attaching the log
herewith for reference.
I don't see anything like that in the log. It looks like an ordinary
compiler error relating to our custom calling convention.
You need to either
1. implement swiftcc in LLVM's ppc64 backend and then teach Clang
that it's legal there or
2. configure Swift to not try to use it.
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.
John.
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
