Re: Unable to compile Phobos using wiki's instruction

2013-06-29 Thread Geod24

On Saturday, 29 June 2013 at 15:15:49 UTC, Andrej Mitrovic wrote:
On Saturday, 29 June 2013 at 15:15:08 UTC, Andrej Mitrovic 
wrote:
On Saturday, 29 June 2013 at 15:14:19 UTC, Andrej Mitrovic 
wrote:

On Saturday, 29 June 2013 at 15:03:05 UTC, Geod24 wrote:

Hi folks,
As I'm learning phobos, I wanted a more inside look and did 
a co of the libs + dmd.


Try getting the latest druntime from git-head, since these 
symbols were moved from phobos into druntime a few pull 
requests ago.


Also not that you're going to have to build druntime again, and
then phobos. It's because druntime will create new .di import
modules, which contain those symbols.


I meant *note*


Successfully built it after fetching the up-to-date repo, thank 
you !


Re: Unable to compile Phobos using wiki's instruction

2013-06-29 Thread Andrej Mitrovic

On Saturday, 29 June 2013 at 15:14:19 UTC, Andrej Mitrovic wrote:

On Saturday, 29 June 2013 at 15:03:05 UTC, Geod24 wrote:

Hi folks,
As I'm learning phobos, I wanted a more inside look and did a 
co of the libs + dmd.


Try getting the latest druntime from git-head, since these 
symbols were moved from phobos into druntime a few pull 
requests ago.


Also not that you're going to have to build druntime again, and
then phobos. It's because druntime will create new .di import
modules, which contain those symbols.


Re: Unable to compile Phobos using wiki's instruction

2013-06-29 Thread Andrej Mitrovic

On Saturday, 29 June 2013 at 15:15:08 UTC, Andrej Mitrovic wrote:
On Saturday, 29 June 2013 at 15:14:19 UTC, Andrej Mitrovic 
wrote:

On Saturday, 29 June 2013 at 15:03:05 UTC, Geod24 wrote:

Hi folks,
As I'm learning phobos, I wanted a more inside look and did a 
co of the libs + dmd.


Try getting the latest druntime from git-head, since these 
symbols were moved from phobos into druntime a few pull 
requests ago.


Also not that you're going to have to build druntime again, and
then phobos. It's because druntime will create new .di import
modules, which contain those symbols.


I meant *note*


Re: Unable to compile Phobos using wiki's instruction

2013-06-29 Thread Andrej Mitrovic

On Saturday, 29 June 2013 at 15:03:05 UTC, Geod24 wrote:

Hi folks,
As I'm learning phobos, I wanted a more inside look and did a 
co of the libs + dmd.


Try getting the latest druntime from git-head, since these 
symbols were moved from phobos into druntime a few pull requests 
ago.


Unable to compile Phobos using wiki's instruction

2013-06-29 Thread Geod24

Hi folks,
As I'm learning phobos, I wanted a more inside look and did a co 
of the libs + dmd.

DMD compiles fine (using dmc), as well as druntime.
But when it comes to phobos, I'm not able to compile, I get:

[...]
DMD v2.064-devel-42b668b-dirty DEBUG
std.md5 is scheduled for deprecation. Please use std.digest.md 
instead
The 'crc32' module has been scheduled for deprecation. Please use 
'std.digest.cr

c' instead.
std\process.d(490): Error: undefined identifier 
GetHandleInformation
std\process.d(491): Error: undefined identifier 
HANDLE_FLAG_INHERIT
std\process.d(493): Error: undefined identifier 
SetHandleInformation
std\process.d(494): Error: undefined identifier 
HANDLE_FLAG_INHERIT
std\process.d(495): Error: undefined identifier 
HANDLE_FLAG_INHERIT
std\process.d(512): Error: undefined identifier 
CREATE_UNICODE_ENVIRONMENT

std\process.d(1311): Error: undefined identifier TerminateProcess

--- errorlevel 1

G:\code\D\dmd2\src\phobos>

I tested on 2 computers (win7 64b).
1) I tried win32/win64, using both the built compiler (DMD 
2.064-devel) and 2.63.2 downloaded from the website. I have VS 
2010 as well as 2012 installed.
2) I tried win64, using only the devel compiler. I also tweaked 
the Makefile (Setting C:\ instead of \ for the SDK / VS path, and 
setting VS version to 11 as I only have VS2012 installed).


For the rest I stricly followed 
http://wiki.dlang.org/Building_DMD (I even have %DM_HOME% in my 
user's env).


Any help will be greatly appreciated, as I'm pretty sure I am 
missing the obvious.