From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Volker Grabsch Newsgroups: gmane.lisp.guile.devel,gmane.lisp.guile.bugs Subject: Re: Guile with win32 cross compiling Date: Sat, 21 May 2011 00:19:31 +0200 Message-ID: <20110520221931.GB2223@flap> References: <20110326220651.GA8300@flap> <20110401185020.GC13643@flap> <20110423161003.GB20479@flap> <20110516230101.GB3311@flap> <20110520122552.GA2454@flap> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1305929986 26259 80.91.229.12 (20 May 2011 22:19:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 20 May 2011 22:19:46 +0000 (UTC) Cc: Andy Wingo , bug-guile@gnu.org, guile-devel@gnu.org To: Jan Nieuwenhuizen Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sat May 21 00:19:41 2011 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QNY2n-0005SJ-5z for guile-devel@m.gmane.org; Sat, 21 May 2011 00:19:41 +0200 Original-Received: from localhost ([::1]:44593 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNY2m-0001ZW-IZ for guile-devel@m.gmane.org; Fri, 20 May 2011 18:19:40 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:44446) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNY2i-0001Yy-DS for guile-devel@gnu.org; Fri, 20 May 2011 18:19:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QNY2g-0000ds-IC for guile-devel@gnu.org; Fri, 20 May 2011 18:19:36 -0400 Original-Received: from mail.notjusthosting.com ([78.47.75.226]:49435) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNY2g-0000dW-DT; Fri, 20 May 2011 18:19:34 -0400 Original-Received: from p5df16dc8.dip.t-dialin.net ([93.241.109.200] helo=flap) by mail.notjusthosting.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1QNY2e-0000ig-Tg; Fri, 20 May 2011 22:19:33 +0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 78.47.75.226 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:12520 gmane.lisp.guile.bugs:5595 Archived-At: Jan Nieuwenhuizen schrieb: > https://github.com/janneke/gub/blob/guile-2.0/gub/specs/guile.py > https://github.com/janneke/gub/tree/guile-2.0/patches Thanks for pointing me to this project. This looks really promising and I would be glad for learning from that. 1) The pthread issue As far as I can see, you have patched libgc to support pthreads under MinGW. You forward-ported those patches from libgc-6.8 to 7.2, so I'm wondering why those patches didn't make it into upstream (i.e. the official libgc project) during that time. Are there any issues with those patches that I should know about? Also, have you actually offered these patches to upstream? If so, what's the URL to their bug tracker, or mailing list archive, where this issue has been discussed? I haven't been able to find any such information in neither the *.py file not the patch files. 2) The struct_timespec / ipv6 / etc. issues It seems that you solve those issues using an even uglier hack than I did. I'm wondering why it is necessary to manipulate the config.cache, as providing those variables as ./configure paramters worked quite well for me. Moreover, is this a sensible thing to do anyway? Shouldn't we try to fix the configure.ac to make it more portable and to make it properly detect those MinGW things in the first place? Greets, Volker -- Volker Grabsch ---<<(())>>---