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: '_imp____mb_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/
