GNU bug report logs - #18101
gccgo fails to build (all platforms)

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Mark H Weaver <mhw <at> netris.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#18101: closed (gccgo fails to build (all platforms))
Date: Thu, 31 Jul 2014 22:31:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 31 Jul 2014 18:30:12 -0400
with message-id <87y4v9yxe3.fsf <at> yeeloong.lan>
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
help-debbugs <at> gnu.org.)


-- 
18101: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18101
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mark H Weaver <mhw <at> netris.org>
To: bug-guix <at> gnu.org
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

[Message part 3 (message/rfc822, inline)]

From: Mark H Weaver <mhw <at> netris.org>
To: 18101-done <at> debbugs.gnu.org
Subject: Re: bug#18101: gccgo fails to build (all platforms)
Date: Thu, 31 Jul 2014 18:30:12 -0400

Mark H Weaver <mhw <at> netris.org> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.