How to build LLVM as ppc64 on Leopard? error: offset in archive not a multiple of 8 (must be since member is an 64-bit object file) #29
Replies: 29 comments 35 replies
-
|
at a certain point, Apple’s ld64 was written to only build if llvm was available. That can be worked around, perhaps, with suitable effort applied. If you have time and skills, you might make progress. I believe Iain has done some of that, in his xtools repo, already. Good luck! |
Beta Was this translation helpful? Give feedback.
-
|
@kencu I thought that getting at least one old @iains Have you ever tried? To be clear, I talk about Leopard, of course. P. S. I tried building it on 10.5.8 installation where I already have complete Macports (though a mixture of universal and ppc32), using gcc7, and it still failed: So yeah, it is not that I am stuck in dependency loop, the thing genuinely fails to build. |
Beta Was this translation helpful? Give feedback.
-
It is not a question of building it - that would not be too hard. not that it's any more difficult than any other port, but it takes a lot of time. I got part way there with llvm-7 .. but I am inclined to switch to llvm-14 now, since the introduction of the AIX port will have required a solution to at least one powerpc-darwin issue. |
Beta Was this translation helpful? Give feedback.
-
@iains My immediate goal was just to take a full advantage of Leopard and build the whole Macports tree as ppc64-only.
Is the reason clear why it fails to build? It is not a frequent thing to happen, it seems. Okay, universal ppc+ppc64 is tricky, but just one arch kinda should build.
That would be fantastic. |
Beta Was this translation helpful? Give feedback.
-
|
Someone else was interested to get LLVM onto PowerPC Macs: https://discourse.llvm.org/t/want-to-add-powerpc-apple-darwin-as-target-what-is-involved/4536 @catap Notice, in relation to Rust. |
Beta Was this translation helpful? Give feedback.
-
|
Here's one reference -- perhaps you might be the one to help Iain get it fixed up: http://personal.denison.edu/~bressoud/cs281-s07/MacOSXLowLevelABI.pdf There are a bunch more here, near the bottom of the page: https://personal.denison.edu/~bressoud/cs281-s07/examples.html |
Beta Was this translation helpful? Give feedback.
-
|
@kencu I decided to try another approach and build @iains By the way, your |
Beta Was this translation helpful? Give feedback.
-
|
The first attempt failed on the following: Now trying to build without x86 and arm targets. |
Beta Was this translation helpful? Give feedback.
-
|
TBH, I am completely lost with what you are trying to achieve here. Unless you are trying to build a 64b toolchain, you do not need a 64b libLTO.dylib .. (and/or libtapi). There is merit in building a 64b ld64 (because the size of debug objects is getting silly with C++) but that is not something to try for a bootstrap-from-native-tools on 10.5 .. |
Beta Was this translation helpful? Give feedback.
-
|
He is trying to build any version of llvm with a ppc64 slice in it, to then use it to build ppc64 software on Leopard or SnowLeopard (Rosetta or PPC) with llvm. The first (of hundreds?) of bugs is here, llvm-3.4:
|
Beta Was this translation helpful? Give feedback.
-
However, that suggests that the version of |
Beta Was this translation helpful? Give feedback.
-
|
Ah -- that is your 'secret knowledge' that we mere mortals might not know :> |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, same |
Beta Was this translation helpful? Give feedback.
-
|
what version of cctools are you using? |
Beta Was this translation helpful? Give feedback.
-
|
@iains I was trying to get the whole Macports on 10.5.8 built as |
Beta Was this translation helpful? Give feedback.
-
|
You don't need llvm of any kind to build ld64-97. And we have decided before that ld64-97 is the only really solid version for PPC anyway. So -- you're done! |
Beta Was this translation helpful? Give feedback.
-
|
At least until Iain's ld64 for PPC with all his fixes makes it into MacPorts somehow. |
Beta Was this translation helpful? Give feedback.
-
|
@iains Same error with |
Beta Was this translation helpful? Give feedback.
-
|
should get you done. |
Beta Was this translation helpful? Give feedback.
-
Probably I missed this part. How do I build it without |
Beta Was this translation helpful? Give feedback.
-
|
see one line above |
Beta Was this translation helpful? Give feedback.
-
|
Tiger builds ld64-97 and has no llvm with it. |
Beta Was this translation helpful? Give feedback.
-
|
@iains I will update on cctools version in half an hour, on the way to the office with the Quad. @kencu I will try, thank you. I am sure however that at least default ld64-97 on Leopard does use llvm since it installs with +llvm33 or +llvm34. But indeed I did not try to build it without, I guess. |
Beta Was this translation helpful? Give feedback.
-
|
I would still like to know the version(s) of the tools that are failing - that helps us build up a map of what works and what doesn't. |
Beta Was this translation helpful? Give feedback.
-
|
@kencu Here is what I get: |
Beta Was this translation helpful? Give feedback.
-
|
@kencu Okay, after tweaking port file I was able to build it. Many thanks for this suggestion! (Hopefully now I can build |
Beta Was this translation helpful? Give feedback.
-
|
"build gcc-7 as ppc64" means building and note, I have NOT tried this - when I build powerpc64- I use the m32 GCC as the bootstrap. |
Beta Was this translation helpful? Give feedback.
-
|
I must say, you certainly choose the least explored paths in this project .. |
Beta Was this translation helpful? Give feedback.
-
|
@iains Could you advise me how to check version of For the linker, this one is And this one is newly installed following @kencu advice: |
Beta Was this translation helpful? Give feedback.
-
|
as -v will tell you the cctools version ( I am assuming you do not do anything crazy like installing parts from more than one into your tree :) ) |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
@iains @kencu Will it make sense if I use system ar instead of the one supplied by Macports to see if that one works for llvm? |
Beta Was this translation helpful? Give feedback.
-
|
@iains @kencu Yeah, |
Beta Was this translation helpful? Give feedback.
-
|
that's pretty much expected with LLVM - try building with at least O1 and no debug (you might be lucky) - but the reason I went to all the trouble to do xtools, was because of issues with building llvm with native tools. |
Beta Was this translation helpful? Give feedback.
-
|
SO .. if you are doing a bootstrap: make -jNN STAGE1_CFLAGS="-mdynamic-no-pic -O1 -pipe" STAGE1_CXXFLAGS="-mdynamic-no-pic -O1 -pipe" ..... CC=gcc-4.2 -m64 .. etc |
Beta Was this translation helpful? Give feedback.
-
|
@iains Here is the output: I will reboot into another installation of 10.5.8 to make sure everything matches. But yeah, tools should be from Xcode 3.1.4 + whatever Macports installs normally. This installation does not even have custom Port repo. |
Beta Was this translation helpful? Give feedback.
-
|
not sure I understand what you are saying. are you saying that the Xcode-3.1.4 ar cannot build 64b archives correctly? that seems highly improbable, given that ppc64 was a supported arch for Xcode-3.1.4 and macOS 10.5 |
Beta Was this translation helpful? Give feedback.
-
@iains I am certainly not in a position to make any claims on this (I mean I just don't know). However ranlib that Macports uses is from its own cctools and not Xcode 3.1.4. @kencu should know this better. |
Beta Was this translation helpful? Give feedback.
-
|
please always use identifiable tools - it is essentially impossible to know what the issue is with something with no serial number
|
Beta Was this translation helpful? Give feedback.
-
@iains By the way how can I use system libtool instead of ar correctly? |
Beta Was this translation helpful? Give feedback.
-
|
just make sure that /usr/bin is in your PATH before /opt/local/bin .. |
Beta Was this translation helpful? Give feedback.
-
|
I sense an upcoming total purge of all of @barracuda156 's toolchains, and a likely starting over with incredible rigor about what is and what is not, exactly, installed and exactly where it is or is not installed. You learn this after the first hot bath in this stuff :> At least -- I did! |
Beta Was this translation helpful? Give feedback.
-
|
@iains System Macports tools give this: |
Beta Was this translation helpful? Give feedback.
-
|
@kencu @iains There is some problem with Compare with the |
Beta Was this translation helpful? Give feedback.
-
|
my advice is - start out with the Xcode-3.1.4 tools + gcc-4.2 (which is part of those anyway) and I think you should be able to build powerpc64-apple-darwin9 from the gcc-7 branch (although TBH, it would make sense to wait for a back port of the various fixes, including the 64b code-gen one). It depends entirely on your overall objective. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
so that Works For ME™ The reason that xtools takes so long to release a new version - is because validating a toolset is a huge task (especially if one is not a rich multi-national corporation with many employees) that is one reason that I always test GCC using an Apple-released toolchain (even if I might test with other tools) |
Beta Was this translation helpful? Give feedback.
-
Outside Macports I have your gcc10 and gcc11 which do build on 10.5.8 for ppc+ppc64. |
Beta Was this translation helpful? Give feedback.
-
|
yes. review feedback suggested a change - and the two patches need to be combined before the backports are done. (it does not matter too much for your unofficial testing - but it does matter for the backports that will be committed). |
Beta Was this translation helpful? Give feedback.
-
|
By the way does this imply that ppc64 is simply broken with "Note 2: Code generation supported for 32-bit ABI only" |
Beta Was this translation helpful? Give feedback.
-
|
Let us be 100% clear. There is NO working publicly released LLVM based compiler for powerpc-darwin. It is possible, of course, that there was internal work at Apple - but the released llvm-gcc-4.2 powerpc compiler simply calls GCC from the driver. My LLVM-7 branch has a working MC layer, which means that it is capable of building an assembler (and other binary tools, including dsymutil) for ppc and ppc64. That is the extent of it - you might be able to build LLVM/clang-xx on powerpc{,64}-darwin9, but you cannot expect it to generate code that matches the system ABI .. so it is of very limited use (perhaps for cross-compiling to X86). |
Beta Was this translation helpful? Give feedback.
-
|
So the ranlib issue kinda sorted, it looks that specific failure happens in |
Beta Was this translation helpful? Give feedback.
-
|
I would remove --enable-host-shared from the configure options and forget JIT for now. |
Beta Was this translation helpful? Give feedback.
-
@iains I have actually did that, however apparently config got ignored for w/e reason. What am I missing? |
Beta Was this translation helpful? Give feedback.
-
|
Ok, just to update: The only problem is that they cannot be built with
|
Beta Was this translation helpful? Give feedback.
-
Without patches to the MC layer none of this actually "works" .. it might build and it might produce object files - but the relocations and other details are not correct .. .. there are test cases for the relocations etc. in the llvm-7.1.1. branch; I would not expect them to pass on the 3.7 and 3.8 branches. |
Beta Was this translation helpful? Give feedback.
-
|
@iains I just noticed that the original patch was from you, and you seem to imply It looked odd that |
Beta Was this translation helpful? Give feedback.
-
|
The llvm-7.1.1 branch contains fixes for the interaction between command line, triple and .machine (it should DTRT for ppc64 as well). The whole system of triples, driver and backend needs to cooperate on understanding this .. ppc-xxxx-xxx => generate mach-o files with a CPUTYPE = ppc and a sub-type as determined by the command line / .machine directives. ppc64-xxx-xxx ==> generate mach-o files with a CPUTYPE - ppc64 and a sub-type "all" AFAIR, ppc7400 is not forced - but it is made the default for ppc-xxxxx-xxxxx NOTE: the funny thing is that ppc970 is not a valid sub-type for a ppc64 file .. which is odd given that 970 is a 64b implementation .. but that's history for you ;) |
Beta Was this translation helpful? Give feedback.
-
|
@iains What Macports has is this patch: https://github.com/macports/macports-ports/blob/master/lang/llvm-3.4/files/0004-Set-the-Mach-O-CPU-Subtype-to-ppc7400-when-targeting.patch
Your |
Beta Was this translation helpful? Give feedback.
-
|
let's be clear about what works and does not work.
^^^ This is, in fact, useful since it provides an up to date assembler and dsymutil tool that works with ppc/ppc64 on powerpc-darwin9.
The sequence that I am working on is:
I am sorry that xtools-0.7.0 is not quite ready yet [let's see if we can push that on during September] .. (the llvm-11.x work is also unpublished so far). It's not clear to me that the effort of back porting all the fixes from LLVM-7.x / 11.x to LLVM-3.4 would be useful just to save steps 1-3 (because probably you'd be building something newer right away anyway). |
Beta Was this translation helpful? Give feedback.
-
I tried once again to set the whole of Macports on Leopard as
ppc64(dropping+universal, since that is hopelessly broken), however one obstacle remains: llvm-3.3 and llvm-3.4 fail to build as ppc64: https://trac.macports.org/ticket/64760The failure is identical for either:
The problem is that
llvmis needed forld64, which in turn is needed forgcc7. (And usingld64_xcodevariant of linker fails to buildgcc7, I tried.)Beta Was this translation helpful? Give feedback.
All reactions