From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30967 invoked by alias); 18 Feb 2015 19:28:08 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 30950 invoked by uid 89); 18 Feb 2015 19:28:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 18 Feb 2015 19:28:06 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t1IJS4jV007217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 18 Feb 2015 14:28:05 -0500 Received: from YAAKOV04.redhat.com ([10.10.116.24]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t1IJS2kr007460 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 18 Feb 2015 14:28:04 -0500 Message-ID: <1424287689.3460.19.camel@cygwin.com> Subject: Re: ffcall From: Yaakov Selkowitz To: cygwin-apps@cygwin.com Date: Wed, 18 Feb 2015 19:28:00 -0000 In-Reply-To: <54E4DEC2.2060400@cornell.edu> References: <54E4DEC2.2060400@cornell.edu> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-02/txt/msg00246.txt.bz2 On Wed, 2015-02-18 at 13:49 -0500, Ken Brown wrote: > I've been trying to adopt Reini's packages that have not yet been ported to > 64-bit Cygwin and that have some connection to packages I already maintain. The > next one on my list is ffcall. I'm guessing this is for clisp? (In Fedora, clisp is the only package which BR: ffcall). > Unfortunately, the source has a lot of assembler code in it, so I will almost > certainly need help from someone well versed in x86_64 assembly language. And > the libffcall project appears to be dead upstream, so I'm not going to get help > there. Unless you can find a patch somewhere for Win64 support. > I have no idea how hard this will be. The code has been ported to x86_64 Linux, > so there's at least a starting point. Only to a point, there are significant differences: https://sourceforge.net/p/mingw-w64/wiki2/MinGW%20x64%20Software% 20convention/ -- Yaakov