Issue persists with DMD2.018.
Should I file this as a bug (?), or is anybody willing check this on a
multicore machine and take care of it???
A. Jung Wrote:
> So its LINK.exe!
Sorry, fingertrouble. Its definitly DMD.exe. Following happens when doing a
fresh install of the entire DMD2.017 package and then replacing DMD.exe with
the one from 2.016:
"D:\test2>batmake
D:\test2>dmd.exe -g -debug-IC:\dmd\src\phobos -c hello.d
-ofob
Now DMD2.017 with LINK2.016:
"D:\test2>batmake
D:\test2>dmd --help
Digital Mars D Compiler v2.027
[...]
D:\test2>link -H
OPTLINK (R) for Win32 Release 8.00.1
[...]
D:\test2>dmd.exe -g -debug-IC:\dmd\src\phobos -c hello.d
-ofobj\debug\hello.obj
D:\test2>echo 0
0
D:\test2>dmd.exe bin\
Unknown W. Brackets Wrote:
> Try it from the command line.
DMD 2.016:
D:\test2>batmake
D:\test2>dmd.exe -g -debug-IC:\dmd\src\phobos -c hello.d
-ofobj\debug\hello.obj
D:\test2>echo 0
0
D:\test2>dmd.exe bin\debug\test2.exe obj\debug\hello.obj phobos.lib
D:\test2>echo 0
0"
DMD 2.017:
"
Well, for me it works. I do use the error level in some scripts I've
written, and it outputs 0 when linking. I'm not linking in the lib
file, though.
Try it from the command line. I know you want it to work in the IDE,
but the first step is to determine whose bug it is. From the command
l
For confirmation: same input, but DMD 2.016:
"-- Build: debug in test2 ---
dmd.exe -g -debug-IC:\dmd\src\phobos -c hello.d -ofobj\debug\hello.obj
dmd.exe bin\debug\test2.exe obj\debug\hello.obj phobos.lib
Output size is 96.53 KB
Process terminated with status 0 (
Frits van Bommel Wrote:
> Shouldn't that be "dmd.exe -ofbin\debug\test2.exe ..."?
Plausible, but OTOH optlink recognizes the type of the file by looking at the
file extension, e.g. .exe -> out file???
Anyway, I don't have a choice, as codeblocks doesn't allow me to customize the
command line ar
A. Jung wrote:
After further research, I'm still convinced that this is a bug in DMD.
In your example above, you used "link.exe" to link the obj files into the final exe.
Codeblocks, however, uses "dmd.exe" to link the obj files.
This is valid and the preferred way according to the DMD docs: "L
After further research, I'm still convinced that this is a bug in DMD.
In your example above, you used "link.exe" to link the obj files into the final
exe. Codeblocks, however, uses "dmd.exe" to link the obj files.
This is valid and the preferred way according to the DMD docs: "Linking is done
d
A. Jung Wrote:
> OK, now it looks like a configuration error of the Codeblocks IDE which
> happenend during the transition to the new D compiler directory structure.
> Still investigating...
>
I keep old directory structure.
OK, now it looks like a configuration error of the Codeblocks IDE which
happenend during the transition to the new D compiler directory structure.
Still investigating...
Thanks so far.
Kagamin Wrote:
> A. Jung Wrote:
>
> > Since DMD 2.017, DMD returns -1073741819, despite linking was success
A. Jung Wrote:
> Since DMD 2.017, DMD returns -1073741819, despite linking was successful with
> an output exe successfully generated:
>
> "Linking executable: bin\debug\test.exe
> Process terminated with status -1073741819 (0 minutes, 3 seconds)
> 0 errors, 0 warnings"
>
c:\dev\d\win>\dev\dmd\
12 matches
Mail list logo
