SMP problems with examples/Makefile.am

SMP problems with examples/Makefile.am

[Bo Forslund]

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

Re: SMP problems with examples/Makefile.am

[Steve Tell]

On Sun, 30 Dec 2001, Bo Forslund wrote:

> 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 $@

I believe the point of the " >tmp && mv tmp $@" construct is that the
final target $@ is not touched unless build-guile-gtk completes
successfully with a zero exit status.

"A && B" is sh for "run A, and if successful then run B" 

If build-guile-gtk aborts due to signal or error, a subsequent make will
still find foo-glue.c or main.c out of date and rebuild them completely,
not being fooled by a recent modification time on an empty or incomplete
file.

Using a parallel make, both rules can execute at once and stomp on each
other writing to the same "tmp" file simultaneously.

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 $@



--
Steve Tell  tell@telltronics.org 

Re: SMP problems with examples/Makefile.am

[Bo Forslund]

[-- 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 --]

SMP problems with examples/Makefile.am

[Bo Forslund]

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

Re: SMP problems with examples/Makefile.am

[Steve Tell]

On Sun, 30 Dec 2001, Bo Forslund wrote:

> 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 $@

I believe the point of the " >tmp && mv tmp $@" construct is that the
final target $@ is not touched unless build-guile-gtk completes
successfully with a zero exit status.

"A && B" is sh for "run A, and if successful then run B" 

If build-guile-gtk aborts due to signal or error, a subsequent make will
still find foo-glue.c or main.c out of date and rebuild them completely,
not being fooled by a recent modification time on an empty or incomplete
file.

Using a parallel make, both rules can execute at once and stomp on each
other writing to the same "tmp" file simultaneously.

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 $@



--
Steve Tell  tell@telltronics.org 

Re: SMP problems with examples/Makefile.am

[Bo Forslund]

[-- 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 --]