getting error in windows 64-bit

[muthunagu100]

Here are the steps that I followed:

1. Install FreeTDS for Windows
   http://sourceforge.net/projects/freetdswindows/
2. Install Python
   http://www.python.org/download/releases/2.7.3/#download
   Then,
   npm install node-gyp
   node-gyp configure --python v2.7.3

Below is the message:
gyp info it worked if it ends with ok
gyp info using node-gyp@0.10.0
gyp info using node@0.8.2 | win32 | ia32
gyp http GET http://nodejs.org/dist/v0.8.2/node-v0.8.2.tar.gz
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: connect ETIMEDOUT
gyp ERR! stack at errnoException (net.js:776:11)
gyp ERR! stack at Object.afterConnect as oncomplete
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\Users\mnagasam\AppData\Roaming\npm\node_module
s\node-gyp\bin\node-gyp.js" "configure" "--python" "v2.7.3"
gyp ERR! cwd c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor
gyp ERR! node -v v0.8.2
gyp ERR! node-gyp -v v0.10.0
gyp ERR! not ok

Not sure why it is trying to do "http://nodejs.org/dist/v0.8.2/node-v0.8.2.tar.gz"

Is it not supposed to be used in windows?
your help would be great on this!!

[muthunagu100]

Could someone throw some information on this?
Is it not doable? Should I have to look for other options?
Appreciate your help!

[Gnate]

Do you have the latest NodeJS? Also, this is an issue with node-gyp and not node-freetds.

[muthunagu100]

my node.js version is 0.8.2
So, i take it that node-freetds can be used with windows node.js applications as well. This seems to be good news. Let me know if it is otherwise.
Also, for windows node.js apps, is there any change that needs to be made with the "binding.gyp" file that you've provided?

[Gnate]

Yes, of course. You'll probably need to edit the "conditions" section. It's been a while since I've used MinGW[64]. I'm afraid that will have to be an exercise of your own ;-)

"conditions": [ [
            'OS=="linux"', {
                "libraries": [
                    "$(shell find /usr/lib -type l -name 'libsybdb.so')"
                ]
            }]
        ],

[muthunagu100]

ok, for windows, should I use "libsybdb.dll" or "libsybdb.lib"?

And, I should just mention the path, right? Do I need MinGW?
can you verify if the following is good?

"conditions": [ [
        'OS=="win"', {
            "libraries": [
                "C:\sybase\OCS-15_0\lib\libsybdb.lib"
            ]
        }]
    ],

[Gnate]

Yes, include the full path. It should be a .dll file not .lib.

Take a look at ldflags and cflags as well. For instance you may need a flag for pointing MinGW to the right library path. In this case you need to include the folder C:\sybase\OCS-15_0\lib as a source for dlls. Do so with:

 -LC:\\sybase\\OCS-15_0\\lib

or

 -Lc/sybase/OCS-15_0/lib

Notice that you did NOT escape the '' character! I think MinGW will go either way, "" or "/". Use the above library path as a starting point.

I think the rest are fine but you may need to include pthreads library from somewhere. I can't recall, but it seems that MinGW includes pthreads.

[muthunagu100]

is it enough if I just install MinGW or should I mention it anywhere?

[Gnate]

Yes, you will need to install MinGW. More specifically mingw-w64.
How else are you compiling node_freetds.cpp?

On another note, I suppose I could resolve this issue for you much later tonight if you are willing to wait.

[muthunagu100]

I am pretty new to this kind of setup.. my previous node.js library installations are through npm.. and those were straight forward.. I am primarily from the java world and would need your help on the exact list of steps to be followed to get this working..
The steps that I followed are listed below. It would be great if you could pinpoint the exact steps to get "node-freetds" setup and working in my windows-64bit. Now, I am a bit confused.. I thought "node-gyp configure/ build" should get "node-freetds" setup and working. Isn't it? Could you please list the exact steps to be followed to get this working in my windows?

1. Install FreeTDS for Windows
   http://sourceforge.net/projects/freetdswindows/
2. Install Python
   http://www.python.org/download/releases/2.7.3/#download
3. Install MinGW:
   http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/
4. Node.js installs:
   npm install -g express@3.1.0
   npm install express@3.1.0
   npm install jade@0.28.1
   npm install nodemon
   npm install -g node-gyp
   npm install node-gyp
   node-gyp configure --python v2.7.3 --msvs_version=2012 --proxy=http://myproxy/

