public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Bo Forslund <bo.forslund@abc.se>
To: egcs@cygnus.com
Cc: guile-gtk list <guile-gtk@sourceware.cygnus.com>
Subject: Re: SMP problems with examples/Makefile.am
Date: Sun, 30 Dec 2001 09:29:00 -0000	[thread overview]
Message-ID: <3C2F4EFD.A1553FC2@abc.se> (raw)
Message-ID: <20011230092900.ught2VNxNWSJmt5KhzOuUcAdSu307cEmH-OMnTDrpxc@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0112300006050.26555-100000@ariel.lan.telltronics.org>

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

Steve Tell wrote:

> Perhaps best would be to use different temporary file names, say based on
> (but not the same as) the final target name:
>
>  foo-glue.c: foo.defs
>   build-guile-gtk glue $< >$@.new && mv $@.new $@
>
>  main.c: foo.defs
>   build-guile-gtk main $< >$@.new && mv $@.new $@
>

It did the trick.

I must say that it was rather difficult to try to understand how to use
guile-gtk with this gnome-guile disturbance and the SPM oddities.

A patch that makes guile-gtk compile outside of gnome-guile, and makes the
examples compile on SMP machines comes as an attach.

and here is a source rpm using the patch

ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-9.src.rpm


Now I shall concentrate on my own little guile-gtk project.  =)

Bo



[-- Attachment #2: guile-gtk-20011121-9.patch.gz --]
[-- Type: application/x-gzip, Size: 1114 bytes --]

  reply	other threads:[~2001-12-30  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-18 13:23 Bo Forslund
2001-11-19 14:42 ` Steve Tell
2001-11-19 14:44   ` Bo Forslund [this message]
2001-12-30  9:29     ` Bo Forslund
2001-12-29 21:13   ` Steve Tell
2001-12-29 19:12 ` Bo Forslund

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C2F4EFD.A1553FC2@abc.se \
    --to=bo.forslund@abc.se \
    --cc=egcs@cygnus.com \
    --cc=guile-gtk@sourceware.cygnus.com \
    /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).