From: Volker Grabsch <vog@notjusthosting.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Andy Wingo <wingo@pobox.com>, bug-guile@gnu.org, guile-devel@gnu.org
Subject: Re: Guile with win32 cross compiling
Date: Sat, 21 May 2011 00:19:31 +0200 [thread overview]
Message-ID: <20110520221931.GB2223@flap> (raw)
In-Reply-To: <xome39k9y1tf.fsf@PC201668.asml.com>
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
---<<(())>>---
next prev parent reply other threads:[~2011-05-20 22:19 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
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 [this message]
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=20110520221931.GB2223@flap \
--to=vog@notjusthosting.com \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.org \
--cc=janneke@gnu.org \
--cc=wingo@pobox.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).