[Bug ada/60620] missing gnattools dependency causes highly parallel build failure with --disable-bootstrap

[ebotcazou at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60620

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-03-31
                 CC|                            |ebotcazou at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> It appears the linking using g++ is intentional as -static-libstdc++ is
> passed, so that means that libstdc++ is required to build gnattools but that
> dependency is not documented.

Yes, the gnattools are also linked with the C++ compiler nowadays:

GCC_LINK=$(CXX) $(GCC_LINK_FLAGS) $(ADA_INCLUDES) $(LDFLAGS)

> The following patches solved the parallel build problems with --disable-
> bootstrap that we were seeing:
> 
> --- Makefile.def.orig	2013-10-29 13:37:47.000000000 -0500
> +++ Makefile.def
> @@ -336,6 +336,7 @@ dependencies = { module=all-libcpp; on=a
>  dependencies = { module=all-fixincludes; on=all-libiberty; };
>  
>  dependencies = { module=all-gnattools; on=all-target-libada; };
> +dependencies = { module=all-gnattools; on=all-target-libstdc++-v3; };
>  
>  dependencies = { module=all-lto-plugin; on=all-libiberty; };
> 
> 
> --- Makefile.in.orig	2014-03-07 07:58:27.000000000 -0500
> +++ Makefile.in
> @@ -46730,6 +46730,7 @@ all-stageprofile-libcpp: maybe-all-stage
>  all-stagefeedback-libcpp: maybe-all-stagefeedback-intl
>  all-fixincludes: maybe-all-libiberty
>  all-gnattools: maybe-all-target-libada
> +all-gnattools: maybe-all-target-libstdc++-v3
>  all-lto-plugin: maybe-all-libiberty
>  
>  all-stage1-lto-plugin: maybe-all-stage1-libiberty

Making host tools depend on target libraries always makes me cringe, but it's
the same situation as with libada so I guess it's OK.  Thanks for the patch.