X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Injected-Via-Gmane:	http://gmane.org/
To:	geda-user AT delorie DOT com
From:	Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject:	Re: [geda-user] Banging my head against the guile-for-windows wall
Date:	Wed, 24 Sep 2014 01:21:13 +0200
Lines:	38
Message-ID:	<lvsv9a$i91$1@ger.gmane.org>
References:	<20140923045453 DOT 56dc3de2 AT akka> <20140923052427 DOT 21624 DOT qmail AT stuge DOT se>
Mime-Version:	1.0
X-Complaints-To:	usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	a89-182-78-195.net-htp.de
User-Agent:	KNode/4.12.4
Reply-To:	geda-user AT delorie DOT com

Peter Stuge wrote:

>> In addition I added "-disable-Werror". The original "-Werror" flag
>> made the build process exit at the config stage. It complained
>> about the type "long long", which allegedly is not supported in
>> c90.
> 
> Mh, don't do this. Fix up the guile source code locally instead.
> 
> 
>> With this flag warnings are ignored and the build declares success.

Configure actually checked for long long and determined it to be 
supported on my set-up. So I figured, this particular warning can be 
safely ignored.  
 
> But who knows what the code will do? There may be actual programming
> errors in the source which the compiler identifies as warnings...
> 
> 
>> However, I get immediate segfault if I start the resulting
>> guile.exe with wine32.
> 
> My guess is that the code is broken somehow. 

And it somehow just affects the cross compile. The very same source 
works just fine if built native on Linux.


> I would work with the source code instead. First fix all warnings
> found by the compiler. Maybe also enable additional warnings and fix
> those. If the shell still crashes, debug by sprinkling
> printf("messages"); fflush(stdout);
> all over the code, to find where the crash happens.

This pedestrian approach is known to me ;-)

---<)kaimartin(>---

- Raw text -