From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#18101: gccgo fails to build (all platforms) Date: Thu, 24 Jul 2014 13:39:45 -0400 Message-ID: <87k3723bby.fsf@yeeloong.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAN0z-0004gu-2v for bug-guix@gnu.org; Thu, 24 Jul 2014 13:41:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XAN0o-0007Au-Cy for bug-guix@gnu.org; Thu, 24 Jul 2014 13:41:12 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:41698) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAN0o-0007Ao-9t for bug-guix@gnu.org; Thu, 24 Jul 2014 13:41:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XAN0o-0003U2-0X for bug-guix@gnu.org; Thu, 24 Jul 2014 13:41:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34404) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAN07-0004Uj-5n for bug-guix@gnu.org; Thu, 24 Jul 2014 13:40:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XAMzz-0006z2-Ly for bug-guix@gnu.org; Thu, 24 Jul 2014 13:40:19 -0400 Received: from world.peace.net ([96.39.62.75]:55138) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAMzz-0006yy-Ij for bug-guix@gnu.org; Thu, 24 Jul 2014 13:40:11 -0400 List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: 18101@debbugs.gnu.org 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