Re: Cygwin on x64
Hi There, please go through the followings for the problem: 1) I want to create a 64 bit DLL using Cygwin in Windows Serever 2003 64 bit platform. 2) I am using Cygwin to run the make file 3) In the make file I have a macro “CFLAGS” where gave the option “-m64” in the make file for 64 bit build 4) But when I use this option I am getting an error like: $ make -f makefile_64 g++ -c -DWIN64 -D__int64=long long -trigraphs -I../include -IC:/Progra~1/Java/jdk1.5.0_10/include -IC:/Progra~1/Java/jdk1.5.0_10/include/win32 -mno-cygwin -m64 Abc.C -o Abc.o Abc.C:1: sorry, unimplemented: 64-bit mode not compiled in make: *** [Abc.o] Error 1 5) The main thing is that I don’t know exactly what should be the option we have to give under cygwin for building a 64 bit DLL (though I have used “-m64” option), but in Linux if you use this option, you’ll get the 64 bit .SO file!!! i tried alot but tillnow didn't get the solution. Please suggest me some alternative options if anybody have. Thanks in advance! Rajeev -- View this message in context: http://www.nabble.com/Cygwin-on-x64-tp16036454p21851105.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin on x64
rajeevs wrote: 1) I want to create a 64 bit DLL using Cygwin in Windows Serever 2003 64 bit platform. 5) The main thing is that I don’t know exactly what should be the option we have to give under cygwin for building a 64 bit DLL (though I have used “-m64” option), There is no 64-bit support in cygwin compilers. You might be interested in the mingw32-x64 project, but there's no support for that here. C and Fortran binaries are available from gfortran wiki, in addition to several other sources. Tbird is taking the clues you give and putting all your repetitive posts in the Spam folder. There are resources for studying how to pose questions effectively. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin on x64
On Thu, Feb 5, 2009 at 9:11 AM, Tim Prince timothypri...@sbcglobal.net wrote: rajeevs wrote: 1) I want to create a 64 bit DLL using Cygwin in Windows Serever 2003 64 bit platform. 5) The main thing is that I don't know exactly what should be the option we have to give under cygwin for building a 64 bit DLL (though I have used -m64 option), There is no 64-bit support in cygwin compilers. You might be interested in the mingw32-x64 project, but there's no support for that here. C and Fortran binaries are available from gfortran wiki, in addition to several other sources. Tbird is taking the clues you give and putting all your repetitive posts in the Spam folder. There are resources for studying how to pose questions effectively. http://mingw-w64.sf.net/ Download a toolchain snapshot that's hosted on cygwin, and voila.. you can build win64 binaries on cygwin :) (Note that you will be cross compiling, so use --host=x86_64-pc-mingw32 in configuring your project). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin on x64
On 3/13/08, Dave Korn [EMAIL PROTECTED] wrote: NightStrike wrote on 13 March 2008 19:20: Is cygwin for Win64 native 64-bit, or does it run in the WoW compatibility layer? The latter. There's no such thing as cygwin for Win64; the dll itself, and all the packages, exist only in bog standard 32-bit ix86 versions. Now that there's a more or less working compiler for Win64, what's required to get at the very least the cygwin dll to compile? A very quick attempt with the current compiler yields this: cc -L/home/nightstrike/cyg/build/x86_64-pc-mingw32/winsup/mingw -L/home/nightstrike/cyg/build/x86_64-pc-mingw32/winsup/w32api/lib -isystem /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include -isystem /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/w32api/include -c -DHAVE_CONFIG_H -g -O2 -I. -I../../../cygwin-snapshot-20080318-1/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic ../../../cygwin-snapshot-20080318-1/libiberty/regex.c -o regex.o In file included from ../../../cygwin-snapshot-20080318-1/libiberty/regex.c:196: /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isalnum': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:154: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:154: error: (Each undeclared identifier is reported only once /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:154: error: for each function it appears in.) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isalpha': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:155: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'iscntrl': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:156: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isdigit': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:157: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isgraph': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:158: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'islower': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:159: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isprint': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:160: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'ispunct': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:161: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isspace': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:162: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isupper': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:163: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isxdigit': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:164: error: '_impmb_cur_max_dll' undeclared (first use in this function) /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isblank': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:169: error: '_impmb_cur_max_dll' undeclared (first use in this function) make[2]: *** [regex.o] Error 1 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin on x64
On Fri, Mar 21, 2008 at 12:17:56PM -0400, NightStrike wrote: On 3/13/08, Dave Korn [EMAIL PROTECTED] wrote: NightStrike wrote on 13 March 2008 19:20: Is cygwin for Win64 native 64-bit, or does it run in the WoW compatibility layer? The latter. There's no such thing as cygwin for Win64; the dll itself, and all the packages, exist only in bog standard 32-bit ix86 versions. Now that there's a more or less working compiler for Win64, what's required to get at the very least the cygwin dll to compile? A very quick attempt with the current compiler yields this: cc -L/home/nightstrike/cyg/build/x86_64-pc-mingw32/winsup/mingw -L/home/nightstrike/cyg/build/x86_64-pc-mingw32/winsup/w32api/lib -isystem /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include -isystem /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/w32api/include -c -DHAVE_CONFIG_H -g -O2 -I. -I../../../cygwin-snapshot-20080318-1/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic ../../../cygwin-snapshot-20080318-1/libiberty/regex.c -o regex.o In file included from ../../../cygwin-snapshot-20080318-1/libiberty/regex.c:196: /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h: In function 'isalnum': /home/nightstrike/cyg/cygwin-snapshot-20080318-1/winsup/mingw/include/ctype.h:154: error: '_impmb_cur_max_dll' undeclared (first use in this function) What are you asking? Are you asking if making a true 64-bit version of cygwin1.dll just requires building the dll with a 64-bit compiler? If so, then the answer is that it is not that simple. There is quite a bit more work involved than just recompiling. 32-bit assumptions would have to be rethought throughout the cygwin and newlib sources. It is not a small job. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Cygwin on x64
Is cygwin for Win64 native 64-bit, or does it run in the WoW compatibility layer? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Cygwin on x64
NightStrike wrote on 13 March 2008 19:20: Is cygwin for Win64 native 64-bit, or does it run in the WoW compatibility layer? The latter. There's no such thing as cygwin for Win64; the dll itself, and all the packages, exist only in bog standard 32-bit ix86 versions. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygwin + vista x64
Corinna, I've been trying to figure out why cygwin isn't working properly on Vista x64. I saw the thread you posted to here: http://www.cygwin.com/ml/cygwin/2006-11/msg00595.html I see that cygwin is performing the trick outlined here: http://www.catch22.net/tuts/undoc01.asp (Search for Pass arbitrary data to a child process!) This is achieved because the child_info class is declared to have: DWORD zero[4]; // must be zeroed It appears as if this trick is no longer working under Vista x64. The question is, does this code now have to resort to using VirtualAllocEx/WriteProcessMemory, or is there a way around it? Have you been able to isolate this into a simple binary test? I am currently running on a Vista x64 system right now with VS2005 installed in case you would like me to try out anything which may be of help. -Andrew -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin + vista x64
Andrew Paprocki wrote: Corinna, I've been trying to figure out why cygwin isn't working properly on Vista x64. I saw the thread you posted to here: http://www.cygwin.com/ml/cygwin/2006-11/msg00595.html I see that cygwin is performing the trick outlined here: http://www.catch22.net/tuts/undoc01.asp (Search for Pass arbitrary data to a child process!) This is achieved because the child_info class is declared to have: DWORD zero[4]; // must be zeroed It appears as if this trick is no longer working under Vista x64. The question is, does this code now have to resort to using VirtualAllocEx/WriteProcessMemory, or is there a way around it? Have you been able to isolate this into a simple binary test? I am currently running on a Vista x64 system right now with VS2005 installed in case you would like me to try out anything which may be of help. You may be interested in this update from Corinna today: http://cygwin.com/ml/cygwin/2006-12/msg00159.html -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
