• Error building devel/electron42 LLVM Producer Reader mismatch

    From Leonard Rucker@len@perpetualthought.com to muc.lists.freebsd.ports on Tue Oct 27 14:33:04 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi
    I build devel/Electron42 via poudriere. Since the port was updated to
    v42.11.14 my build has been failing with the linker error.
    ld.lld: error: obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.8e755ce130c7673f-cgu.0.rcgu.o):
    Not an int attribute (Producer: 'LLVM23.1.1-rust-1.99.1-stable' Reader:
    'LLVM 22.1.8')

    Does anyone know what would cause this and how I would fix it?

    Thanks
    Len


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.ports on Tue Oct 27 18:33:17 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 10/27/26 14:33, Leonard Rucker wrote:
    Hi
    I build devel/Electron42 via poudriere. Since the port was updated to v42.11.14 my build has been failing with the linker error.
    ld.lld: error: obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.8e755ce130c7673f-cgu.0.rcgu.o):
    Not an int attribute (Producer: 'LLVM23.1.1-rust-1.99.1-stable' Reader:
    'LLVM 22.1.8')

    Does anyone know what would cause this and how I would fix it?

    I tend to associate messages with the likes of "(Producer: 'LLVM23.1.1-rust-1.99.1-stable' Reader: 'LLVM 22.1.8')" as being tied to
    the build attempting something like LTO use while using a mix of
    tools/files from distinct LLVM versions, something that is not generally supported, here:

    LLVM23.1.1-rust-1.99.1-stable files used by LLVM 22.1.8 tools.

    My understanding is that LTO (for example) does not in general have
    forward or backward compatibility. LLVM23 tools could object to some
    LLVM22 files, for example.

    You may be better off forcing the default devel/LLVM* selection, causing
    use of that default, and setting up rust to use that selection instead
    of its internal, partial LLVM toolchain. Or give up on using the likes
    of LTO, where version specific internals are exposed and used. (If that
    is what is actually going on here.)


    Thanks
    Len


    --
    ===
    Mark Millard
    marklmi at yahoo.com


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Leonard Rucker@len@perpetualthought.com to muc.lists.freebsd.ports on Wed Oct 28 18:48:53 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Tue, 27 Oct 2026 18:33:17 -0700
    Mark Millard <marklmi@yahoo.com> wrote:

    On 10/27/26 14:33, Leonard Rucker wrote:
    Hi
    I build devel/Electron42 via poudriere. Since the port was updated
    to v42.11.14 my build has been failing with the linker error.
    ld.lld: error: obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.8e755ce130c7673f-cgu.0.rcgu.o):
    Not an int attribute (Producer: 'LLVM23.1.1-rust-1.99.1-stable'
    Reader: 'LLVM 22.1.8')

    Does anyone know what would cause this and how I would fix it?

    I tend to associate messages with the likes of "(Producer: 'LLVM23.1.1-rust-1.99.1-stable' Reader: 'LLVM 22.1.8')" as being tied
    to the build attempting something like LTO use while using a mix of tools/files from distinct LLVM versions, something that is not
    generally supported, here:

    LLVM23.1.1-rust-1.99.1-stable files used by LLVM 22.1.8 tools.

    My understanding is that LTO (for example) does not in general have
    forward or backward compatibility. LLVM23 tools could object to some
    LLVM22 files, for example.

    You may be better off forcing the default devel/LLVM* selection,
    causing use of that default, and setting up rust to use that
    selection instead of its internal, partial LLVM toolchain. Or give up
    on using the likes of LTO, where version specific internals are
    exposed and used. (If that is what is actually going on here.)


    Thanks
    Len





    I had a similar though with reguards to llmv build options. I just left
    the defaults for everything except I changed all LLVM version I use to BE_FREEBSD instead of BE_STANDARD. I changed this back for all LLVM
    versions poudriere uses to no effect. I also noticed that OPTION GOLD
    is no longer present in LLVM23 so I unset this from all privious LLVM
    versions in poudriere to no avail as well.

    The thing that strikes me as odd is that the build log makes no
    mention of LLVM23 in the build-depeends phase but does mention
    both llvm19 and llvm22.

    I also took a look at my build of rust. It is built with defaults with
    the only interesting option is to use devel/llvm instead of the llvm
    bundled with rust. I didn't want to mess with this. Just was checking
    if there was anything that might show me what might be an issue.


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2