digitalmars.D.bugs - [Issue 18015] New: [Reg 2.075] link failure unknown  section `'
- d-bugmail puremagic.com (44/44) Nov 26 2017 https://issues.dlang.org/show_bug.cgi?id=18015
https://issues.dlang.org/show_bug.cgi?id=18015 Issue ID: 18015 Summary: [Reg 2.075] link failure unknown  section `' in group [.group] Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: regression Priority: P1 Component: dmd Assignee: nobody puremagic.com Reporter: llucenic gmail.com Pull request #6564 (indicated by digger) definitively causes a regression besides the one solved in issue 17338. This regression is valid for DMD releases since 2.075.0 thru 2.077.0 (at the time of this writing). I have a project split in dub configuration into three subpackages. When I try to build it monolithic (all source files at once) the build succeeds. But when I let the subpackages be built as libraries and linked into the final binary I get linker errors: --- Linking... /usr/bin/ld: .dub/build/library-debug-linux.posix-x86_64-dmd_2075-6DE222CFD88EDD0D48F9BB14A21E15BC/libars-engine.a(log_840_28d9.o): unknown  section `' in group [.group] /usr/bin/ld: .dub/build/library-debug-linux.posix-x86_64-dmd_2075-6DE222CFD88EDD0D48F9BB14A21E15BC/libars-engine.a(log_840_28d9.o): unknown  section `' in group [.group] .dub/build/library-debug-linux.posix-x86_64-dmd_2075-6DE222CFD88EDD0D48F9BB14A21E15BC/libars-engine.a: error adding symbols: File format not recognized collect2: error: ld returned 1 exit status Error: linker exited with status 1 dmd failed with exit code 1. --- Content of the library that is built from one of the subpackages (ars-engine) is corrupt. Utility 'nm' reports for some object files within the library the same error (see the issue title) as the linker in the later phase when building the application. The project is built on top of vibe.d, what may be somehow connected with https://ci.dlang.io/blue/organizations/jenkins/dlang-org%2Fdmd/detail/PR-6564/17/pipeline/ Will this error message be enough or do I need to provide more information on the issue? --
Nov 26 2017