Thread overview | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
June 29, 2018 Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
This doesn't appear to specifically be a Vibe issue, just noticing this error when I use eventcore from it (trying to use async). C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: SetWindowLongPtrA C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: GetWindowLongPtrA I'm using DMD 2.080 from the zip file provided on the downloads page, plus DMC (unfortunately acquiring a Visual Studio license would not be easy at my workplace, and I don't see how to use the provided DMD installer without it). As far as I can tell, this issue seems to be happening because user32.lib from the windows/lib64/mingw folder does not define these two functions. Seems to work when I build the project as 32-bit though. Wondering if someone could double-check my reasoning here. |
June 29, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Chris M. | On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote: > This doesn't appear to specifically be a Vibe issue, just noticing this error when I use eventcore from it (trying to use async). > > C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: SetWindowLongPtrA > C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: GetWindowLongPtrA > > I'm using DMD 2.080 from the zip file provided on the downloads page, plus DMC (unfortunately acquiring a Visual Studio license would not be easy at my workplace, and I don't see how to use the provided DMD installer without it). As far as I can tell, this issue seems to be happening because user32.lib from the windows/lib64/mingw folder does not define these two functions. Seems to work when I build the project as 32-bit though. Wondering if someone could double-check my reasoning here. Did you see this? https://github.com/vibe-d/vibe.d#note-for-building-on-win64 Perhaps it could be that? |
June 29, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Chris M. | On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote:
> This doesn't appear to specifically be a Vibe issue, just noticing this error when I use eventcore from it (trying to use async).
>
> C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: SetWindowLongPtrA
> C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: GetWindowLongPtrA
>
> I'm using DMD 2.080 from the zip file provided on the downloads page, plus DMC (unfortunately acquiring a Visual Studio license would not be easy at my workplace, and I don't see how to use the provided DMD installer without it). As far as I can tell, this issue seems to be happening because user32.lib from the windows/lib64/mingw folder does not define these two functions. Seems to work when I build the project as 32-bit though. Wondering if someone could double-check my reasoning here.
Are you compiling to 64bit?
Else the functions will be named GetClassLongA and SetClassLongA
|
June 29, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Timoses | On Friday, 29 June 2018 at 19:53:04 UTC, Timoses wrote: > On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote: >> This doesn't appear to specifically be a Vibe issue, just noticing this error when I use eventcore from it (trying to use async). >> >> C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: SetWindowLongPtrA >> C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: GetWindowLongPtrA >> >> I'm using DMD 2.080 from the zip file provided on the downloads page, plus DMC (unfortunately acquiring a Visual Studio license would not be easy at my workplace, and I don't see how to use the provided DMD installer without it). As far as I can tell, this issue seems to be happening because user32.lib from the windows/lib64/mingw folder does not define these two functions. Seems to work when I build the project as 32-bit though. Wondering if someone could double-check my reasoning here. > > Did you see this? > https://github.com/vibe-d/vibe.d#note-for-building-on-win64 > Perhaps it could be that? Vibe builds fine on 64bit for me and I think that's outdated. It hasn't been modified for 4 years. https://github.com/vibe-d/vibe.d/blame/master/README.md#L130 |
June 29, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Timoses | On Friday, 29 June 2018 at 19:53:04 UTC, Timoses wrote: > On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote: >> This doesn't appear to specifically be a Vibe issue, just noticing this error when I use eventcore from it (trying to use async). >> >> C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: SetWindowLongPtrA >> C:\dmd2\windows\bin\lld-link.exe: warning: eventcore.lib(sockets_101f_952.obj): undefined symbol: GetWindowLongPtrA >> >> I'm using DMD 2.080 from the zip file provided on the downloads page, plus DMC (unfortunately acquiring a Visual Studio license would not be easy at my workplace, and I don't see how to use the provided DMD installer without it). As far as I can tell, this issue seems to be happening because user32.lib from the windows/lib64/mingw folder does not define these two functions. Seems to work when I build the project as 32-bit though. Wondering if someone could double-check my reasoning here. > > Did you see this? > https://github.com/vibe-d/vibe.d#note-for-building-on-win64 > Perhaps it could be that? Unfortunately made it worse C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(win32_13b7_601.obj): undefined symbol: SetWindowLongPtrA C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(win32_13b7_601.obj): undefined symbol: GetWindowLongPtrA C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(threadedfile_1361_70d.obj): undefined symbol: open C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(threadedfile_1361_70d.obj): undefined symbol: chmod C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(threadedfile_1361_70d.obj): undefined symbol: lseek C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(threadedfile_1361_70d.obj): undefined symbol: close C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(threadedfile_1361_70d.obj): undefined symbol: read C:\dmd2\windows\bin\lld-link.exe: warning: vibe-d_core.lib(threadedfile_1361_70d.obj): undefined symbol: write |
June 29, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to bauss | On Friday, 29 June 2018 at 19:53:27 UTC, bauss wrote: > On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote: >> [...] > > Are you compiling to 64bit? > > Else the functions will be named GetClassLongA and SetClassLongA Yeah, that's what I'm targeting > Vibe builds fine on 64bit for me and I think that's outdated. It hasn't been modified for 4 years. Seems to be an issue when I import vibe.core.concurrency |
July 02, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Chris M. | On Friday, 29 June 2018 at 20:08:49 UTC, Chris M. wrote:
> On Friday, 29 June 2018 at 19:53:27 UTC, bauss wrote:
>> On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote:
>>> [...]
>>
>> Are you compiling to 64bit?
>>
>> Else the functions will be named GetClassLongA and SetClassLongA
>
> Yeah, that's what I'm targeting
>
>> Vibe builds fine on 64bit for me and I think that's outdated. It hasn't been modified for 4 years.
>
> Seems to be an issue when I import vibe.core.concurrency
Bumping this one back up
|
July 02, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Chris M. | On Monday, 2 July 2018 at 12:53:19 UTC, Chris M. wrote:
> On Friday, 29 June 2018 at 20:08:49 UTC, Chris M. wrote:
>> On Friday, 29 June 2018 at 19:53:27 UTC, bauss wrote:
>>> On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote:
>>>> [...]
>>>
>>> Are you compiling to 64bit?
>>>
>>> Else the functions will be named GetClassLongA and SetClassLongA
>>
>> Yeah, that's what I'm targeting
>>
>>> Vibe builds fine on 64bit for me and I think that's outdated. It hasn't been modified for 4 years.
>>
>> Seems to be an issue when I import vibe.core.concurrency
>
> Bumping this one back up
If I don't get around it tonight then I will tomorrow and see if I can find a solution for you or perhaps figure out what exactly goes wrong.
Kinda half important for me too to fix something like this since I have a framework relying on vibe.d
|
July 02, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Bauss | On Monday, 2 July 2018 at 17:33:20 UTC, Bauss wrote:
> On Monday, 2 July 2018 at 12:53:19 UTC, Chris M. wrote:
>> On Friday, 29 June 2018 at 20:08:49 UTC, Chris M. wrote:
>>> On Friday, 29 June 2018 at 19:53:27 UTC, bauss wrote:
>>>> On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote:
>>>>> [...]
>>>>
>>>> Are you compiling to 64bit?
>>>>
>>>> Else the functions will be named GetClassLongA and SetClassLongA
>>>
>>> Yeah, that's what I'm targeting
>>>
>>>> Vibe builds fine on 64bit for me and I think that's outdated. It hasn't been modified for 4 years.
>>>
>>> Seems to be an issue when I import vibe.core.concurrency
>>
>> Bumping this one back up
>
> If I don't get around it tonight then I will tomorrow and see if I can find a solution for you or perhaps figure out what exactly goes wrong.
>
> Kinda half important for me too to fix something like this since I have a framework relying on vibe.d
Thanks for checking, I have no idea what else to try (short of getting MS Build Tools somehow, but I unfortunately can't in my current environment so I'm stuck with DMC + DMD)
|
July 02, 2018 Re: Issues with undefined symbols when using Vibe on Windows | ||||
---|---|---|---|---|
| ||||
Posted in reply to Chris M. | On Monday, July 02, 2018 18:26:27 Chris M. via Digitalmars-d-learn wrote:
> On Monday, 2 July 2018 at 17:33:20 UTC, Bauss wrote:
> > On Monday, 2 July 2018 at 12:53:19 UTC, Chris M. wrote:
> >> On Friday, 29 June 2018 at 20:08:49 UTC, Chris M. wrote:
> >>> On Friday, 29 June 2018 at 19:53:27 UTC, bauss wrote:
> >>>> On Friday, 29 June 2018 at 19:25:42 UTC, Chris M. wrote:
> >>>>> [...]
> >>>>
> >>>> Are you compiling to 64bit?
> >>>>
> >>>> Else the functions will be named GetClassLongA and SetClassLongA
> >>>
> >>> Yeah, that's what I'm targeting
> >>>
> >>>> Vibe builds fine on 64bit for me and I think that's outdated. It hasn't been modified for 4 years.
> >>>
> >>> Seems to be an issue when I import vibe.core.concurrency
> >>
> >> Bumping this one back up
> >
> > If I don't get around it tonight then I will tomorrow and see if I can find a solution for you or perhaps figure out what exactly goes wrong.
> >
> > Kinda half important for me too to fix something like this since I have a framework relying on vibe.d
>
> Thanks for checking, I have no idea what else to try (short of getting MS Build Tools somehow, but I unfortunately can't in my current environment so I'm stuck with DMC + DMD)
How are you compiling for 64-bit without the MS toolchain?
- Jonathan M Davis
|
Copyright © 1999-2021 by the D Language Foundation