parallel make fails for guile 1.8

parallel make fails for guile 1.8

[Mattias Holm]

Makes fails  when parallelisation option -jN is used. This is at  
least true for Mac OS X (which also fail in other parts of the make  
process, though this later error are apparently known (this also  
prevents me from using Guile 1.8 in my project)).

Non the less, something in the line of this results from parallel makes:

./guile-snarf -o arbiters.x arbiters.c -DHAVE_CONFIG_H -I.. -I.. -I/ 
opt/gmp/include -g -O2 -Wall -Wmissing-prototypes -Werror
In file included from ../libguile/_scm.h:63,
                  from alist.c:20:
../libguile/__scm.h:76:32: error: libguile/scmconfig.h: No such file  
or directory
In file included from ../libguile/_scm.h:63,


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: parallel make fails for guile 1.8

[Neil Jerram]

Mattias Holm <mattias.holm@contra.nu> writes:

> Makes fails  when parallelisation option -jN is used. This is at
> least true for Mac OS X (which also fail in other parts of the make
> process, though this later error are apparently known (this also
> prevents me from using Guile 1.8 in my project)).
>
> Non the less, something in the line of this results from parallel makes:
>
> ./guile-snarf -o arbiters.x arbiters.c -DHAVE_CONFIG_H -I.. -I.. -I/
> opt/gmp/include -g -O2 -Wall -Wmissing-prototypes -Werror
> In file included from ../libguile/_scm.h:63,
>                   from alist.c:20:
> ../libguile/__scm.h:76:32: error: libguile/scmconfig.h: No such file
> or directory
> In file included from ../libguile/_scm.h:63,

Thanks for reporting this.  I would guess this means that the Makefile
is failing to work out that the libguile .c files depend on
scmconfig.h, but I'm afraid I don't know the details of how this is
supposed to happen.

Regards,
        Neil



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: parallel make fails for guile 1.8

[Kevin Ryde]

Neil Jerram <neil@ossau.uklinux.net> writes:
>
> I would guess this means that the Makefile
> is failing to work out that the libguile .c files depend on
> scmconfig.h,

Yep.  I added scmconfig.h to the .x and .doc files dependencies,
because they run cpp.

For the .o files depending on scmconfig.h, I don't think there's a
good way to express that with automake.  The magic dependency tracking
might be supposed to do it, but I find that too painful.

BUILT_SOURCES (where scmconfig.h already is) is usually the easiest
way to get stuff done before building main .o files etc.  In our case
its defeated because guile.texi is in BUILT_SOURCES too, and it
depends on the main "guile" target, so that starts on the .o files for
libguile (under a parallel make).  But is guile.texi actually used for
anything?


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: parallel make fails for guile 1.8

[Neil Jerram]

Kevin Ryde <user42@zip.com.au> writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> I would guess this means that the Makefile
>> is failing to work out that the libguile .c files depend on
>> scmconfig.h,
>
> Yep.  I added scmconfig.h to the .x and .doc files dependencies,
> because they run cpp.
>
> For the .o files depending on scmconfig.h, I don't think there's a
> good way to express that with automake.  The magic dependency tracking
> might be supposed to do it, but I find that too painful.
>
> BUILT_SOURCES (where scmconfig.h already is) is usually the easiest
> way to get stuff done before building main .o files etc.  In our case
> its defeated because guile.texi is in BUILT_SOURCES too, and it
> depends on the main "guile" target, so that starts on the .o files for
> libguile (under a parallel make).  But is guile.texi actually used for
> anything?

It's only used as part of the doc/maint/docstring.el mechanism for
keeping the manual in sync with libguile docstrings - see
doc/maint/README.

I think that means it can be certainly be removed from BUILT_SOURCES.
It probably doesn't need to be built automatically at all; a developer
can do "make guile.texi" when they need it.

Regards,
     Neil



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: parallel make fails for guile 1.8

[Kevin Ryde]

Neil Jerram <neil@ossau.uklinux.net> writes:
>
> I think that means it can be certainly be removed from BUILT_SOURCES.

Beaut, I did that.

> It probably doesn't need to be built automatically at all; a developer
> can do "make guile.texi" when they need it.

Sticking it in "nodist_noinst_DATA = guile.texi" seems to work to get
it built under "make all", if you still want it.  If normal users
don't need it then maybe it should be restricted to "if
ENABLE_MAINTAINER_MODE" though.


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: parallel make fails for guile 1.8

[Neil Jerram]

Kevin Ryde <user42@zip.com.au> writes:

> Sticking it in "nodist_noinst_DATA = guile.texi" seems to work to get
> it built under "make all", if you still want it.  If normal users
> don't need it then maybe it should be restricted to "if
> ENABLE_MAINTAINER_MODE" though.

Thanks for noting that.  Feel free to go ahead with this if you like;
otherwise I think I'll wait until next time I actually need this,
before doing anything.

     Neil 



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile