X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=date:from:to:subject:message-id:mail-followup-to:references
	:mime-version:content-type:content-disposition:in-reply-to
	:user-agent;
	bh=aUgufwy/MCCnW8RT/loWjFofLh4fDLReHE9a5Osjsqs=;
	b=WTONyga8ztrPDP+yQ3sYDSLCenQVUcsrJIHfR8DF5hO1/RkgvT77U1b35i9xwAgKXD
	qG5lQP0k8MZUzbsQKwuW19HD0iZ9YLegkcoufw/yxhC5kV+ga12dIIKWSmshQMPWelU2
	ufJa7Qvm9VcPGYOMSxCTXK7OWPKJ+nOZdxMU6PBXP0cAQSCPhBTf5C93Z69Dm4AZH1zK
	ZJxxh5UmzXR4tnGDtOqBV232kMHhegyEU+2Anu3WZM63oyK3HAQi+XxZfzJAfNJaoFeT
	24Ys7qj6e9o09CCnqsTgeCrmgCioMvpfOvYcClggcM8DzdFk2uMzH9HaqBd0UAQKOJXy
	D9EQ==
X-Received:	by 10.152.5.201 with SMTP id u9mr28508471lau.26.1441796170188;
	Wed, 09 Sep 2015 03:56:10 -0700 (PDT)
Date:	Wed, 9 Sep 2015 13:56:07 +0300
From:	"Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Geda for windows -- notes from the engineroom
Message-ID:	<20150909105607.GA3354@localhost.localdomain>
Mail-Followup-To:	geda-user AT delorie DOT com
References:	<CAM2RGhT=aTYjyHWuxYFJXac8VhTOcB_piEGhq2dCNa61gAtFNw AT mail DOT gmail DOT com>
	<55E9BD63 DOT 8070407 AT jump-ing DOT de>
	<F6F6D986-713A-443E-B8FC-C6F7828C570D AT noqsi DOT com>
	<201509051930 DOT t85JUlTh019874 AT envy DOT delorie DOT com>
	<20150905210158 DOT GC7185 AT localhost DOT localdomain>
	<55EB74BF DOT 8010402 AT jump-ing DOT de>
	<20150906092106 DOT GF2637 AT localhost DOT localdomain>
	<msiafv$n14$1 AT ger DOT gmane DOT org>
	<20150908104643 DOT GA27440 AT localhost DOT localdomain>
	<msnj13$dr5$1 AT ger DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<msnj13$dr5$1@ger.gmane.org>
User-Agent:	Mutt/1.5.23 (2014-03-12)
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, Sep 08, 2015 at 11:13:06PM +0200, Kai-Martin Knaak wrote:
...
> Like the README suggested, I removed all guile related packages from the system. (This also took out the autogen package and of course geda-
> gschem from the repo). 
I would recommend using of chroot/VM for cross-compiling in order to not
break anything on your working system.
> 
> Still following the README I did:
>   ./mpk source guile
>   cp -r sources/guile .
>   cd guile/
>   ./autogen.sh && ./configure && make && sudo make install
> configure needed a little help by setting an environment variable:
> 	export BDW_GC_CFLAGS=-L/usr/lib BDW_GC_LIBS=-lgc
I don't know why they are needed, I've never done this.

> The compile took a little longer than expected (~80 minutes on an intel quad core). But it reported success and it installed to /usr/local/
> 
> For some reason, the install did not register the library. So I ran
> ldconfig manually - just like I always do if a recompile of geda
> bumps the version of gedalib. (Isn't libtool supposed to take care of
> this?)
> 
> Unfortunately, the guile cross compile was still unhappy:
> /minipack$ make guile
> Configuring guile...
> configure: WARNING: using cross tools not prefixed with host triplet
> configure: WARNING: Guessing that stack grows down -- see scmconfig.h
> configure: error: building Guile 2.0.11.148-d85d6d-dirty but `/usr/local/bin/guile' has version 2.1.0"
> 
> A quick check with 'guile -v' reveals that the freshly compiled binary
> in /usr/local is indeed version 2.1.0 . But for some reason the cross
> compile from the same sources insists to become version 2.0.11.148.. WTF?
> My shot in the dark: The windows cross compile is deliberately restricted
> to 2.0.11 because there are mission critical bugs in later versions.
> 
> Next try: There is a tag v2.0.11 in the git repo of guile. I checked out
> to this tag and recompiled and installed to /usr/local
> 
> The guile recipe needed a little tweak to also switch to the tag.
> 	repository=guile.git
> 	...
>   	if [ -d $name ]; then
>    	   cd $name && git checkout $branch && git pull origin $branch
>   	else
>   	   git clone $pkg_download && git checkout $branch
>   	fi
> 	...
> 	
> Now, the cross compile of guile managed to pass the configure stage. 
> Unfortunately, it stopped with errors shortly afterwards:
No, no. You have to use the same latest commit in the stable-2.0 branch
both for installation on your system and for cross-compilation. v2.0.11
doesn't build for windows. See the 'commit' variable in the recipe.
Probably, for guile it should to be more definite, i.e. just commit hash.
Now, either just checkout stable-2.0 or git pull the latest changes from
the minipack repo I've just made. It should checkout the needed commit
automatically.

2.1 is an unstable branch. It hardly has any windows support. The new
stable is 2.2. I've not tried it yet.

Cheers,
  Vladimir

- Raw text -