Opened 14 months ago
Last modified 14 months ago
#68404 assigned defect
ocaml fails to build on 10.8 Intel and earlier: clang: error: linker command failed with exit code 1 (use -v to see invocation)
Reported by: | barracuda156 | Owned by: | pmetzger (Perry E. Metzger) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | mountainlion, lion, snowleopard | Cc: | |
Port: | ocaml |
Description
ld: warning: unexpected dylib (/usr/lib/libSystem.dylib) on link line 0 0x1073810e7 __assert_rtn + 144 1 0x1073ea966 ld::tool::SectionRelocationsAtom<x86>::sectSymNum(bool, ld::Atom const*) + 0 2 0x1073d8ef8 ld::tool::SectionRelocationsAtom<x86_64>::encodeSectionReloc(ld::Internal::FinalSection*, ld::tool::SectionRelocationsAtom<x86_64>::Entry const&, std::__1::vector<macho_relocation_info<Pointer64<LittleEndian> >, std::__1::allocator<macho_relocation_info<Pointer64<LittleEndian> > > >&) + 86 3 0x10740e060 ld::tool::SectionRelocationsAtom<x86_64>::encode() + 62 4 0x1073dfffe ld::tool::OutputFile::updateLINKEDITAddresses(ld::Internal&) + 454 5 0x1073dace4 ld::tool::OutputFile::write(ld::Internal&) + 138 6 0x107381d94 main + 1012 7 0x1076dc7e1 start + 0 A linker snapshot was created at: /tmp/dynlink_compilerlibs.o-2023-09-05-065212.ld-snapshot ld: Assertion failed: (_machoSection != 0), function machoSection, file /SourceCache/ld64/ld64-236.4/src/ld/ld.hpp, line 714. clang: error: linker command failed with exit code 1 (use -v to see invocation) File "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_ocaml/ocaml/work/ocaml-4.14.1/otherlibs/dynlink/native/dynlink_compilerlibs.cmx", line 1: Error: Error during partial linking
On 10.6.8 Intel clang-3.4
is picked, and it also fails: https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/173117/steps/install-port/logs/stdio
Change History (4)
comment:1 follow-up: 2 Changed 14 months ago by pmetzger (Perry E. Metzger)
comment:2 Changed 14 months ago by barracuda156
Replying to pmetzger:
As you know, I have no access to such a system (nor do I have much motivation, tbh.) If you can find patches that fix this to be conditionally included on older hardware, we will of course accept them.
I will look into this. Intel systems are not a great priority for me to be honest, but for the sake of testing I would prefer this building, of course.
comment:3 follow-up: 4 Changed 14 months ago by pmetzger (Perry E. Metzger)
I'll also say directly that I don't care much about historical versions of MacOS. I care about current users of MacPorts. If people want to spend effort keeping old stuff going that's fine, but it's not something I want to spend time on. So, if you want to get it working, fine, and if not, fine.
comment:4 Changed 14 months ago by barracuda156
Replying to pmetzger:
I'll also say directly that I don't care much about historical versions of MacOS. I care about current users of MacPorts. If people want to spend effort keeping old stuff going that's fine, but it's not something I want to spend time on. So, if you want to get it working, fine, and if not, fine.
No issues, I got your position. Why I assign a ticket is merely because you are the maintainer of OCaml and may still want to be informed. No obligation is implied whatsoever.
As you know, I have no access to such a system (nor do I have much motivation, tbh.) If you can find patches that fix this to be conditionally included on older hardware, we will of course accept them.