subject:"\[Issue 16423\] ModuleInfo missing when linking to static lib with classes"

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 Iain Buclaw changed: What|Removed |Added Priority|P1 |P4 --

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2020-01-16 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 Walter Bright changed: What|Removed |Added Keywords||objc CC|

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-12-22 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #15 from Ketmar Dark --- (just a speculation) maybe ld merges identical symbols from different libraries by default or something, and optlink doesn't. --

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-12-22 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #14 from Ketmar Dark --- i suspect optlink. sadly, i can't check with ms linker. (ketmar dreaming of getting rid of optlink and moving the defaults to mingw's binutils) --

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-12-22 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #13 from Jacob Carlborg --- (In reply to Ketmar Dark from comment #12) > funny, it doesn't cause any problems on GNU/Linux, only windows builds are > affected. It seems to work on all platforms except Windows. Might be

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-12-21 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #12 from Ketmar Dark --- funny, it doesn't cause any problems on GNU/Linux, only windows builds are affected. --

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-12-21 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #11 from Jacob Carlborg --- (In reply to Ketmar Dark from comment #10) > by the way. applying 6076 broke windows builds: phobos refused to build with > "duplicate ModuleInfo for object.d" error. Yeah, I noticed that four

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-12-21 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #10 from Ketmar Dark --- by the way. applying 6076 broke windows builds: phobos refused to build with "duplicate ModuleInfo for object.d" error. --

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-10-11 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #9 from Ketmar Dark --- (In reply to Steven Schveighoffer from comment #8) > But there may be code out there which expects Object.factory to work, and in > some cases, it will not. and there is. some of my UI

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-10-11 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #8 from Steven Schveighoffer --- Whether we need it or not, it's currently a feature of the runtime. Do we not care about existing code anymore? I'm totally in favor of deprecating Object.factory, and also in favor

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-10-10 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #7 from Martin Nowak --- (In reply to Steven Schveighoffer from comment #5) > This is penny-wise and pound-foolish. First we need to solve megabyte sized > template symbol names. Then we need full shared library support.

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-09-21 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #6 from Jacob Carlborg --- (In reply to Steven Schveighoffer from comment #5) > In fact, I actually TRY your suggestion to solve the original problem and it > doesn't work. See the PR: >

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-09-21 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 Steven Schveighoffer changed: What|Removed |Added Status|RESOLVED|REOPENED

[Issue 16423] ModuleInfo missing when linking to static lib with classes

2016-09-20 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=16423 --- Comment #4 from Martin Nowak --- Another rather obvious solution is to tell the linker to include the whole archive, sensibly named --whole-archive/--no-whole-archive for ld. Unfortunately dmd currently reorders linker flags (see