Jump to page: 1 2
Thread overview
Dexed Fails to Link on x86_64 Windows
Jul 24
user1234
Jul 25
harakim
Jul 25
harakim
Jul 25
harakim
Aug 10
Basile B.
Aug 10
Basile B.
Aug 10
Basile B.
Nov 08
Bienlein
Nov 08
Bienlein
Nov 08
Bienlein
Dec 02
Basile B.
July 22

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.

July 24

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

July 25

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.

July 25

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

July 25

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:

>
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

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?

July 25
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.logger

I 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.
July 28

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:

>

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

I'm getting basically the same error with MSVC.

August 10

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 that should work compile (I admit I have not tested to see if that even runs) now.

August 10

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:

>

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 that should work compile (I admit I have not tested to see if that even runs) now.

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..

August 10

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:

>

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 that should work compile (I admit I have not tested to see if that even runs) now.

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..

that's why compiler warnings are bad ;)

« First   ‹ Prev
1 2