From: Neil Jerram <neil@ossau.uklinux.net>
To: "carlo.bramix" <carlo.bramix@libero.it>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Reconsideration of MinGW work
Date: Tue, 23 Mar 2010 00:35:48 +0000 [thread overview]
Message-ID: <878w9jlvrv.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <KZNLW7$39BB0B1F144D250B5712400EAD7C74A5@libero.it> (carlo bramix's message of "Sun, 21 Mar 2010 23:45:43 +0100")
"carlo.bramix" <carlo.bramix@libero.it> writes:
> Hello!
Hi Carlo!
> Unfortunately, the network is one of the common problems when
> porting. It could be resoved with some work and with some "tricks" if
> someone wants.
Indeed. I know that I have patches pending for this. I also wonder if
the MinGW Guile port at the SF page that I cited includes those tricks.
(I will take a look.)
> Did you mean "regex" with "regular expressions"?
Yes.
> There
> are two of these libraries at mingw downloads but, unfortunately, I
> was not able to make them working: I had to take original sources and
> I recompiled myself.
Again, I wonder if the advertised MinGW Guile port has regex support.
>> Second, though, it turns out that using i586-mingw32msvc-* and Wine
>> on Linux unfortunately does not give the same results as MSYS and
>> MinGW on Windows. For example I've found that system(NULL) throws a
>> SIGSEGV under Wine, but for Carlo Bramix, working on Windows, that
>> wasn't a problem; and instead, for Carlo, there were other problems
>> that I don't see with a Linux cross build.
>
> Yes, it seems to be a bug of WINE. Look the sources of _wsystem()
> function at:
>
> http://source.winehq.org/git/wine.git/?a=blob;f=dlls/msvcrt/process.c;h=0b1eb01d2728b4df9e7d12a457dd3065bed1f1d1;hb=HEAD
Thanks.
> I have not tried to compile latest GUILE 1.9.9 on CYGWIN but I will
> try it in the lunch pause tomorrow. I'm quite confident it will work
> because I had not particular problems on previous versions.
Thanks, that's good to know.
> DLLs, well integrated in the system and running at a native speed that
> you will never reach in cygwin. Although many efforts have been made,
> cygwin acts more similar to virtual machine to me.
But why? I don't doubt that this is true - because many people have
said this, and I've seen myself that Cygwin applications seem slow. But
why, technically speaking, is it true?
> I'm not trying to
> change the decisions of the team in any way, I just wanted to show you
> why true win32 applications should be prefered to the ones made with
> cygwin (if this is possible to do, of course!).
Thanks. I accept that now.
> Me too, I made a working GUILE 1.8.6 that I'm currently using and
> until now it worked fine; afterall, I'm trying to build GUILE on
> Windows since version 1.8.3 :P
Yes. I appreciate your efforts, and I'm sorry it's taken a while for us
to get everything needed upstream.
>> - As far as future development is concerned, including the current
>> "master" branch, MinGW portability fixes should be directed at
>> Gnulib if possible, instead of done directly in the Guile code.
>
> For a project as complex as guile, probably this sounds to be a good
> solution.
Many thanks for your comments.
Neil
next prev parent reply other threads:[~2010-03-23 0:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 22:45 Re:Reconsideration of MinGW work carlo.bramix
2010-03-23 0:35 ` Neil Jerram [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-21 20:51 Reconsideration " Neil Jerram
2010-03-21 21:36 ` Grant Rettke
2010-03-22 1:28 ` Ken Raeburn
2010-03-22 20:10 ` Andy Wingo
2010-03-22 23:38 ` Greg Troxel
2010-03-23 0:04 ` Neil Jerram
2010-03-23 6:59 ` Ken Raeburn
2010-03-23 8:50 ` Andy Wingo
2010-03-22 8:10 ` Peter Brett
2010-03-22 20:00 ` Andy Wingo
2010-03-22 20:05 ` Linas Vepstas
2010-03-23 0:20 ` Neil Jerram
2010-03-23 0:13 ` Neil Jerram
2010-03-28 22:26 ` Ludovic Courtès
2010-03-29 20:34 ` Neil Jerram
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=878w9jlvrv.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=carlo.bramix@libero.it \
--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).