[muthunagu100]

Can you direct me with the following steps and it would help me to take it forward:

1. should I compile "node_freetds.cpp" manually using "MinGW"? If so, after compiling, should I just leave the compiled file in the "/build" folder? Actually, I already have "binding.sln", "node-freetds.vcxproj" etc., there in "/build" folder. These are created when i executed "node-gyp configure"
2. When I run "node-gyp build", it throws an error saying "cannot open include file: 'sqldb.h'" as below:
   ..\src\node_freetds.cpp(14): fatal error C1083: Cannot open include file: 'sqld
   b.h': No such file or directory [c:\myproject\build\node-freetds.vcxproj]

Can you help me with resolving this build error?
Here is how my binding.gyp looks (I am sure there should be some more changes to be done to this binding.gyp)

{
"targets": [ {
        "target_name": "node-freetds",
        "sources": [ "src/node_freetds.cpp" ],
        'type': 'loadable_module',
        "product_extension": "node",
        "conditions": [ [
            'OS=="linux"', {
                "libraries": [
                    "$(shell find /usr/lib -type l -name 'libsybdb.so')"
                ]
            }],[
            'OS=="win"', {
                "libraries": [
                    "C:\\sybase\\OCS-15_0\\dll\\libsybdb.dll"
                ]
            }]
        ],
        "cflags": [
            "-g",
            "-D_FILE_OFFSET_BITS=64",
            "-D_LARGEFILE_SOURCE",
            "-Wall"
        ],
        "ldflags": [
            "-LC:\\sybase\\OCS-15_0\\dll",
            "-lpthread",
            "-lC:\\sybase\\OCS-15_0\\include\\sybdb.h"
        ]
    }
]
}

[muthunagu100]

any updates on this?

[Gnate]

Okay, I had a lot of updating to do before I can get to a Windows build. But while I was working through the details I noticed that you will also be needing libv8.dll and v8.h you will also need nodejs header files.

For your problem with sqldb.h - this should come from the freetds project. Perhaps you can download their stable release. I found the include file under freetds-0.91/include. You'll need to build the source to generate the dll file (again, probably using MinGW). This of course may lead to other projects that need to be built... I may have done this using Cygwin.

Likewise if you cannot find nodejs development files in dll form then you will also need to build those.

[muthunagu100]

Thanks for your inputs.
I've setup "freetds-0.91", "v8" and added their include paths to my binding.gyp; Also, i found the node.js library files under MinGW and added it's include path as well.
However, I couldn't find a way to get "libv8.dll";

Now, after recompiling, when I executed "node-gyp build --verbose", I am getting some syntax errors in "node-freetds.cpp" as below; Could you please help me fixing this?

