Thread overview | |||||
---|---|---|---|---|---|
|
August 13, 2012 Linker errors after updating to DMD 2.060 | ||||
---|---|---|---|---|
| ||||
Hey all, After switching to 2.060, I'm getting the following linker errors on a project of mine: Error 42: Symbol Undefined _D4core6memory2GC6extendFPvkkZk build\unittest.obj(unittest) Error 42: Symbol Undefined _D4core6memory2GC6qallocFkkZS4core6memory8BlkInfo_ build\unittest.obj(unittest) Error 42: Symbol Undefined _D4core5bitop3bsrFNaNbkZi build\unittest.obj(unittest) Error 42: Symbol Undefined _D4core6memory2GC6mallocFkkZPv build\unittest.obj(unittest) Error 42: Symbol Undefined _D3std6loader19ExeModule_GetSymbolFKPvxAyaZPv build\unittest.obj(unittest) Error 42: Symbol Undefined _D4core6memory2GC8minimizeFZv build\unittest.obj(unittest) Error 42: Symbol Undefined _D4core6memory2GC4freeFPvZv build\unittest.obj(unittest) Error 42: Symbol Undefined _D4core6memory2GC11removeRangeFxPvZv build\unittest.obj(unittest) Error 42: Symbol Undefined _D4core6memory2GC7collectFZv build\unittest.obj(unittest) Error 42: Symbol Undefined _D3std6loader14ExeModule_LoadFxAyaZPv build\unittest.obj(unittest) Error 42: Symbol Undefined _D3std6loader12__ModuleInfoZ Any idea's why it does compile but fails to link on: core.memory core.bitop std.loader (by the way the 2.059 was able to link them just fine) Code is available via github: https://github.com/DannyArends/D-coding checkout and build using > rake or > rake unittest |
August 13, 2012 Re: Linker errors after updating to DMD 2.060 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Danny Arends | Make sure you completely wipe out your old installation. Several modules were _removed_ that may be still hanging around. On top of that, ensure that you're not linking any object files from 2.059 with new object files from 2.060 (i.e. do a complete rebuild). |
August 13, 2012 Re: Linker errors after updating to DMD 2.060 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Bernard Helyer | On Monday, 13 August 2012 at 11:41:47 UTC, Bernard Helyer wrote:
> Make sure you completely wipe out your old installation.
> Several modules were _removed_ that may be still hanging
> around.
>
> On top of that, ensure that you're not linking any object
> files from 2.059 with new object files from 2.060 (i.e. do
> a complete rebuild).
Thanks...
Removing the old stuff and a fresh install did the trick
Now it compiles and links the most basic progs, and on the more complex ones I get some fixable errors ("String is not an array type")
|
Copyright © 1999-2021 by the D Language Foundation