digitalmars.D.ide - Dexed Fails to Link on x86_64 Windows
- Ruby The Roobster (9/9) Jul 22 2023 Following all of the steps for building on windows, I get the
- user1234 (4/13) Jul 24 2023 hi, you might have reached
- harakim (8/17) Jul 24 2023 I'm by no means an expert on the compiler toolchain, but if it
- harakim (6/15) Jul 24 2023 I just went through the build process with 1.33.0 and it also
- harakim (7/16) Jul 24 2023 You can see that all of the code was moved to std.logger, which
- Richard (Rikki) Andrew Cattermole (6/9) Jul 24 2023 I talked with Basile about this yesterday, it appears to be related to
- Ruby The Roobster (2/19) Jul 28 2023 I'm getting basically the same error with MSVC.
- Basile B. (4/13) Aug 10 2023 Since [those
Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.
Jul 22 2023
user1234 <user12324 12.de> On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.hi, you might have reached https://gitlab.com/basile.b/dexed/-/issues/116
Jul 24 2023
On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.I'm by no means an expert on the compiler toolchain, but if it were me, I would try upgrading to LDC 1.33 because it's low effort and a reasonable chance of success. std.experimental.logger is deprecated, so it might have been removed. ldc.dll looks like it's ldc, but that's where I might be mistaken.
Jul 24 2023
On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.I just went through the build process with 1.33.0 and it also failed: lld-link: error: undefined symbol: __declspec(dllimport) ModuleInfo for std.experimental.logger
Jul 24 2023
On Tuesday, 25 July 2023 at 06:20:37 UTC, harakim wrote:On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:You can see that all of the code was moved to std.logger, which makes sense and it was publicly imported, which seems ideal: https://github.com/dlang/phobos/blob/master/std/experimental/logger/core.d I was wondering if because the module is empty, it does not generate a ModuleInfo struct. Should the problem be solved in the library or in the calling code?``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``````lld-link: error: undefined symbol: __declspec(dllimport) ModuleInfo for std.experimental.logger```
Jul 24 2023
On 25/07/2023 6:20 PM, harakim wrote:I just went through the build process with 1.33.0 and it also failed: lld-link: error: undefined symbol: __declspec(dllimport) ModuleInfo for std.experimental.loggerI talked with Basile about this yesterday, it appears to be related to the dllimport override switch. https://gitlab.com/basile.b/dexed/-/issues/116 A fix relating to dllimport override switch has already been discussed, but not yet tested.
Jul 24 2023
On Tuesday, 25 July 2023 at 06:20:37 UTC, harakim wrote:On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:I'm getting basically the same error with MSVC.Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.I just went through the build process with 1.33.0 and it also failed: lld-link: error: undefined symbol: __declspec(dllimport) ModuleInfo for std.experimental.logger
Jul 28 2023
On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.Since [those changes](https://gitlab.com/basile.b/dexed/-/commit/052e49aa35f7c2097bd714033a5ac75dac5fe992#9d1e5b64717091f93d3582fa811 e60b73160ccf_15_13) that should ~~work~~ compile (I admit I have not tested to see if that even runs) now.
Aug 10 2023
On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Actually I will tell you a little story. Trust it or dont. So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..." It turns out that this worked... but the linker output 3000 lines of warnings..Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.Since [those changes](https://gitlab.com/basile.b/dexed/-/commit/052e49aa35f7c2097bd714033a5ac75dac5fe992#9d1e5b64717091f93d3582fa811 e60b73160ccf_15_13) that should ~~work~~ compile (I admit I have not tested to see if that even runs) now.
Aug 10 2023
On Thursday, 10 August 2023 at 22:38:06 UTC, Basile B. wrote:On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:that's why compiler warnings are bad ;)On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Actually I will tell you a little story. Trust it or dont. So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..." It turns out that this worked... but the linker output 3000 lines of warnings..Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.Since [those changes](https://gitlab.com/basile.b/dexed/-/commit/052e49aa35f7c2097bd714033a5ac75dac5fe992#9d1e5b64717091f93d3582fa811 e60b73160ccf_15_13) that should ~~work~~ compile (I admit I have not tested to see if that even runs) now.
Aug 10 2023
On Thursday, 10 August 2023 at 22:38:06 UTC, Basile B. wrote:On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:If there is a working executable, could it be placed on some location from which it can be grabed? Maybe from https://gitlab.com/basile.b/dexed?On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Actually I will tell you a little story. Trust it or dont. So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..." It turns out that this worked... but the linker output 3000 lines of warnings..Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.Since [those changes](https://gitlab.com/basile.b/dexed/-/commit/052e49aa35f7c2097bd714033a5ac75dac5fe992#9d1e5b64717091f93d3582fa811 e60b73160ccf_15_13) that should ~~work~~ compile (I admit I have not tested to see if that even runs) now.
Nov 08 2023
On Wednesday, 8 November 2023 at 08:22:16 UTC, Bienlein wrote:On Thursday, 10 August 2023 at 22:38:06 UTC, Basile B. wrote:Sorry, I meant a working executable for Windows.On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:If there is a working executable, could it be placed on some location from which it can be grabed? Maybe from https://gitlab.com/basile.b/dexed?On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Actually I will tell you a little story. Trust it or dont. So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..." It turns out that this worked... but the linker output 3000 lines of warnings..Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.Since [those changes](https://gitlab.com/basile.b/dexed/-/commit/052e49aa35f7c2097bd714033a5ac75dac5fe992#9d1e5b64717091f93d3582fa811 e60b73160ccf_15_13) that should ~~work~~ compile (I admit I have not tested to see if that even runs) now.
Nov 08 2023
On Wednesday, 8 November 2023 at 08:23:02 UTC, Bienlein wrote:On Wednesday, 8 November 2023 at 08:22:16 UTC, Bienlein wrote:On AppYewyor it is no longer available. It says: "Artifacts older than 1 month are automatically deleted. For more details see Artifacts retention policy.".On Thursday, 10 August 2023 at 22:38:06 UTC, Basile B. wrote:Sorry, I meant a working executable for Windows.On Thursday, 10 August 2023 at 10:29:13 UTC, Basile B. wrote:If there is a working executable, could it be placed on some location from which it can be grabed? Maybe from https://gitlab.com/basile.b/dexed?On Saturday, 22 July 2023 at 16:50:17 UTC, Ruby The Roobster wrote:Actually I will tell you a little story. Trust it or dont. So I was on IRC, in contact with Richard, trying to fix the problem. So it was like "if I do that that will be ok ?" which I did. But there was still many error messages...So I was a bit upset like "that still does not work..." It turns out that this worked... but the linker output 3000 lines of warnings..Following all of the steps for building on windows, I get the following linker error: ``` dexed-d.obj : error LNK2019: unresolved external symbol __imp__D3std12experimental6logger12__ModuleInfoZ referenced in function ldc.dllimport_relocation ``` I'm using LDC 1.32.0. Linker used is the Microsoft linker, not sure if that matters.Since [those changes](https://gitlab.com/basile.b/dexed/-/commit/052e49aa35f7c2097bd714033a5ac75dac5fe992#9d1e5b64717091f93d3582fa811 e60b73160ccf_15_13) that should ~~work~~ compile (I admit I have not tested to see if that even runs) now.
Nov 08 2023
On Wednesday, 8 November 2023 at 08:26:03 UTC, Bienlein wrote:On AppYewyor it is no longer available. It says: "Artifacts older than 1 month are automatically deleted. For more details see Artifacts retention policy.".I just have regenerated them : https://ci.appveyor.com/api/buildjobs/4k69nijm393122g7/artifacts/setup%2Foutput.zip
Dec 02 2023