unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-user <guile-user@gnu.org>,
	guile-gtk <guile-gtk-general@gnu.org>,
	guile-devel@gnu.org
Subject: Re: guile-gnome-0 - guile-1.6.8-6.3 - random crash
Date: Thu, 08 Apr 2010 22:06:17 +0200	[thread overview]
Message-ID: <87mxxd4sli.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3y6gx22ua.fsf@pobox.com> (Andy Wingo's message of "Thu, 08 Apr 2010 20:53:17 +0200")

() Andy Wingo <wingo@pobox.com>
() Thu, 08 Apr 2010 20:53:17 +0200

   No such luck with guile-pg, it will need patches.  I even tried
   applying debian's patches to see if that would help, but
   guile-pg uses gh.h.  Copying Thien-Thi, who appears to be the
   upstream: what is the right thing to do here?  Get it into a
   project on savannah in git hosting, no?

Sorry, i don't understand.  What does "it" refer to?

The right thing to do in any case is to identify the platform
specific parts, write tests to detect them, and code to accomodate
for them.

I started this with src/gi.h, but that is just the beginning.

thi




  reply	other threads:[~2010-04-08 20:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100317170918.0a21c8be@rascar>
     [not found] ` <m3bpegw0y9.fsf@pobox.com>
2010-04-08 18:06   ` guile-gnome-0 - guile-1.6.8-6.3 - random crash David Pirotte
2010-04-08 18:53     ` Andy Wingo
2010-04-08 20:06       ` Thien-Thi Nguyen [this message]
2010-04-08 22:13         ` Andy Wingo
2010-04-09  7:08           ` Thien-Thi Nguyen
2010-04-09  8:40             ` Andy Wingo
2010-04-10 14:23       ` David Pirotte
2010-04-11 20:24         ` Andy Wingo
2010-04-10 14:36       ` David Pirotte
2010-04-13 14:09       ` guile-gnome-0 - guile-1.6-latest - corrupted double-linked David Pirotte
2010-04-14 18:55         ` Andy Wingo
2010-04-15 19:46           ` 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=87mxxd4sli.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-devel@gnu.org \
    --cc=guile-gtk-general@gnu.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).