[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Portability fixes for win32 cross compiling

From: Volker Grabsch
Subject: Portability fixes for win32 cross compiling
Date: Thu, 15 Apr 2010 02:51:16 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Dear Guile developers,

I recently added support for your great guile library to
the mingw-cross-env project. In order to make this work,
I had to perform some portability fixes.

I originally created the fixes for the latest stable version
(guile 1.8.7), but I ported them forward to your current
development version. See the attached patches.
(generated with "git format-patch origin/master..HEAD")

Note that this doesn't solve all issues. I wasn't able to
forward-port my corrections to libguile/__scm.h regarding
win32 cross compiling of a _static_ libguile. Well, I could
provide something, but I'm unable to test it, because I'm
stuck with another problem introduced in 1.9.x:

The "gen-scmconfig" script includes a mix of native and
cross headers, which goes horribly wrong when performing
win32 cross compiling. Is it really necessary to #include
the "uniconv.h" from the cross system and to provide corresponding
SCM_ICONVEH_* constants?

Another note, regarding my patch for the "pthread_att_get_stack"
check: I assumed that when in doubt (i.e. when cross-compiling),
it is safe to set "works=no". However, I'm not sure about
that. Maybe this feature is so common that one should assume
"works=yes" when cross-compiling.



Volker Grabsch
NotJustHosting GbR

Attachment: 0001-add-pdcurses-to-the-list-of-termlibs.patch
Description: Text Data

Attachment: 0002-don-t-run-the-pthread_att_get_stack-check-when-cross.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]