From: Timothy Wall <twall@users.sf.net>
To: Nathan Rajlich <nathan@tootallnate.net>
Cc: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: How to compile on Windows?
Date: Wed, 04 Jan 2012 23:08:00 -0000 [thread overview]
Message-ID: <7AD44BCE-4C07-49AE-8DF6-334579CD8B84@users.sf.net> (raw)
In-Reply-To: <CAN5MXocHu3im=fsCTQoLgXn6Y9a4jvzKVU9cJrhiJxf-BX1riw@mail.gmail.com>
"configure" relies on more than just the shell; you need either msys (from 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 sure 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 <twall@users.sf.net> wrote:
>> 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!
>>
next prev parent reply other threads:[~2012-01-04 23:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 22:10 Nathan Rajlich
2012-01-04 22:59 ` Timothy Wall
2012-01-04 23:03 ` Nathan Rajlich
2012-01-04 23:08 ` Timothy Wall [this message]
2012-01-04 23:13 ` Nathan Rajlich
2012-01-04 23:23 ` Timothy Wall
2012-01-04 23:35 ` Nathan Rajlich
2012-01-05 17:25 ` Nathan Rajlich
2012-01-05 17:29 ` Cauê Waneck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7AD44BCE-4C07-49AE-8DF6-334579CD8B84@users.sf.net \
--to=twall@users.sf.net \
--cc=libffi-discuss@sourceware.org \
--cc=nathan@tootallnate.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).