From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23765 invoked by alias); 4 Jan 2012 23:35:13 -0000 Received: (qmail 23525 invoked by uid 22791); 4 Jan 2012 23:35:12 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,TW_BF X-Spam-Check-By: sourceware.org Received: from mail-vx0-f169.google.com (HELO mail-vx0-f169.google.com) (209.85.220.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 04 Jan 2012 23:34:56 +0000 Received: by vcge1 with SMTP id e1so15543052vcg.0 for ; Wed, 04 Jan 2012 15:34:56 -0800 (PST) Received: by 10.220.157.17 with SMTP id z17mr34007012vcw.73.1325720096159; Wed, 04 Jan 2012 15:34:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.112.42 with HTTP; Wed, 4 Jan 2012 15:34:35 -0800 (PST) In-Reply-To: <38EFF2D8-1F5F-479B-A97D-48E494D11E0A@users.sf.net> References: <5FD07A30-7023-4D32-A38C-3741C88BC0F5@users.sf.net> <7AD44BCE-4C07-49AE-8DF6-334579CD8B84@users.sf.net> <38EFF2D8-1F5F-479B-A97D-48E494D11E0A@users.sf.net> From: Nathan Rajlich Date: Wed, 04 Jan 2012 23:35:00 -0000 Message-ID: Subject: Re: How to compile on Windows? To: libffi-discuss Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org X-SW-Source: 2012/txt/msg00006.txt.bz2 Well here's the full output of running the "configure" command on my Windows box: https://gist.github.com/1562838 However, here's the output of executing the make.exe from the gnuwin32 ports site: https://gist.github.com/1562844 So still stuck here. Thanks for the help so far again though! On Wed, Jan 4, 2012 at 3:22 PM, Timothy Wall wrote: > If your configure worked fine with that line, then it's quite possible th= at your "make" will work given a proper "make" program. > > Last I tried that configuration it didn't work for me, though I might hav= e gotten something else wrong. > > On Jan 4, 2012, at 6:12 PM, Nathan Rajlich wrote: > >> Hhmm, ok I guess I can try messing around with gcc/mingw first. I was >> just under the impression that building with MSVC would work from the >> example in the README: >> >> path/to/configure CC=3Dpath/to/msvcc.sh LD=3Dlink CPP=3D\"cl -nologo -EP= \" >> >> Unfortunately it doesn't say what to do past that point :p >> >> On Wed, Jan 4, 2012 at 3:07 PM, Timothy Wall wrote: >>> "configure" relies on more than just the shell; you need either msys (f= rom mingw) or cygwin. >>> >>> You should get configure/compile working with gcc/mingw before you try = it with msvc, since while libffi includes some wrapper scripts to work with= MSVC, I'm not certain they will work out of the box, so you want to make s= ure everything else is resolved first. >>> >>> >>> >>> On Jan 4, 2012, at 6:03 PM, Nathan Rajlich wrote: >>> >>>> Thanks for the quick replies guys. >>>> >>>> I am trying to use the MSVC compiler. I do have the Git Bash installed >>>> though, which is how I was able to execute the configure script. >>>> Executing 'dmake' after getting a download of it displays: >>>> >>>> dmake.exe: Error -- /bin/sh: No such file or directory >>>> >>>> Any ideas? >>>> >>>> On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall wrot= e: >>>>> Are you trying to compile with MSVC or gcc/mingw? >>>>> >>>>> Regardless of compiler, I doubt you'll be able to get "nmake" to work= on configure-generated makefiles; you'll need either cygwin or MSYS-based = make. >>>>> >>>>> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote: >>>>> >>>>>> Hello all, >>>>>> >>>>>> I am attempting to compile libffi on windows, and am having some >>>>>> trouble. I was able to figure out how to get the "configure" step to >>>>>> work by using the provided example in the README. The configure step >>>>>> completed successfully and the necessary .h and Makefiles were >>>>>> created. >>>>>> >>>>>> Now when I try to invoke 'nmake', it quits quickly with an error >>>>>> saying "Illegal '\' character in macro. Quitting." or something along >>>>>> those lines, and I'm not sure where to take it from here. >>>>>> >>>>>> Any advice would be much appreciated! Thanks in advance! >>>>> >>> >