[debbugs-tracker] bug#18101: closed (gccgo fails to build (all platforms))

[GNU bug Tracking System]

Your message dated Thu, 31 Jul 2014 18:30:12 -0400
with message-id <address@hidden>
and subject line Re: bug#18101: gccgo fails to build (all platforms)
has caused the debbugs.gnu.org bug report #18101,
regarding gccgo fails to build (all platforms)
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18101: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18101
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> gccgo fails to build (all platforms)
>
>
>
>
> Date: 
>
> Thu, 24 Jul 2014 13:39:45 -0400
>
>
>
>
> At the very end of the builds for gccgo, there is an error:
>
>   cycle detected in the references of `/gnu/store/*-gccgo-4.8.3-lib'
>
> and that causes the build to fail.
>
> I wonder if this is fallout from when the gcc packages had their libs
> split into a different output.  Maybe the "lib" and "out" outputs of
> gccgo reference each other, and perhaps this is a problem?
>
>      Mark
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#18101: gccgo fails to build (all platforms)
>
>
>
>
> Date: 
>
> Thu, 31 Jul 2014 18:30:12 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
>
>
>
>
> Mark H Weaver <address@hidden> writes:
>
> > At the very end of the builds for gccgo, there is an error:
> >
> >   cycle detected in the references of `/gnu/store/*-gccgo-4.8.3-lib'
> >
> > and that causes the build to fail.
> >
> > I wonder if this is fallout from when the gcc packages had their libs
> > split into a different output.  Maybe the "lib" and "out" outputs of
> > gccgo reference each other, and perhaps this is a problem?
>
> I fixed this by suppressing the separate "lib" output in gccgo, commit
> c4df90a594672042ae106730ab5ce07fe85cf46f.  Closing this bug.
>
>       Mark
>
>
> --- End Message ---