| 1 |
On 03-07-2018 19:31:11 +0200, Michael Weiser wrote: |
| 2 |
> Hi Fabian, |
| 3 |
> |
| 4 |
> On Fri, Jun 29, 2018 at 03:18:58PM +0200, Fabian Groffen wrote: |
| 5 |
> |
| 6 |
> > > Did you try to compile clang with it? |
| 7 |
> > IIRC clang-3.5.1 can be built, but it can't compile a newer clang. |
| 8 |
> |
| 9 |
> I also once spent quite some time on this and found that ld64 mislinked |
| 10 |
> clang. I think I was trying 3.4.2 at the time and the resulting binary |
| 11 |
> was bus-erroring. |
| 12 |
> |
| 13 |
> That was the reason I added PPC support back into newer versions of ld64 |
| 14 |
> in the hope that the cause of the mislinkage had been fixed |
| 15 |
> incidentally somehow. But that was not the case. (The newer ld64 linked |
| 16 |
> no worse either, though. :) |
| 17 |
|
| 18 |
Indeed, 6.3 (version that can be compiled without issues lacking clang) |
| 19 |
works very well, and is able to compile @system. |
| 20 |
|
| 21 |
> A workaround I found was to link the mislinked library (one of the |
| 22 |
> zillon libLLVM*.dylibs) incrementally. I'm not quite sure any more how I |
| 23 |
> did that exactly but it produced a working clang. |
| 24 |
|
| 25 |
Hmm, I wonder if it being a 32-bits linker is part of the problem then. |
| 26 |
|
| 27 |
For now I deferred clang/llvm, compiler-rt lacks powerpc support last I |
| 28 |
checked. |
| 29 |
|
| 30 |
Fabian |
| 31 |
|
| 32 |
-- |
| 33 |
Fabian Groffen |
| 34 |
Gentoo on a different level |
Archives