www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Visual D fails to build after Windows updates

reply "Mike James" <foo bar.com> writes:
Hi,

After a recent Windows update cycle the Visual D projects now fail to
build - it can't find the D source files - the output from compiler is
below.

===================================================================================

OPTLINK (R) for Win32  Release 8.00.12
Copyright (C) Digital Mars 1989-2010  All rights reserved.
http://www.digitalmars.com/ctg/optlink.html
OPTLINK : Error 118: Filename Expected
Path=C:\D\dmd2\windows\bin;C:\Program Files\Microsoft
SDKs\Windows\v7.0\bin;C:\Program
Files\GTK+-Runtime-3.4.2\bin;C:\D\dmd2\windows\bin;C:\D\dm\bin;c:\MinGW\;C:\Program
Files\CVSNT\;C:\lazarus\fpc\2.4.0\bin\i386-Win32;c:\dmd2\windows\bin;c:\dm\bin;c:\opt\gtk\bin;c:\bud\bin;c:\program
files\mercurial;c:\program files\cmake\bin;c:\d\dmd2\dsss\bin;C:\D\dmd2\gtkD

^
--- errorlevel 1
Building Debug\dgen.exe failed!

====================================================================================

This has occured on 2 PCs, one Vista and one Win7 straight after recent
updates. Has this occured to anybody else and whats the fix for it?

Thanks.

Regards, Mike.
Sep 26 2012
parent reply Rainer Schuetze <r.sagitario gmx.de> writes:
On 26.09.2012 16:57, Mike James wrote:

 Hi,

 After a recent Windows update cycle the Visual D projects now fail to
 build - it can't find the D source files - the output from compiler is
 below.

 ===================================================================================


 OPTLINK (R) for Win32  Release 8.00.12
 Copyright (C) Digital Mars 1989-2010  All rights reserved.
 http://www.digitalmars.com/ctg/optlink.html
 OPTLINK : Error 118: Filename Expected
 Path=C:\D\dmd2\windows\bin;C:\Program Files\Microsoft
 SDKs\Windows\v7.0\bin;C:\Program
 Files\GTK+-Runtime-3.4.2\bin;C:\D\dmd2\windows\bin;C:\D\dm\bin;c:\MinGW\;C:\Program

 Files\CVSNT\;C:\lazarus\fpc\2.4.0\bin\i386-Win32;c:\dmd2\windows\bin;c:\dm\bin;c:\opt\gtk\bin;c:\bud\bin;c:\program

 files\mercurial;c:\program
 files\cmake\bin;c:\d\dmd2\dsss\bin;C:\D\dmd2\gtkD

 ^
 --- errorlevel 1
 Building Debug\dgen.exe failed!

 ====================================================================================


 This has occured on 2 PCs, one Vista and one Win7 straight after recent
 updates. Has this occured to anybody else and whats the fix for it?

 Thanks.

 Regards, Mike.


This is a linker problem caused by the '+' in your PATH environment 
variable:

http://d.puremagic.com/issues/show_bug.cgi?id=5860
http://d.puremagic.com/issues/show_bug.cgi?id=4831
Sep 26 2012
parent "Mike James" <foo bar.com> writes:
 "Rainer Schuetze"  wrote in message news:k3vfh2$1g0$1 digitalmars.com...

 On 26.09.2012 16:57, Mike James wrote:

 Hi,

 After a recent Windows update cycle the Visual D projects now fail to
 build - it can't find the D source files - the output from compiler is
 below.

 ===================================================================================


 OPTLINK (R) for Win32  Release 8.00.12
 Copyright (C) Digital Mars 1989-2010  All rights reserved.
 http://www.digitalmars.com/ctg/optlink.html
 OPTLINK : Error 118: Filename Expected
 Path=C:\D\dmd2\windows\bin;C:\Program Files\Microsoft
 SDKs\Windows\v7.0\bin;C:\Program
 Files\GTK+-Runtime-3.4.2\bin;C:\D\dmd2\windows\bin;C:\D\dm\bin;c:\MinGW\;C:\Program

 Files\CVSNT\;C:\lazarus\fpc\2.4.0\bin\i386-Win32;c:\dmd2\windows\bin;c:\dm\bin;c:\opt\gtk\bin;c:\bud\bin;c:\program

 files\mercurial;c:\program
 files\cmake\bin;c:\d\dmd2\dsss\bin;C:\D\dmd2\gtkD

 ^
 --- errorlevel 1
 Building Debug\dgen.exe failed!

 ====================================================================================


 This has occured on 2 PCs, one Vista and one Win7 straight after recent
 updates. Has this occured to anybody else and whats the fix for it?

 Thanks.

 Regards, Mike.


 This is a linker problem caused by the '+' in your PATH environment 
 variable:

 http://d.puremagic.com/issues/show_bug.cgi?id=5860
 http://d.puremagic.com/issues/show_bug.cgi?id=4831


Thanks. A re-install of GTK+ did the trick.

Regards, Mike.
Sep 26 2012