From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Volker Grabsch Newsgroups: gmane.lisp.guile.bugs,gmane.lisp.guile.devel Subject: Re: Portability fixes for win32 cross compiling Date: Fri, 28 May 2010 16:44:28 +0200 Message-ID: <20100528144428.GC24983@flap> References: <20100415005116.GB28615@flap> <87bpc0f9re.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1275057890 17215 80.91.229.12 (28 May 2010 14:44:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 28 May 2010 14:44:50 +0000 (UTC) Cc: bug-guile@gnu.org, guile-devel@gnu.org To: Ludovic =?iso-8859-1?Q?Court=E8s?= Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Fri May 28 16:44:49 2010 connect(): No such file or directory Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OI0no-0002C4-Jc for guile-bugs@m.gmane.org; Fri, 28 May 2010 16:44:48 +0200 Original-Received: from localhost ([127.0.0.1]:40898 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OI0no-000563-0P for guile-bugs@m.gmane.org; Fri, 28 May 2010 10:44:48 -0400 Original-Received: from [140.186.70.92] (port=52841 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OI0ne-0004zu-IL for bug-guile@gnu.org; Fri, 28 May 2010 10:44:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OI0nd-0003vr-FM for bug-guile@gnu.org; Fri, 28 May 2010 10:44:38 -0400 Original-Received: from mail.notjusthosting.com ([78.47.75.226]:34891) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OI0nX-0003tA-ER; Fri, 28 May 2010 10:44:31 -0400 Original-Received: from pd95895f3.dip.t-dialin.net ([217.88.149.243] helo=flap.v.notjusthosting.com) by mail.notjusthosting.com with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1OI0nV-0003va-Kt; Fri, 28 May 2010 14:44:29 +0000 Original-Received: from vog by flap.v.notjusthosting.com with local (Exim 4.63) (envelope-from ) id 1OI0nU-0002cV-4I; Fri, 28 May 2010 16:44:28 +0200 Content-Disposition: inline In-Reply-To: <87bpc0f9re.fsf@gnu.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.bugs:4609 gmane.lisp.guile.devel:10391 Archived-At: Ludovic Courtès schrieb: > Volker Grabsch writes: > > > The "gen-scmconfig" script includes a mix of native and > > cross headers, which goes horribly wrong when performing > > win32 cross compiling. > > What happens exactly? I don't think that the exact error messages are relevant here (some conflicting definitions of various symbols and types, resulting in various compiling errors), because this is a general thing: You can't expect such a mix of headers to work properly. More concretely, when building "gen-scmconfig" with the native compiler, you can only expect the native headers to be available, not the cross headers. Well, the cross headers _are_ available, but only because you add their include paths via "-I", which is certainly not a sensible thing to do: You force the native compiler to include headers written to be used by the cross compiler. You simply can't expect that to work. Don't #include cross headers in a native build. > > Is it really necessary to #include > > the "uniconv.h" from the cross system and to provide corresponding > > SCM_ICONVEH_* constants? > > The idea is to avoid including libunistring headers in public Guile > headers, so that the dependency on libunistring isn’t visible from the > outside. > > Perhaps we could extract the values in some other way, but I’d like to > make sure I understand the problem before attempting something. I hope my explainations above help to make the issues more clear. BTW, you can easily reproduce the issues by installing "Mingw-cross-env" on your system, if you like. http://mingw-cross-env.nongnu.org/#tutorial Greets, Volker -- Volker Grabsch ---<<(())>>--- Administrator NotJustHosting GbR