public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Bo Forslund <bo.forslund@abc.se>
To: Steve Tell <tell@telltronics.org>,
	guile-gtk list <guile-gtk@sourceware.cygnus.com>
Cc: Marius Vollmer <mvo@zagadka.ping.de>
Subject: Yet a new version (was Re: ERROR: In procedure dynamic-link:)
Date: Fri, 28 Dec 2001 20:21:00 -0000	[thread overview]
Message-ID: <3C2D44DA.2FE67936@abc.se> (raw)
Message-ID: <20011228202100.zahOEB479R-M9RoCzHkKIC-87TG76vev6KpRPLizwPY@z> (raw)
In-Reply-To: <3C2D174B.B0AF030E@abc.se>

I think I found what's wrong. It is not the package as a whole.

I used the exapmles to check whether the rpm builds were OK. I thought
that if the examples compiled OK then the package would be OK. I
suspected that it might be a SMP problem, and it might be. But not when
it comes to compile the package, only when it comes to compile the
examples. I think that the pagkage was built OK every time. It was just
the examples that were failing

I think it is last few lines in Makefile.am that is failing

foo-glue.c: foo.defs
        build-guile-gtk glue $< >tmp && mv tmp $@

main.c: foo.defs
        build-guile-gtk main $< >tmp && mv tmp $@

With this above in Makefile.am a build would fail 9 times of 10 or so.

I dont really understand how this works but I think the tmp-something is
deleted before the final file is ready written and that it is here it
might be an SMP problem. I am building on a dual CPU box.



Whith this  in Automake.am it works. I have tried several builds.

foo-glue.c: foo.defs
        build-guile-gtk glue $< >$@

main.c: foo.defs
        build-guile-gtk main $< >$@


Here is the last src.rpm
ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-8.src.rpm

The latest patch comes as an attach

G'nite
Bo

  reply	other threads:[~2001-12-28 20:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  4:34 ERROR: In procedure dynamic-link: Bo Forslund
2001-10-11  6:16 ` Alexey Rodriguez Y
2001-10-11 13:25   ` Bo Forslund
2001-10-11 15:20     ` Alexey Rodriguez Y
2001-10-18  0:23       ` Bo Forslund
2001-10-18  3:10         ` Marius Vollmer
2001-10-18 10:59           ` Alexey Rodriguez Y
2001-10-19 15:01             ` Bo Forslund
2001-11-05 17:33               ` Marius Vollmer
2001-11-12 13:11                 ` Bo Forslund
2001-11-14 10:53                   ` Marius Vollmer
2001-11-12 14:08             ` Marius Vollmer
2001-11-14 20:24               ` Alexey Rodriguez Y
2001-11-15  5:28                 ` Marius Vollmer
2001-11-15  7:11                   ` Bo Forslund
2001-11-15 15:20                     ` guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:) Steve Tell
2001-11-15 15:39                       ` Steve Tell
2001-11-16 14:11                         ` Bo Forslund
2001-11-17  6:17                           ` Bo Forslund
2001-11-18  8:30                             ` Bo Forslund [this message]
2001-12-28 20:21                               ` Yet a new version " Bo Forslund
2001-12-28 17:07                             ` guile-gtk snapshot " Bo Forslund
2001-12-28 16:47                           ` Bo Forslund
2001-12-28  6:25                         ` Steve Tell
2001-11-25  5:33                       ` Ariel Rios
2001-12-30 23:39                         ` Ariel Rios
2001-12-27 20:28                       ` Steve Tell
2001-11-25  7:33                     ` ERROR: In procedure dynamic-link: 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=3C2D44DA.2FE67936@abc.se \
    --to=bo.forslund@abc.se \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=mvo@zagadka.ping.de \
    --cc=tell@telltronics.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).