gyp info it worked if it ends with ok
gyp verb cli [ 'node',
gyp verb cli 'C:\Users\mnagasam\AppData\Roaming\npm\node_modules\node-g
yp\bin\node-gyp.js',
gyp verb cli 'build',
gyp verb cli '--verbose' ]
gyp info using node-gyp@0.10.0
gyp info using node@0.8.2 | win32 | ia32
gyp verb command build []
gyp verb build type Release
gyp verb architecture ia32
gyp verb node dev dir C:\msys\1.0\home.node-gyp\0.8.2
gyp verb found first Solution file build/binding.sln
gyp verb could not find "msbuild.exe" in PATH - finding location in registry
gyp verb "Release" dir needed to be created? null
gyp verb copying "node.lib" for ia32 C:\msys\1.0\home.node-gyp\0.8.2\Release\no
de.lib
gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args '/nologo',
gyp info spawn args '/p:Configuration=Release;Platform=Win32' ]
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
Build started 6/20/2013 3:06:19 AM.
Project "c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\binding.sln" on nod
e 1 (default targets).
ValidateSolutionConfiguration:
Building solution configuration "Release|Win32".
Project "c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\binding.sln" (1) is
building "c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxp
roj" (2) on node 1 (default targets).
InitializeBuildStatus:
Touching "Release\obj\node-freetds\node-freetds.unsuccessfulbuild".
ClCompile:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\CL.exe /c /I"C:\ms
ys\1.0\home.node-gyp\0.8.2\src" /I"C:\msys\1.0\home.node-gyp\0.8.2\deps\uv
include" /I"C:\msys\1.0\home.node-gyp\0.8.2\deps\v8\include" /I"C:\freetds-0
.91\include" /I"C:\v8-master\include" /I"C:\msys\1.0\home.node-gyp\0.8.2\src
" /Zi /nologo /W3 /WX- /Ox /Ob2 /Oi /Ot /Oy /GL /D WIN32 /D _CRT_SECURE_NO_DE
PRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D BUILDING_V8_SHARED=1 /D BUILDING_UV_S
HARED=1 /D BUILDING_NODE_EXTENSION /D _WINDLL /GF /Gm- /MT /GS /Gy /fp:precis
e /Zc:wchar_t /Zc:forScope /GR- /Fo"Release\obj\node-freetds" /Fd"Release\o
bj\node-freetds\vc110.pdb" /Gd /TP /wd4251 /analyze- /errorReport:queue /MP .
.\src\node_freetds.cpp
node_freetds.cpp
..\src\node_freetds.cpp(141): error C2065: 'eio_req' : undeclared identifier [c
:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(141): error C2065: 'req' : undeclared identifier [c:\Us
ers\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(141): error C2448: 'waitForDataResponse' : function-sty
le initializer appears to be a function definition [c:\Users\mnagasam\Desktop\M
uthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(147): error C2065: 'eio_req' : undeclared identifier [c
:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(147): error C2065: 'req' : undeclared identifier [c:\Us
ers\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(147): error C2448: 'onDataResponse' : function-style in
itializer appears to be a function definition [c:\Users\mnagasam\Desktop\Muthu
PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(329): error C2065: 'waitForDataResponse' : undeclared i
dentifier [c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxp
roj]
..\src\node_freetds.cpp(329): error C2065: 'EIO_PRI_DEFAULT' : undeclared ident
ifier [c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(329): error C2065: 'onDataResponse' : undeclared identi
fier [c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(329): error C3861: 'eio_custom': identifier not found [
c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
Done Building Project "c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-
freetds.vcxproj" (default targets) -- FAILED.

Done Building Project "c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\bindi
ng.sln" (default targets) -- FAILED.

Build FAILED.

"c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\binding.sln" (default targe
t) (1) ->
"c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj" (defa
ult target) (2) ->
(ClCompile target) ->
..\src\node_freetds.cpp(141): error C2065: 'eio_req' : undeclared identifier
[c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(141): error C2065: 'req' : undeclared identifier [c:
Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(141): error C2448: 'waitForDataResponse' : function-s
tyle initializer appears to be a function definition [c:\Users\mnagasam\Desktop
\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(147): error C2065: 'eio_req' : undeclared identifier
[c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(147): error C2065: 'req' : undeclared identifier [c:
Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(147): error C2448: 'onDataResponse' : function-style
initializer appears to be a function definition [c:\Users\mnagasam\Desktop\Muth
u\PurgeMonitor\build\node-freetds.vcxproj]
..\src\node_freetds.cpp(329): error C2065: 'waitForDataResponse' : undeclared
identifier [c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vc
xproj]
..\src\node_freetds.cpp(329): error C2065: 'EIO_PRI_DEFAULT' : undeclared ide
ntifier [c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxpro
j]
..\src\node_freetds.cpp(329): error C2065: 'onDataResponse' : undeclared iden
tifier [c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj
]
..\src\node_freetds.cpp(329): error C3861: 'eio_custom': identifier not found
[c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor\build\node-freetds.vcxproj]

0 Warning(s)
10 Error(s)

Time Elapsed 00:00:00.68
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Users\mnagasam\AppData\Roaming\npm
\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:91:17)
gyp ERR! stack at Process._handle.onexit (child_process.js:674:10)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\Users\mnagasam\AppData\Roaming\npm\node_module
s\node-gyp\bin\node-gyp.js" "build" "--verbose"
gyp ERR! cwd c:\Users\mnagasam\Desktop\Muthu\PurgeMonitor
gyp ERR! node -v v0.8.2
gyp ERR! node-gyp -v v0.10.0
gyp ERR! not ok

[Gnate]

This looks correct to me :-) My issue at the moment is resolving eio_req. Since somewhere around nodejs 0.9.3 libev and libeio was dropped in favor of libuv. libuv needs to be implemented in this code for the new NodeJS version. An interim solution for you would be to use NodeJS 0.8.x; unless you want to supply a patch here for NodeJS > 0.8.x ?... :-) Otherwise you will have to wait for me to get some time (maybe this week) to resolve this.

[muthunagu100]

My node.js version is 0.8.2.. still getting this error.. any suggestions?