From: Bo Forslund <bo.forslund@abc.se>
To: guile-gtk list <guile-gtk@sourceware.cygnus.com>
Cc: Marius Vollmer <mvo@zagadka.ping.de>
Subject: SMP problems with examples/Makefile.am
Date: Sun, 18 Nov 2001 13:23:00 -0000 [thread overview]
Message-ID: <3C2E863A.BE4C0EF7@abc.se> (raw)
Hello!
It is SMP problems with the Makefile in the examples dir.
I tested 30-40 compiles of the examples on a single-CPU box using a
Makefile built by the original Makefile.am containing the lines
foo-glue.c: foo.defs
build-guile-gtk glue $< >tmp && mv tmp $@
main.c: foo.defs
build-guile-gtk main $< >tmp && mv tmp $@
And it just worked. Every time.
On the dual-CPU box it failed most of the times with really odd result.
Sometimes the build created a main.c identical to foo-glue.c. Sometimes
the foo-glue.c or main.c was created with a couple of thousand
NULL characters (displayed as ^@ in emacs) and a chopped off line with
the extern sgtk_.... vars, and the rest of foo-glue.c as it should look.
something like
/* Generated by build-guile-gtk from "foo.defs". Do not edit. */
#include <libguile.h>
#include <guile-gtk.h>
#include <foo.h>
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
several thousands of ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
info sgtk_gdk_cap_style_info;
extern sgtk_enum_info sgtk_gdk_join_style_info;
extern sgtk_enum_info sgtk_gdk_cursor_type_info;
extern sgtk_enum_info sgtk_gdk_event_type_info;
extern sgtk_enum_info sgtk_gdk_notify_type_info;
### The rest of the file OK.
Having Makefile.am looking like this works on both the uni-cpu and the
dual-cpu box.
foo-glue.c: foo.defs
build-guile-gtk glue $< >$@
main.c: foo.defs
build-guile-gtk main $< >$@
I can't say that I really understand what the line "$< tmp && mv tmp $@"
does. Doesn't the line "$< >$@" work very much the same? Perhaps someone
can explain what can happen on parallell builds?
Bo
WARNING: multiple messages have this Message-ID
From: Bo Forslund <bo.forslund@abc.se>
To: guile-gtk list <guile-gtk@sourceware.cygnus.com>
Cc: Marius Vollmer <mvo@zagadka.ping.de>
Subject: SMP problems with examples/Makefile.am
Date: Sat, 29 Dec 2001 19:12:00 -0000 [thread overview]
Message-ID: <3C2E863A.BE4C0EF7@abc.se> (raw)
Message-ID: <20011229191200.h6Rjhp6Wm7hZVUKxlz_uvwy9JCenVoJR6FE5-D2O3w4@z> (raw)
Hello!
It is SMP problems with the Makefile in the examples dir.
I tested 30-40 compiles of the examples on a single-CPU box using a
Makefile built by the original Makefile.am containing the lines
foo-glue.c: foo.defs
build-guile-gtk glue $< >tmp && mv tmp $@
main.c: foo.defs
build-guile-gtk main $< >tmp && mv tmp $@
And it just worked. Every time.
On the dual-CPU box it failed most of the times with really odd result.
Sometimes the build created a main.c identical to foo-glue.c. Sometimes
the foo-glue.c or main.c was created with a couple of thousand
NULL characters (displayed as ^@ in emacs) and a chopped off line with
the extern sgtk_.... vars, and the rest of foo-glue.c as it should look.
something like
/* Generated by build-guile-gtk from "foo.defs". Do not edit. */
#include <libguile.h>
#include <guile-gtk.h>
#include <foo.h>
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
several thousands of ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
info sgtk_gdk_cap_style_info;
extern sgtk_enum_info sgtk_gdk_join_style_info;
extern sgtk_enum_info sgtk_gdk_cursor_type_info;
extern sgtk_enum_info sgtk_gdk_event_type_info;
extern sgtk_enum_info sgtk_gdk_notify_type_info;
### The rest of the file OK.
Having Makefile.am looking like this works on both the uni-cpu and the
dual-cpu box.
foo-glue.c: foo.defs
build-guile-gtk glue $< >$@
main.c: foo.defs
build-guile-gtk main $< >$@
I can't say that I really understand what the line "$< tmp && mv tmp $@"
does. Doesn't the line "$< >$@" work very much the same? Perhaps someone
can explain what can happen on parallell builds?
Bo
next reply other threads:[~2001-12-30 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 13:23 Bo Forslund [this message]
2001-11-19 14:42 ` Steve Tell
2001-11-19 14:44 ` Bo Forslund
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=3C2E863A.BE4C0EF7@abc.se \
--to=bo.forslund@abc.se \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=mvo@zagadka.ping.de \
/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).