unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Volker Grabsch <vog@notjusthosting.com>
Cc: bug-guile@gnu.org, guile-devel@gnu.org, Mike Gran <spk121@yahoo.com>
Subject: Re: Guile with win32 cross compiling
Date: Fri, 01 Apr 2011 12:38:26 +0200	[thread overview]
Message-ID: <m3hbaiuuhp.fsf@unquote.localdomain> (raw)
In-Reply-To: <20110326220651.GA8300@flap> (Volker Grabsch's message of "Sat, 26 Mar 2011 23:06:51 +0100")

On Sat 26 Mar 2011 23:06, Volker Grabsch <vog@notjusthosting.com> writes:

> The first issue is the "#include <uniconv.h>" in gen-scmconfig,
> which has already been discussed in the past and for which I
> already provided a clean, working solution. I forward-ported
> my patch to guile-2.0.0 and it seems to work. This patch is
> attached to this email, please consider applying it.

I don't know what discussion you are referring to here; best to link.

In any case, I don't understand the mechanism here, but I believe the
point was to make it so that #include <libguile.h> would not pull in
iconv headers.  gen-scmconfig looks up the value of the constants for
iconv conversion handlers, and writes them into scmconfig.h.  Your patch
undoes that.

What problem are you working around here?

> The other open issue is also a known one: the missing mmap()
> function under Windows. After some research, I found a promising
> mmap()/munmap() implementation for Windows in a free software
> project:
>
> http://code.google.com/p/flvmeta/source/browse/trunk/src/mmap.h?r=74
> http://code.google.com/p/flvmeta/source/browse/trunk/src/mmap.c?r=74
>
> Maybe this is worth integrating into guile?

You know, not only do we not rely on MAP_SHARED -- I switched it to use
PRIVATE, just now -- we didn't actually need mmap at all.  I just
changed it to use read(2) if mmap is not available, and it seems to work
fine, just a little (5-10%) slower to start up.  That should help our
unfortunate friends working on Windows :)

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-04-01 10:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 22:06 Guile with win32 cross compiling Volker Grabsch
2011-04-01 10:38 ` Andy Wingo [this message]
2011-04-01 18:50   ` Volker Grabsch
2011-04-12 11:14     ` Andy Wingo
2011-04-23 16:10       ` Volker Grabsch
2011-04-24 10:42         ` Andy Wingo
2011-05-16 23:01           ` Volker Grabsch
2011-05-20 10:32             ` Andy Wingo
2011-05-20 12:25               ` Volker Grabsch
2011-05-20 12:48                 ` Jan Nieuwenhuizen
2011-05-20 13:25                   ` Andy Wingo
2011-05-20 22:19                   ` Volker Grabsch
2011-06-17  9:03                     ` Andy Wingo
2011-07-01 13:52                       ` Andy Wingo
2011-04-24 20:22       ` Ludovic Courtès
2011-04-28 21:03         ` Andy Wingo
2011-06-19 14:42           ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2011-04-05 19:43 Mike Gran
2011-04-06  1:38 ` Volker Grabsch
2011-04-06 12:46   ` Ludovic Courtès
2011-03-26 22:04 Volker Grabsch

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3hbaiuuhp.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=spk121@yahoo.com \
    --cc=vog@notjusthosting.com \
    /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).