Displaying 3 results from an estimated 3 matches for "ppc641e".
Did you mean:
ppc64
2019 Jul 04
2
LLVM Releases
...me compiler that would work?
>
> I used gcc 4.8.5 to compile LLVM ~8.0.1-rc2 on CentOS 7 AMD64 not long ago,
> which worked ok. That was using cmake, with these specific options (in case
> that's useful):
I’ve installed it successfully on both x86 and ARM. It’s only on POWER9 (ppc641e) that it fails.
That one is not in your TARGETS_TO_BUILD list, alas.
Thanks,
Marty
>
> $ mkdir $HOME/local/source
> $ cd $HOME/local/source
> $ git clone -b release/8.x https://github.com/llvm/llvm-project <https://github.com/llvm/llvm-project>
> $ mkdir build
>...
2019 Jun 30
2
LLVM Releases
...s clang says it is version 9.0.0 (trunk 357348). I tried to do
another spack install llvm at develop, but it said that I already had it installed. Does that mean there
were no changes since March 30, or does spack not look for any changes?
I also tried spack install llvm at develop on a POWER9 (ppc641e) machine, but I can not find a compiler that
will compile it. gcc 4.8.5 is reported as too old, and gcc 7.3.0 and 8.1.0 both fail in the same place:
>> 9069 /home/msi3/hpct/spack/var/spack/stage/llvm-develop-iu3myet5ceoz4q7
k5twmk4dlths3aemz/spack-src/projects/libcxx/includ...
2019 Jul 03
2
LLVM Releases
Thank you.
> On Jul 3, 2019, at 4:04 AM, Justin Clift <justin at postgresql.org> wrote:
>
> On 2019-07-01 00:22, Marty Itzkowitz via llvm-dev wrote:
>> I also tried spack install llvm at develop on a POWER9 (ppc641e)
>> machine, but I can not find a compiler that
>> will compile it. gcc 4.8.5 is reported as too old, and gcc 7.3.0 and
>> 8.1.0 both fail in the same place:
>> >> 9069 /home/msi3/hpct/spack/var/spack/stage/llvm-develop-iu3myet5ceoz4q7
>> k5twmk4d...