unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Barry Fishman <barry@ecubist.org>
Cc: guile-user@gnu.org
Subject: Re: getting started writing desktop applications
Date: Thu, 21 Jul 2016 16:35:56 -0300	[thread overview]
Message-ID: <20160721163556.1f00d52b@capac> (raw)
In-Reply-To: <m3vb00l2mn.fsf@ecube.ecubist.org>

[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]

Hello Barry,
Nala,

> On 2016-07-18 12:52:24 +08, Nala Ginrut wrote:
> > I happened to try guile-gnome few days ago, seems not workable with
> > 2.1, I'm using the latest master. Anyone ever tried it?  

> Yes, with the same bad results.  It is hard for me to tell where the
> issue lies, since many of its dependent packages fail their self tests,
> although work with my own simple tests.

Indeed. Guile-GNOME depends on G-Wrap and Guile-Cairo, and FWIW, note that all
compile and work fine with 2.0.11, 2.0.12 and up to 2.1.2.

G-Wrap fails with 2.1.3, because it uses a series of libguile.h functions marked as
deprecated in 2.2

I will try to solve this, but I have very little knowledge of the internals of
G-Wrap itself, so don't hold your breath: instead, if you can, use 2.1.2 or 2.0.12
of course.

> The whole autoreconf setup for added modules seems to get broken with
> every development releases.  Some packages seem to require multiple
> reconfigs before they build. 

I'm not aware of any of this, could you be more specific?

> Tests break with errors like not being able to exec "/bin/sh"

This is the symptom that you have a 'corrupted' environment, and the test suite can't
find guile and/or guild

> I don't understand why Guile modules use such a patchy environment when

What Guile modules?

> necessary, building its own C tests.  Simple packages like guile-lib now
> fail tests even without need for C tests.

This has been fixed, patched under revision: they will be pushed and guile-lib will
be released by the end of this month.

	https://lists.gnu.org/archive/html/guile-devel/2016-07/msg00055.html

In the mean time, you can use guile-lib: the make check failure is 'just' because
its autotool chain files have not been updated to require the tests to be serial.

Note that even after these 11 patches, the test suite will fail for 2 tests against
2.1.3: these concerns modules that are _not_ used by Guile-GNOME, I reported and
will personally not debug these, patch welcome:

	https://lists.gnu.org/archive/html/guile-devel/2016-07/msg00066.html

> Yes, work has been put into autoconf to make it very powerful, but like
> most pure macro based environments the output is fragile, and almost
> unreadable by most mortals.

AFAICT, there is no autotool chain related bug in Guile-GNOME, neither in Guile
itself.  Make check fails for Guile-Cairo for the same reason as it does for
guile-lib, but it works fine, just make check fails: I'll patch [I did locally] and
upload an unofficial release somewhere.

David.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-07-21 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17 16:38 getting started writing desktop applications Christopher M. Hobbs
2016-07-17 16:43 ` Paul Emsley
2016-07-18  4:52   ` Nala Ginrut
2016-07-20 16:01     ` Barry Fishman
2016-07-21 19:35       ` David Pirotte [this message]
2016-07-21 21:39         ` Barry Fishman
2016-07-21 23:15           ` David Pirotte

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=20160721163556.1f00d52b@capac \
    --to=david@altosw.be \
    --cc=barry@ecubist.org \
    --cc=guile-user@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).