From: Volker Grabsch <vog@notjusthosting.com>
To: guile-devel@gnu.org
Subject: Re: Portability fixes for win32 cross compiling
Date: Wed, 28 Jul 2010 14:40:11 +0200 [thread overview]
Message-ID: <20100728124011.GA13196@flap> (raw)
In-Reply-To: <AANLkTikPkrgu9JC-xwu_ujoMCKYEPXb579phUXg-AY3U@mail.gmail.com>
No Itisnt <theseaisinhere@gmail.com> schrieb:
> Volker Grabsch <vog@notjusthosting.com> writes:
> > Ludovic Courtès <ludo@gnu.org> schrieb:
> >>
> >> This one is wrong: the file uses mmap(3), which is declared in
> >> <sys/mman.h> according to
> >> <http://www.opengroup.org/onlinepubs/9699919799/functions/mmap.html>.
> >>
> >> This function is missing on MinGW, though, but there’s currently no
> >> replacement in Guile. Would you like to work on it?
> >
> > Sorry, I don't think I'm able to do that.
>
> Try <http://msdn.microsoft.com/en-us/library/aa366556(VS.85).aspx> for
> Windows' mmap equivalent. You could also just write a generic
> fread/malloc equivalent, since the mmap is only for speed (I think).
Sorry, but this is really going too far. It would be a different
thing if I was actually using Guile for Windows, but I don't have
any interest in doing that.
I'm just the maintainer of Mingw-cross-env who included Guile
on the request of a user. I fixed the latest Guile release to allow
for Windows cross compiling, which resulted in two small changes.
All I wanted to do was providing those two fixes to the Guile project
so that more people would profit from them. But I noticed that the
release was quite far behind the development version of Guile, so I
decided to port-forward my patches to make them more useful to you.
Porting the first change was straight-forward, but the second part
had to be fixed at another place in the dev version. And it still
didn't work, because the dev version contained many more non-portable
places which didn't exist in the release. I ended up fixig 6 places
in total, consuming a day rather than an hour of work. Then I gave
up and just sent the patches to you, assuming they would be useful
to you nevertheless.
Please, don't count on me on fixing anything more. I already helped
out more than I originally intended to do. I'm just the wrong guy
for that task.
Greets,
Volker
--
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR
next prev parent reply other threads:[~2010-07-28 12:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 0:51 Portability fixes for win32 cross compiling Volker Grabsch
2010-04-15 14:12 ` Mike Gran
2010-04-15 20:58 ` Volker Grabsch
2010-04-21 20:22 ` Volker Grabsch
2010-05-03 9:17 ` Volker Grabsch
2010-05-03 12:31 ` Greg Troxel
2010-05-21 10:09 ` Andy Wingo
2010-05-22 13:44 ` Ludovic Courtès
2010-05-24 20:30 ` Volker Grabsch
2010-05-28 13:10 ` Ludovic Courtès
2010-05-28 14:56 ` Volker Grabsch
2010-06-08 22:01 ` Ludovic Courtès
2010-06-08 22:12 ` No Itisnt
2010-06-09 6:42 ` Andy Wingo
2010-07-28 12:40 ` Volker Grabsch [this message]
2010-05-28 13:15 ` Ludovic Courtès
2010-05-28 14:44 ` 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=20100728124011.GA13196@flap \
--to=vog@notjusthosting.com \
--cc=guile-devel@gnu.org \
/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).